Channel
ХИТ КАВКАЗА ⛰
@kavkaz_musica
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,939subscribers
+3 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001297093751 |
|---|---|
| Type | Channel |
| Username | @kavkaz_musica |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 September 2026 |
| Last confirmed live | 27 September 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 27 September 2026 |
| On Telegram | t.me/kavkaz_musica |
Topic
Other / unclassifiable — 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 85% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Sept 2026, 07:57 | 2,939 | -7 |
| 18 Sept 2026, 02:19 | 2,946 | +1 |
| 13 Sept 2026, 13:59 | 2,945 | -2 |
| 11 Sept 2026, 23:54 | 2,947 | no change |
| 9 Sept 2026, 20:40 | 2,947 | +4 |
| 4 Sept 2026, 13:57 | 2,943 | -1 |
| 31 Aug 2026, 15:18 | 2,944 | +6 |
| 28 Aug 2026, 16:04 | 2,938 | +2 |
| 25 Aug 2026, 17:42 | 2,936 | -9 |
| 22 Aug 2026, 12:58 | 2,945 | -1 |
| 19 Aug 2026, 09:55 | 2,946 | -4 |
| 16 Aug 2026, 16:35 | 2,950 | +4 |
| 12 Aug 2026, 15:16 | 2,946 | +4 |
| 9 Aug 2026, 21:52 | 2,942 | +5 |
| 7 Aug 2026, 03:00 | 2,937 | +1 |
| 6 Aug 2026, 16:53 | 2,936 | 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.
@kavkaz_muz · 35,972
Telegram ranks this channel #10 of 76 here — alongside 75 others — read 2 September 2026
@new_muzyka_kavkaza · 22,802
Telegram ranks this channel #29 of 66 here — alongside 65 others — read 20 September 2026
This channel appears in 2 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 27 September 2026 — this entry's latest reading, not the date you are reading this.
“ХИТ КАВКАЗА ⛰” (@kavkaz_musica), 2,939 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/kavkaz_musica.
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.