Telegram RegisterThe public register of Telegram
Telegram profile photo for Ariush_music

Channel

Ariush_music

@ariush_music

On this record: Topic · Growth · Engagement · Cite this entry

3,384subscribers

+38 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001034292953
TypeChannel
Username@ariush_music
CreatedBetween 1 January 2016 and 31 October 2016 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 September 2026
Last confirmed live5 November 2026
Measurements held23
Confirmed unchanged1 time, most recently 5 November 2026
On Telegramt.me/ariush_music

Topic

Music — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 14 September 2026 and assigned it the closest of 31 fixed categories, at 82% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.

Growth

3,3253,3993,3627 August 2026 — 3,346 subscribers7 August 2026 — 3,345 subscribers11 August 2026 — 3,348 subscribers14 August 2026 — 3,339 subscribers17 August 2026 — 3,337 subscribers21 August 2026 — 3,329 subscribers24 August 2026 — 3,328 subscribers28 August 2026 — 3,325 subscribers31 August 2026 — 3,337 subscribers3 September 2026 — 3,360 subscribers9 September 2026 — 3,360 subscribers9 September 2026 — 3,379 subscribers13 September 2026 — 3,382 subscribers17 September 2026 — 3,386 subscribers26 September 2026 — 3,380 subscribers5 October 2026 — 3,364 subscribers11 October 2026 — 3,361 subscribers15 October 2026 — 3,360 subscribers25 October 2026 — 3,381 subscribers28 October 2026 — 3,394 subscribers31 October 2026 — 3,399 subscribers2 November 2026 — 3,389 subscribers5 November 2026 — 3,384 subscribers3,3847 August 20265 November 2026
23 measurements spanning 90 days, net +38. 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 3,314–3,410 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 23
Measured (UTC)SubscribersChange
5 Nov 2026, 15:163,384-5
2 Nov 2026, 22:573,389-10
31 Oct 2026, 05:493,399+5
28 Oct 2026, 05:283,394+13
25 Oct 2026, 01:193,381+21
15 Oct 2026, 00:163,360-1
11 Oct 2026, 09:153,361-3
5 Oct 2026, 05:183,364-16
26 Sept 2026, 12:413,380-6
17 Sept 2026, 17:003,386+4
13 Sept 2026, 05:553,382+3
9 Sept 2026, 07:563,379+19
9 Sept 2026, 00:033,360no change
3 Sept 2026, 17:013,360+23
31 Aug 2026, 07:143,337+12
28 Aug 2026, 02:263,325-3
24 Aug 2026, 23:153,328-1
21 Aug 2026, 05:583,329-8
17 Aug 2026, 21:493,337-2
14 Aug 2026, 20:363,339first 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.

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 5 November 2026 — this entry's latest reading, not the date you are reading this.

“Ariush_music” (@ariush_music), 3,384 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/ariush_music.

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.