Channel
π»πΎππ π¦πΆπππΆππΆπΆ
@khity_kavkaza
On this record: Topic Β· Growth Β· Engagement Β· Telegram's recommendations Β· Cite this entry
4,202subscribers
+140 since we began measuring on 7 August 2026
Risers and fallers across the register Β· movement among entries of 3,162β10,000.
Register entry
| Telegram ID | -1001934629618 |
|---|---|
| Type | Channel |
| Username | @khity_kavkaza |
| Created | Between 1 April 2023 and 31 October 2023 β estimated from Telegramβs id allocation, not measured. How this range is calculated. |
| First recorded | 4 September 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/khity_kavkaza |
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 13 September 2026 and assigned it the closest of 31 fixed categories, at 68% 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 |
|---|---|---|
| 6 Nov 2026, 20:17 | 4,202 | +5 |
| 3 Nov 2026, 17:51 | 4,197 | +15 |
| 31 Oct 2026, 20:37 | 4,182 | +2 |
| 29 Oct 2026, 03:18 | 4,180 | +12 |
| 26 Oct 2026, 06:45 | 4,168 | +10 |
| 23 Oct 2026, 15:39 | 4,158 | +4 |
| 20 Oct 2026, 12:04 | 4,154 | +3 |
| 17 Oct 2026, 18:37 | 4,151 | +10 |
| 14 Oct 2026, 15:54 | 4,141 | +6 |
| 11 Oct 2026, 10:38 | 4,135 | +17 |
| 4 Oct 2026, 21:37 | 4,118 | +18 |
| 25 Sept 2026, 08:21 | 4,100 | +25 |
| 15 Sept 2026, 09:01 | 4,075 | +5 |
| 11 Sept 2026, 23:00 | 4,070 | +6 |
| 7 Sept 2026, 18:21 | 4,064 | -21 |
| 4 Sept 2026, 23:52 | 4,085 | no change |
| 3 Sept 2026, 02:28 | 4,085 | +1 |
| 30 Aug 2026, 17:32 | 4,084 | +5 |
| 27 Aug 2026, 16:52 | 4,079 | -10 |
| 25 Aug 2026, 02:53 | 4,089 | 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 Β· 36,066
Telegram ranks this channel #7 of 76 here β alongside 75 others β read 2 September 2026
@rasulova_patimat Β· 25,713
Telegram ranks this channel #8 of 67 here β alongside 66 others β read 21 September 2026
@new_muzyka_kavkaza Β· 23,557
Telegram ranks this channel #21 of 66 here β alongside 65 others β read 20 September 2026
This channel appears in 4 seed channels' Telegram-generated recommendation lists in total, of which the 3 where it ranks highest are shown above. 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 6 November 2026 β this entry's latest reading, not the date you are reading this.
βπ»πΎππ π¦πΆπππΆππΆπΆβ (@khity_kavkaza), 4,202 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/khity_kavkaza.
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.