Channel
Playlist
@musicccccc1221
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,684subscribers
-176 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002085151701 |
|---|---|
| Type | Channel |
| Username | @musicccccc1221 |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 September 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/musicccccc1221 |
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 14 September 2026 and assigned it the closest of 31 fixed categories, at 68% 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 |
|---|---|---|
| 6 Nov 2026, 21:04 | 3,684 | -6 |
| 4 Nov 2026, 03:24 | 3,690 | -4 |
| 1 Nov 2026, 00:15 | 3,694 | -2 |
| 29 Oct 2026, 00:05 | 3,696 | -7 |
| 25 Oct 2026, 12:10 | 3,703 | -5 |
| 22 Oct 2026, 07:21 | 3,708 | -6 |
| 18 Oct 2026, 19:50 | 3,714 | -5 |
| 16 Oct 2026, 03:06 | 3,719 | -1 |
| 12 Oct 2026, 18:08 | 3,720 | -47 |
| 5 Oct 2026, 19:38 | 3,767 | -18 |
| 28 Sept 2026, 14:36 | 3,785 | -17 |
| 15 Sept 2026, 18:39 | 3,802 | -13 |
| 12 Sept 2026, 05:59 | 3,815 | -6 |
| 7 Sept 2026, 20:39 | 3,821 | -3 |
| 6 Sept 2026, 13:36 | 3,824 | no change |
| 2 Sept 2026, 17:27 | 3,824 | -8 |
| 30 Aug 2026, 05:57 | 3,832 | -5 |
| 27 Aug 2026, 04:22 | 3,837 | -1 |
| 23 Aug 2026, 23:45 | 3,838 | -4 |
| 20 Aug 2026, 10:32 | 3,842 | 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.
@Trilion_Games · 21,726
Telegram ranks this channel #4 of 59 here — alongside 58 others — read 20 September 2026
@signaIpersian · 53,054
Telegram ranks this channel #33 of 59 here — alongside 58 others — read 22 August 2026
@king_of_crypto_ir · 254,036
Telegram ranks this channel #50 of 57 here — alongside 56 others — read 13 August 2026
@cryptoo_ab · 246,832
Telegram ranks this channel #52 of 64 here — alongside 63 others — read 10 August 2026
This channel appears in 6 seed channels' Telegram-generated recommendation lists in total, of which the 4 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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“Playlist” (@musicccccc1221), 3,684 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/musicccccc1221.
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.