Telegram RegisterThe public register of Telegram
Telegram profile photo for RuMp3 | Скачать Треки Поиск песни

Bot

RuMp3 | Скачать Треки Поиск песни

@RuMp3Bot

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

278,576monthly users

+67,398 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 100,000–316,228.

Register entry

Telegram ID8083208743
TypeBot
Username@RuMp3Bot
First recorded7 August 2026
Last confirmed live10 November 2026
Measurements held59
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/RuMp3Bot

Topic

Music — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 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

96,817278,576187,696.57 August 2026 — 211,178 monthly users7 August 2026 — 211,178 monthly users8 August 2026 — 212,541 monthly users9 August 2026 — 205,565 monthly users10 August 2026 — 197,128 monthly users11 August 2026 — 191,026 monthly users12 August 2026 — 185,684 monthly users13 August 2026 — 173,090 monthly users14 August 2026 — 168,901 monthly users16 August 2026 — 159,180 monthly users17 August 2026 — 154,947 monthly users18 August 2026 — 151,845 monthly users20 August 2026 — 147,532 monthly users21 August 2026 — 142,933 monthly users22 August 2026 — 136,539 monthly users24 August 2026 — 121,506 monthly users25 August 2026 — 122,032 monthly users26 August 2026 — 121,008 monthly users27 August 2026 — 119,687 monthly users28 August 2026 — 118,367 monthly users29 August 2026 — 117,317 monthly users30 August 2026 — 116,180 monthly users1 September 2026 — 114,567 monthly users2 September 2026 — 109,421 monthly users4 September 2026 — 105,363 monthly users6 September 2026 — 102,331 monthly users10 September 2026 — 97,336 monthly users12 September 2026 — 97,025 monthly users14 September 2026 — 96,817 monthly users15 September 2026 — 96,867 monthly users17 September 2026 — 96,835 monthly users28 September 2026 — 179,882 monthly users5 October 2026 — 203,616 monthly users9 October 2026 — 228,540 monthly users13 October 2026 — 233,672 monthly users14 October 2026 — 236,160 monthly users15 October 2026 — 239,768 monthly users16 October 2026 — 241,540 monthly users17 October 2026 — 246,331 monthly users18 October 2026 — 248,389 monthly users20 October 2026 — 248,833 monthly users21 October 2026 — 234,421 monthly users22 October 2026 — 234,828 monthly users23 October 2026 — 218,946 monthly users24 October 2026 — 211,429 monthly users25 October 2026 — 194,503 monthly users26 October 2026 — 191,752 monthly users28 October 2026 — 187,708 monthly users29 October 2026 — 182,385 monthly users30 October 2026 — 172,902 monthly users31 October 2026 — 172,303 monthly users1 November 2026 — 171,345 monthly users3 November 2026 — 191,396 monthly users4 November 2026 — 211,209 monthly users5 November 2026 — 225,473 monthly users6 November 2026 — 238,019 monthly users7 November 2026 — 248,442 monthly users8 November 2026 — 268,093 monthly users10 November 2026 — 278,576 monthly users7 August 202610 November 2026
59 measurements spanning 95 days, net +67,398. 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 69,553–305,840 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 59
Measured (UTC)Monthly usersChange
10 Nov 2026, 07:50278,576+10,483
8 Nov 2026, 17:57268,093+19,651
7 Nov 2026, 08:06248,442+10,423
6 Nov 2026, 09:45238,019+12,546
5 Nov 2026, 08:20225,473+14,264
4 Nov 2026, 06:18211,209+19,813
3 Nov 2026, 06:34191,396+20,051
1 Nov 2026, 09:10171,345-958
31 Oct 2026, 08:19172,303-599
30 Oct 2026, 11:41172,902-9,483
29 Oct 2026, 14:55182,385-5,323
28 Oct 2026, 12:59187,708-4,044
26 Oct 2026, 17:08191,752-2,751
25 Oct 2026, 15:12194,503-16,926
24 Oct 2026, 12:10211,429-7,517
23 Oct 2026, 11:28218,946-15,882
22 Oct 2026, 10:15234,828+407
21 Oct 2026, 04:31234,421-14,412
20 Oct 2026, 00:11248,833+444
18 Oct 2026, 21:06248,389first 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 12 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 10 November 2026 — this entry's latest reading, not the date you are reading this.

“RuMp3 | Скачать Треки Поиск песни” (@RuMp3Bot), 278,576 monthly users as measured 10 November 2026. Telegram Register, tgregister.com/channel/RuMp3Bot.

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.