Telegram RegisterThe public register of Telegram
Telegram profile photo for Kumyk Muz🎵

Channel

Kumyk Muz🎵

@kumykmuz

On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry

4,668subscribers

+64 since we began measuring on 1 October 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001531628978
TypeChannel
Username@kumykmuz
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded1 October 2026
Last confirmed live5 November 2026
Measurements held11
Confirmed unchanged1 time, most recently 5 November 2026
On Telegramt.me/kumykmuz

Topic

Music — a classification, not a measurement. An on-box language model (qwen3.6:35b-a3b, prompt version 1) read this channel’s own recent posts on 18 October 2026 and assigned it the closest of 31 fixed categories, at 98% 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

4,6044,6684,6361 October 2026 — 4,604 subscribers6 October 2026 — 4,605 subscribers12 October 2026 — 4,625 subscribers15 October 2026 — 4,623 subscribers18 October 2026 — 4,624 subscribers21 October 2026 — 4,629 subscribers24 October 2026 — 4,635 subscribers27 October 2026 — 4,639 subscribers30 October 2026 — 4,653 subscribers2 November 2026 — 4,659 subscribers5 November 2026 — 4,668 subscribers1 October 20265 November 2026
11 measurements spanning 34 days, net +64. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 4,594–4,678 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Nov 2026, 06:464,668+9
2 Nov 2026, 04:594,659+6
30 Oct 2026, 02:314,653+14
27 Oct 2026, 03:094,639+4
24 Oct 2026, 12:574,635+6
21 Oct 2026, 17:174,629+5
18 Oct 2026, 17:104,624+1
15 Oct 2026, 08:374,623-2
12 Oct 2026, 16:364,625+20
6 Oct 2026, 08:024,605+1
1 Oct 2026, 23:504,604first 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.

КУМЫКСКИЕ ПЕСНИ❤️
@Kumykskie_pesni05 · 19,799
Telegram ranks this channel #2 of 48 here — alongside 47 others — read 1 October 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 5 November 2026 — this entry's latest reading, not the date you are reading this.

“Kumyk Muz🎵” (@kumykmuz), 4,668 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/kumykmuz.

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.