Channel
Русские хиты | Музыка | Песни
@muzyka39
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,737subscribers
-211 since we began measuring on 28 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001454394714 |
|---|---|
| Type | Channel |
| Username | @muzyka39 |
| Created | Between 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 September 2026 |
| Last confirmed live | 8 November 2026 |
| Measurements held | 19 |
| Confirmed unchanged | 1 time, most recently 8 November 2026 |
| On Telegram | t.me/muzyka39 |
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 15 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Nov 2026, 12:50 | 2,737 | -16 |
| 5 Nov 2026, 12:59 | 2,753 | -9 |
| 2 Nov 2026, 18:37 | 2,762 | -8 |
| 30 Oct 2026, 18:31 | 2,770 | -10 |
| 27 Oct 2026, 23:39 | 2,780 | -5 |
| 24 Oct 2026, 22:20 | 2,785 | -5 |
| 22 Oct 2026, 01:09 | 2,790 | -14 |
| 18 Oct 2026, 17:16 | 2,804 | -7 |
| 15 Oct 2026, 11:19 | 2,811 | -12 |
| 12 Oct 2026, 11:39 | 2,823 | -20 |
| 5 Oct 2026, 08:00 | 2,843 | -22 |
| 26 Sept 2026, 22:38 | 2,865 | -22 |
| 17 Sept 2026, 13:54 | 2,887 | -8 |
| 13 Sept 2026, 19:54 | 2,895 | -8 |
| 12 Sept 2026, 01:19 | 2,903 | no change |
| 10 Sept 2026, 03:55 | 2,903 | -22 |
| 4 Sept 2026, 13:20 | 2,925 | -11 |
| 31 Aug 2026, 18:55 | 2,936 | -12 |
| 28 Aug 2026, 01:45 | 2,948 | 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.
@khity2 · 27,618
Telegram ranks this channel #28 of 85 here — alongside 84 others — read 8 September 2026
@ai_buddy_channel · 47,612
Telegram ranks this channel #54 of 55 here — alongside 54 others — read 4 October 2026
@freebitcoin_fun_holder · 81,036
Telegram ranks this channel #73 of 73 here — alongside 72 others — read 28 August 2026
@ScanCryptoSeed · 88,401
Telegram ranks this channel #81 of 82 here — alongside 81 others — read 28 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 8 November 2026 — this entry's latest reading, not the date you are reading this.
“Русские хиты | Музыка | Песни” (@muzyka39), 2,737 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/muzyka39.
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.