Channel
Ali Tirdad
@alitirdadmusic
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,068subscribers
+1,588 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001071834616 |
|---|---|
| Type | Channel |
| Username | @alitirdadmusic |
| Created | Between 1 October 2016 and 31 July 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 September 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/alitirdadmusic |
Topic
Other / unclassifiable — 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 15 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Nov 2026, 11:06 | 2,068 | -16 |
| 3 Nov 2026, 10:19 | 2,084 | -27 |
| 31 Oct 2026, 01:27 | 2,111 | -35 |
| 27 Oct 2026, 18:19 | 2,146 | -17 |
| 24 Oct 2026, 17:58 | 2,163 | -18 |
| 22 Oct 2026, 00:20 | 2,181 | -25 |
| 19 Oct 2026, 00:10 | 2,206 | -31 |
| 16 Oct 2026, 06:06 | 2,237 | -38 |
| 12 Oct 2026, 21:26 | 2,275 | -82 |
| 6 Oct 2026, 05:19 | 2,357 | -102 |
| 29 Sept 2026, 09:16 | 2,459 | -212 |
| 19 Sept 2026, 05:37 | 2,671 | -80 |
| 14 Sept 2026, 21:59 | 2,751 | -97 |
| 12 Sept 2026, 21:46 | 2,848 | no change |
| 11 Sept 2026, 03:39 | 2,848 | -157 |
| 6 Sept 2026, 16:17 | 3,005 | +601 |
| 2 Sept 2026, 05:05 | 2,404 | +756 |
| 30 Aug 2026, 09:59 | 1,648 | -42 |
| 27 Aug 2026, 14:43 | 1,690 | -30 |
| 24 Aug 2026, 20:48 | 1,720 | first 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.
@masoudjahanioriginal · 83,386
Telegram ranks this channel #8 of 68 here — alongside 67 others — read 18 August 2026
@shahan_tunes · 31,337
Telegram ranks this channel #16 of 71 here — alongside 70 others — read 21 September 2026
@DJPhellix · 31,985
Telegram ranks this channel #33 of 63 here — alongside 62 others — read 7 September 2026
@Asmaol_Hosna · 50,694
Telegram ranks this channel #44 of 63 here — alongside 62 others — read 25 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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“Ali Tirdad” (@alitirdadmusic), 2,068 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/alitirdadmusic.
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.