Channel
Ziba Rahimi
@zibarahimi_music
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,508subscribers
-9 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 | -1001167762635 |
|---|---|
| Type | Channel |
| Username | @zibarahimi_music |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 September 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/zibarahimi_music |
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 14 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 21:59 | 3,508 | +31 |
| 12 Sept 2026, 05:01 | 3,477 | -5 |
| 8 Sept 2026, 13:17 | 3,482 | no change |
| 8 Sept 2026, 01:59 | 3,482 | -1 |
| 3 Sept 2026, 09:48 | 3,483 | -2 |
| 31 Aug 2026, 06:47 | 3,485 | -5 |
| 28 Aug 2026, 13:35 | 3,490 | +1 |
| 25 Aug 2026, 05:54 | 3,489 | -3 |
| 22 Aug 2026, 12:16 | 3,492 | -6 |
| 19 Aug 2026, 11:45 | 3,498 | -8 |
| 16 Aug 2026, 09:07 | 3,506 | -3 |
| 13 Aug 2026, 03:36 | 3,509 | -3 |
| 10 Aug 2026, 09:55 | 3,512 | -6 |
| 7 Aug 2026, 08:08 | 3,518 | +1 |
| 6 Aug 2026, 21:10 | 3,517 | 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.
@TehranMusic · 45,002
Telegram ranks this channel #24 of 80 here — alongside 79 others — read 30 August 2026
@nivadmusic · 25,974
Telegram ranks this channel #36 of 91 here — alongside 90 others — read 13 September 2026
@shimamuzic · 31,316
Telegram ranks this channel #37 of 85 here — alongside 84 others — read 6 September 2026
@birmusicOfficial · 47,462
Telegram ranks this channel #47 of 79 here — alongside 78 others — read 26 August 2026
@rozmusict · 87,308
Telegram ranks this channel #60 of 84 here — alongside 83 others — read 18 August 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.
“Ziba Rahimi” (@zibarahimi_music), 3,508 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/zibarahimi_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.