Channel
بلوچی زیمل | آهنگ بلوچی
@balochizimol
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
5,236subscribers
+31 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 | -1001564133414 |
|---|---|
| Type | Channel |
| Username | @balochizimol |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 31 August 2026 |
| Last confirmed live | 23 October 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 23 October 2026 |
| On Telegram | t.me/balochizimol |
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 13 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 |
|---|---|---|
| 23 Oct 2026, 21:58 | 5,236 | +2 |
| 20 Oct 2026, 21:28 | 5,234 | +1 |
| 17 Oct 2026, 16:17 | 5,233 | -3 |
| 14 Oct 2026, 21:46 | 5,236 | +4 |
| 11 Oct 2026, 23:55 | 5,232 | +8 |
| 27 Sept 2026, 14:19 | 5,224 | -2 |
| 18 Sept 2026, 13:59 | 5,226 | -4 |
| 14 Sept 2026, 01:41 | 5,230 | +6 |
| 10 Sept 2026, 03:38 | 5,224 | +2 |
| 5 Sept 2026, 05:37 | 5,222 | -9 |
| 1 Sept 2026, 09:25 | 5,231 | +4 |
| 31 Aug 2026, 22:13 | 5,227 | no change |
| 29 Aug 2026, 09:26 | 5,227 | -1 |
| 26 Aug 2026, 16:46 | 5,228 | +7 |
| 23 Aug 2026, 20:09 | 5,221 | +1 |
| 20 Aug 2026, 14:36 | 5,220 | +1 |
| 17 Aug 2026, 19:13 | 5,219 | +8 |
| 14 Aug 2026, 06:19 | 5,211 | +4 |
| 10 Aug 2026, 20:29 | 5,207 | +4 |
| 8 Aug 2026, 05:52 | 5,203 | 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.
@golchinmusic01 · 20,290
Telegram ranks this channel #23 of 58 here — alongside 57 others — read 30 September 2026
@balochestaniha1 · 22,967
Telegram ranks this channel #27 of 73 here — alongside 72 others — read 19 September 2026
@Vava_baloch · 49,832
Telegram ranks this channel #43 of 71 here — alongside 70 others — read 2 September 2026
@nambaronebalouch · 35,135
Telegram ranks this channel #53 of 74 here — alongside 73 others — read 2 September 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 23 October 2026 — this entry's latest reading, not the date you are reading this.
“بلوچی زیمل | آهنگ بلوچی” (@balochizimol), 5,236 subscribers as measured 23 October 2026. Telegram Register, tgregister.com/channel/balochizimol.
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.