Channel
شیوا موزیک
@muzik_shiva
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,357subscribers
+8 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001213457061 |
|---|---|
| Type | Channel |
| Username | @muzik_shiva |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 3 September 2026 |
| Last confirmed live | 3 November 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 2 times, most recently 3 November 2026 |
| On Telegram | t.me/muzik_shiva |
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 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 |
|---|---|---|
| 31 Oct 2026, 15:17 | 4,357 | -5 |
| 28 Oct 2026, 11:19 | 4,362 | -7 |
| 25 Oct 2026, 11:15 | 4,369 | -4 |
| 22 Oct 2026, 20:50 | 4,373 | -3 |
| 19 Oct 2026, 22:48 | 4,376 | +9 |
| 17 Oct 2026, 09:05 | 4,367 | -9 |
| 14 Oct 2026, 14:19 | 4,376 | -4 |
| 11 Oct 2026, 10:14 | 4,380 | -9 |
| 5 Oct 2026, 08:19 | 4,389 | -11 |
| 18 Sept 2026, 03:02 | 4,400 | +2 |
| 13 Sept 2026, 19:40 | 4,398 | +10 |
| 9 Sept 2026, 19:17 | 4,388 | +9 |
| 4 Sept 2026, 09:41 | 4,379 | +3 |
| 3 Sept 2026, 22:49 | 4,376 | no change |
| 31 Aug 2026, 20:36 | 4,376 | +9 |
| 28 Aug 2026, 10:58 | 4,367 | +6 |
| 25 Aug 2026, 18:14 | 4,361 | +13 |
| 22 Aug 2026, 17:24 | 4,348 | +8 |
| 18 Aug 2026, 22:18 | 4,340 | -5 |
| 15 Aug 2026, 20:03 | 4,345 | 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.
@Charkhessh · 829,830
Telegram ranks this channel #34 of 60 here — alongside 59 others — read 12 August 2026
@hijranofficial · 19,795
Telegram ranks this channel #46 of 64 here — alongside 63 others — read 29 September 2026
@sebti_irrr · 42,951
Telegram ranks this channel #68 of 71 here — alongside 70 others — read 5 October 2026
@khabareh_forie · 63,691
Telegram ranks this channel #83 of 92 here — alongside 91 others — read 21 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 31 October 2026 — this entry's latest reading, not the date you are reading this.
“شیوا موزیک” (@muzik_shiva), 4,357 subscribers as measured 31 October 2026. Telegram Register, tgregister.com/channel/muzik_shiva.
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.