Telegram RegisterThe public register of Telegram
Telegram profile photo for Amir Arsin

Channel

Amir Arsin

@AmirArsiin

On this record: Growth · Engagement · Telegram's recommendations · Cite this entry

5,475subscribers

+400 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001496366738
TypeChannel
Username@AmirArsiin
CreatedBetween 1 November 2019 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded30 August 2026
Last confirmed live9 September 2026
Measurements held13
Confirmed unchanged1 time, most recently 9 September 2026
On Telegramt.me/AmirArsiin

Growth

5,0755,4875,2816 August 2026 — 5,075 subscribers7 August 2026 — 5,082 subscribers10 August 2026 — 5,117 subscribers13 August 2026 — 5,220 subscribers16 August 2026 — 5,274 subscribers19 August 2026 — 5,328 subscribers23 August 2026 — 5,404 subscribers26 August 2026 — 5,409 subscribers29 August 2026 — 5,434 subscribers30 August 2026 — 5,434 subscribers1 September 2026 — 5,461 subscribers4 September 2026 — 5,487 subscribers9 September 2026 — 5,475 subscribers5,4756 August 20269 September 2026
13 measurements spanning 34 days, net +400. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 5,013–5,549 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Sept 2026, 18:395,475-12
4 Sept 2026, 12:575,487+26
1 Sept 2026, 07:495,461+27
30 Aug 2026, 23:205,434no change
29 Aug 2026, 10:295,434+25
26 Aug 2026, 16:075,409+5
23 Aug 2026, 20:345,404+76
19 Aug 2026, 23:515,328+54
16 Aug 2026, 17:185,274+54
13 Aug 2026, 06:045,220+103
10 Aug 2026, 03:325,117+35
7 Aug 2026, 12:335,082+7
6 Aug 2026, 23:585,075first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

novan
@novanmusic · 52,236
Telegram ranks this channel #31 of 49 here — alongside 48 others — read 24 August 2026
1mhyar
@mahyartunes · 76,497
Telegram ranks this channel #40 of 51 here — alongside 50 others — read 28 August 2026
Aliyasini
@aliyasini · 75,602
Telegram ranks this channel #46 of 61 here — alongside 60 others — read 19 August 2026
Soheil mehrzadegan
@soheilmehrzadegan · 40,368
Telegram ranks this channel #61 of 72 here — alongside 71 others — read 30 August 2026

This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 9 September 2026 — this entry's latest reading, not the date you are reading this.

“Amir Arsin” (@AmirArsiin), 5,475 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/AmirArsiin.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.