Channel
Muz~Bespridel
@muz_bespridel
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,716subscribers
+30 since we began measuring on 18 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001530509920 |
|---|---|
| Type | Channel |
| Username | @muz_bespridel |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 20 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/muz_bespridel |
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 95% 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 |
|---|---|---|
| 5 Nov 2026, 16:58 | 3,716 | +6 |
| 2 Nov 2026, 09:54 | 3,710 | +3 |
| 27 Oct 2026, 07:49 | 3,707 | +3 |
| 24 Oct 2026, 12:56 | 3,704 | -2 |
| 21 Oct 2026, 20:28 | 3,706 | +5 |
| 18 Oct 2026, 17:40 | 3,701 | -6 |
| 15 Oct 2026, 07:06 | 3,707 | +5 |
| 12 Oct 2026, 12:51 | 3,702 | -6 |
| 5 Oct 2026, 11:19 | 3,708 | +3 |
| 27 Sept 2026, 02:21 | 3,705 | +21 |
| 17 Sept 2026, 14:00 | 3,684 | -2 |
| 13 Sept 2026, 03:41 | 3,686 | -1 |
| 9 Sept 2026, 01:37 | 3,687 | -4 |
| 7 Sept 2026, 00:06 | 3,691 | no change |
| 3 Sept 2026, 08:15 | 3,691 | -6 |
| 31 Aug 2026, 01:55 | 3,697 | +11 |
| 27 Aug 2026, 15:36 | 3,686 | +6 |
| 25 Aug 2026, 02:04 | 3,680 | -2 |
| 18 Aug 2026, 14:53 | 3,682 | -4 |
| 18 Aug 2026, 00:30 | 3,686 | 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.
@kavkaz_muz · 36,066
Telegram ranks this channel #27 of 76 here — alongside 75 others — read 2 September 2026
@new_muzyka_kavkaza · 23,557
Telegram ranks this channel #40 of 66 here — alongside 65 others — read 20 September 2026
@muzone_official · 24,929
Telegram ranks this channel #49 of 54 here — alongside 53 others — read 15 September 2026
This channel appears in 4 seed channels' Telegram-generated recommendation lists in total, of which the 3 where it ranks highest are shown above. 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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“Muz~Bespridel” (@muz_bespridel), 3,716 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/muz_bespridel.
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.