Channel
Russian music
@russianmusic_1
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,589subscribers
-129 since we began measuring on 1 September 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001508863540 |
|---|---|
| Type | Channel |
| Username | @russianmusic_1 |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 September 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/russianmusic_1 |
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 18 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 |
|---|---|---|
| 7 Nov 2026, 00:50 | 2,589 | -10 |
| 3 Nov 2026, 15:29 | 2,599 | -7 |
| 31 Oct 2026, 08:54 | 2,606 | -5 |
| 27 Oct 2026, 23:07 | 2,611 | -4 |
| 24 Oct 2026, 18:39 | 2,615 | -11 |
| 21 Oct 2026, 13:58 | 2,626 | -15 |
| 18 Oct 2026, 01:21 | 2,641 | -4 |
| 15 Oct 2026, 05:46 | 2,645 | -7 |
| 12 Oct 2026, 04:58 | 2,652 | -1 |
| 5 Oct 2026, 13:40 | 2,653 | -18 |
| 27 Sept 2026, 11:39 | 2,671 | -16 |
| 18 Sept 2026, 13:20 | 2,687 | -13 |
| 14 Sept 2026, 00:06 | 2,700 | no change |
| 13 Sept 2026, 23:19 | 2,700 | -6 |
| 10 Sept 2026, 05:55 | 2,706 | -8 |
| 5 Sept 2026, 03:57 | 2,714 | -4 |
| 1 Sept 2026, 11:30 | 2,718 | 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.
@m_a_s_o_u_di · 42,143
Telegram ranks this channel #46 of 54 here — alongside 53 others — read 1 September 2026
@PayamnoriaData · 21,875
Telegram ranks this channel #61 of 68 here — alongside 67 others — read 22 September 2026
@divar_neveshtha · 20,058
Telegram ranks this channel #74 of 84 here — alongside 83 others — read 28 September 2026
This channel appears in 3 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 7 November 2026 — this entry's latest reading, not the date you are reading this.
“Russian music” (@russianmusic_1), 2,589 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/russianmusic_1.
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.