Channel
𝕸𝖚𝖘𝖎𝖈𝖆𝖑 𝕮𝖆𝖕𝖗𝖎𝖈𝖊 🎶❤️
@Musik_Caprice
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,816subscribers
+23 since we began measuring on 30 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001695882806 |
|---|---|
| Type | Channel |
| Username | @Musik_Caprice |
| Created | 13 September 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 12 September 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/Musik_Caprice |
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 16 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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 |
|---|---|---|
| 16 Sept 2026, 00:59 | 2,816 | -2 |
| 12 Sept 2026, 23:54 | 2,818 | no change |
| 12 Sept 2026, 07:39 | 2,818 | +19 |
| 8 Sept 2026, 11:16 | 2,799 | +8 |
| 3 Sept 2026, 01:49 | 2,791 | -1 |
| 31 Aug 2026, 03:57 | 2,792 | -1 |
| 30 Aug 2026, 09:15 | 2,793 | 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.
@muzukarussia · 23,909
Telegram ranks this channel #6 of 54 here — alongside 53 others — read 17 September 2026
@club_sound · 35,691
Telegram ranks this channel #9 of 59 here — alongside 58 others — read 2 September 2026
@best_mus_on · 55,904
Telegram ranks this channel #17 of 60 here — alongside 59 others — read 7 September 2026
@best_deeep · 153,044
Telegram ranks this channel #45 of 65 here — alongside 64 others — read 17 September 2026
@kanallatii · 25,977
Telegram ranks this channel #48 of 55 here — alongside 54 others — read 13 September 2026
@CarrMuzic · 32,091
Telegram ranks this channel #67 of 69 here — alongside 68 others — read 5 September 2026
@MUSICplusze · 23,330
Telegram ranks this channel #69 of 75 here — alongside 74 others — read 18 September 2026
@Soundbaar · 40,500
Telegram ranks this channel #71 of 78 here — alongside 77 others — read 30 August 2026
This channel appears in 8 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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“𝕸𝖚𝖘𝖎𝖈𝖆𝖑 𝕮𝖆𝖕𝖗𝖎𝖈𝖊 🎶❤️” (@Musik_Caprice), 2,816 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/Musik_Caprice.
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.