Telegram RegisterThe public register of Telegram
Telegram profile photo for VK Music - Музыка из ВК

Bot

VK Music - Музыка из ВК

@VKMusicalRobot

On this record: Topic · Growth · Engagement · Citations · Cite this entry

30,501monthly users

-1,990 since we began measuring on 8 August 2026

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

Register entry

Telegram ID6795502581
TypeBot
Username@VKMusicalRobot
First recorded13 August 2026
Last confirmed live6 November 2026
Measurements held41
Confirmed unchanged2 times, most recently 6 November 2026
On Telegramt.me/VKMusicalRobot

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 9 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

27,08132,63529,8588 August 2026 — 32,491 monthly users9 August 2026 — 32,446 monthly users11 August 2026 — 32,367 monthly users13 August 2026 — 32,367 monthly users14 August 2026 — 32,156 monthly users15 August 2026 — 32,130 monthly users17 August 2026 — 32,195 monthly users18 August 2026 — 32,277 monthly users20 August 2026 — 32,314 monthly users22 August 2026 — 32,278 monthly users25 August 2026 — 32,266 monthly users27 August 2026 — 32,534 monthly users28 August 2026 — 32,635 monthly users29 August 2026 — 32,556 monthly users1 September 2026 — 32,467 monthly users5 September 2026 — 31,921 monthly users8 September 2026 — 31,825 monthly users11 September 2026 — 31,275 monthly users12 September 2026 — 30,985 monthly users16 September 2026 — 30,490 monthly users18 September 2026 — 30,155 monthly users2 October 2026 — 27,101 monthly users7 October 2026 — 27,092 monthly users11 October 2026 — 27,081 monthly users14 October 2026 — 27,179 monthly users16 October 2026 — 27,307 monthly users17 October 2026 — 27,189 monthly users18 October 2026 — 27,172 monthly users20 October 2026 — 27,356 monthly users21 October 2026 — 27,332 monthly users22 October 2026 — 27,266 monthly users24 October 2026 — 27,244 monthly users25 October 2026 — 27,535 monthly users27 October 2026 — 27,861 monthly users29 October 2026 — 28,563 monthly users30 October 2026 — 28,788 monthly users31 October 2026 — 29,075 monthly users1 November 2026 — 29,408 monthly users2 November 2026 — 29,751 monthly users4 November 2026 — 30,310 monthly users5 November 2026 — 30,501 monthly users30,5018 August 20265 November 2026
41 measurements spanning 89 days, net -1,990. 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 26,248–33,468 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 41
Measured (UTC)Monthly usersChange
5 Nov 2026, 11:3630,501+191
4 Nov 2026, 10:2130,310+559
2 Nov 2026, 12:1529,751+343
1 Nov 2026, 11:1629,408+333
31 Oct 2026, 09:4529,075+287
30 Oct 2026, 07:0828,788+225
29 Oct 2026, 06:5928,563+702
27 Oct 2026, 01:0727,861+326
25 Oct 2026, 22:5127,535+291
24 Oct 2026, 20:0927,244-22
22 Oct 2026, 19:4727,266-66
21 Oct 2026, 15:3927,332-24
20 Oct 2026, 08:5627,356+184
18 Oct 2026, 09:3527,172-17
17 Oct 2026, 07:0927,189-118
16 Oct 2026, 05:5927,307+128
14 Oct 2026, 03:0427,179+98
11 Oct 2026, 18:3827,081-11
7 Oct 2026, 06:0127,092-9
2 Oct 2026, 06:1827,101first reading

Engagement

No post feed to measure. Telegram publishes a readable post stream for channels, not for bots, so views, reactions and engagement rates do not exist for this entry — they are not missing, pending or withheld. The register records what this handle is and what it resolves to.

Forward network

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 7 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

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.

“VK Music - Музыка из ВК” (@VKMusicalRobot), 30,501 monthly users as measured 5 November 2026. Telegram Register, tgregister.com/channel/VKMusicalRobot.

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.