Channel
Music Sweet
@Music_Sweet
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,724subscribers
-139 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 | -1001109719221 |
|---|---|
| Type | Channel |
| Username | @Music_Sweet |
| Created | Between 1 February 2017 and 30 November 2019 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 September 2026 |
| Last confirmed live | 1 November 2026 |
| Measurements held | 22 |
| Confirmed unchanged | 1 time, most recently 1 November 2026 |
| On Telegram | t.me/Music_Sweet |
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 96% 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 |
|---|---|---|
| 1 Nov 2026, 05:07 | 3,724 | -5 |
| 29 Oct 2026, 11:51 | 3,729 | -6 |
| 26 Oct 2026, 03:16 | 3,735 | -11 |
| 23 Oct 2026, 06:48 | 3,746 | -4 |
| 19 Oct 2026, 21:58 | 3,750 | -4 |
| 16 Oct 2026, 19:17 | 3,754 | -4 |
| 13 Oct 2026, 21:27 | 3,758 | -9 |
| 8 Oct 2026, 04:41 | 3,767 | -10 |
| 1 Oct 2026, 08:36 | 3,777 | -30 |
| 16 Sept 2026, 09:00 | 3,807 | -5 |
| 12 Sept 2026, 12:56 | 3,812 | -10 |
| 8 Sept 2026, 15:19 | 3,822 | -9 |
| 6 Sept 2026, 13:28 | 3,831 | no change |
| 31 Aug 2026, 10:56 | 3,831 | -3 |
| 28 Aug 2026, 14:44 | 3,834 | -5 |
| 25 Aug 2026, 17:45 | 3,839 | -3 |
| 22 Aug 2026, 20:03 | 3,842 | -9 |
| 19 Aug 2026, 14:51 | 3,851 | -4 |
| 16 Aug 2026, 22:15 | 3,855 | -4 |
| 13 Aug 2026, 09:06 | 3,859 | 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.
@sedaynab · 26,235
Telegram ranks this channel #28 of 61 here — alongside 60 others — read 13 September 2026
@Radio_alizo · 186,770
Telegram ranks this channel #37 of 52 here — alongside 51 others — read 12 August 2026
@rokoshaa · 366,874
Telegram ranks this channel #47 of 64 here — alongside 63 others — read 10 August 2026
@RadioRelax · 323,678
Telegram ranks this channel #86 of 90 here — alongside 89 others — read 10 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 1 November 2026 — this entry's latest reading, not the date you are reading this.
“Music Sweet” (@Music_Sweet), 3,724 subscribers as measured 1 November 2026. Telegram Register, tgregister.com/channel/Music_Sweet.
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.