Channel
Radio Music 📻 ❄️
@RadioMusicRock
On this record: Topic · Previous handles · Growth · Engagement · Telegram's recommendations · Cite this entry
1,593subscribers
+5 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001009892186 |
|---|---|
| Type | Channel |
| Username | @RadioMusicRock |
| Description | Classical to Rock n Roll We cordially invite you to join the channel Instagram: instagram.com/radio_music_rock |
| Created | Between 1 October 2015 and 31 January 2016 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 26 September 2026 |
| Last confirmed live | 26 September 2026 |
| Measurements held | 14 |
| On Telegram | t.me/RadioMusicRock |
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 26 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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.
Previous handles
Recorded in 2019 as “Radio Music 📻” — the title held for this same channel (matched by Telegram id, not by handle) in the Pushshift Telegram Dataset, a third-party archive captured in 2019-2020, years before this register made its own first observation. CC BY 4.0, Baumgartner, Zannettou, Squire & Blackburn (2020), Zenodo. A third party’s dated snapshot, not a measurement this register made itself.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 26 Sept 2026, 03:45 | 1,593 | no change |
| 19 Sept 2026, 11:21 | 1,593 | +3 |
| 15 Sept 2026, 03:39 | 1,590 | +1 |
| 7 Sept 2026, 11:40 | 1,589 | -1 |
| 2 Sept 2026, 08:44 | 1,590 | -2 |
| 30 Aug 2026, 19:13 | 1,592 | +3 |
| 27 Aug 2026, 16:28 | 1,589 | +1 |
| 25 Aug 2026, 02:53 | 1,588 | -2 |
| 21 Aug 2026, 07:55 | 1,590 | +2 |
| 18 Aug 2026, 14:24 | 1,588 | +1 |
| 12 Aug 2026, 13:54 | 1,587 | -4 |
| 9 Aug 2026, 14:15 | 1,591 | +4 |
| 6 Aug 2026, 14:40 | 1,587 | -1 |
| 5 Aug 2026, 21:37 | 1,588 | 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.
@dialecticofsolitude · 36,340
Telegram ranks this channel #86 of 88 here — alongside 87 others — read 1 September 2026
This channel appears in 1 seed channel's Telegram-generated recommendation list 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 26 September 2026 — this entry's latest reading, not the date you are reading this.
“Radio Music 📻 ❄️” (@RadioMusicRock), 1,593 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/RadioMusicRock.
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.