
Channel
بانک ریتم وصدااحمدحسن زاده🎹
@ahmadhasanzadehritm
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,009subscribers
+17 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001074550938 |
|---|---|
| Type | Channel |
| Username | @ahmadhasanzadehritm |
| Created | Between 1 September 2016 and 30 September 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 5 September 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/ahmadhasanzadehritm |
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 92% 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 16:59 | 4,009 | +29 |
| 12 Sept 2026, 02:55 | 3,980 | +14 |
| 7 Sept 2026, 16:19 | 3,966 | +6 |
| 5 Sept 2026, 22:39 | 3,960 | no change |
| 2 Sept 2026, 21:37 | 3,960 | -6 |
| 31 Aug 2026, 05:04 | 3,966 | -2 |
| 28 Aug 2026, 09:06 | 3,968 | -1 |
| 25 Aug 2026, 17:32 | 3,969 | -4 |
| 22 Aug 2026, 19:17 | 3,973 | +1 |
| 19 Aug 2026, 10:03 | 3,972 | -2 |
| 16 Aug 2026, 08:36 | 3,974 | -8 |
| 12 Aug 2026, 21:28 | 3,982 | -3 |
| 9 Aug 2026, 19:11 | 3,985 | -2 |
| 6 Aug 2026, 18:57 | 3,987 | -5 |
| 5 Aug 2026, 23:23 | 3,992 | 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.
@abolfazlrahimiorg · 73,432
Telegram ranks this channel #1 of 59 here — alongside 58 others — read 27 August 2026
@mortezajavan22 · 24,710
Telegram ranks this channel #10 of 63 here — alongside 62 others — read 15 September 2026
@shahrainy · 29,143
Telegram ranks this channel #14 of 56 here — alongside 55 others — read 9 September 2026
@ahangemahalikhorasan · 47,311
Telegram ranks this channel #18 of 54 here — alongside 53 others — read 27 August 2026
@MashtiRemix · 33,565
Telegram ranks this channel #44 of 53 here — alongside 52 others — read 6 September 2026
This channel appears in 5 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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“بانک ریتم وصدااحمدحسن زاده🎹” (@ahmadhasanzadehritm), 4,009 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/ahmadhasanzadehritm.
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.