Telegram RegisterThe public register of Telegram
Telegram profile photo for Search Music πŸ”

Bot

Search Music πŸ”

@Whatssmusiicbot

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

27,623monthly users

-7,331 since we began measuring on 10 August 2026

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

Register entry

Telegram ID6754339838
TypeBot
Username@Whatssmusiicbot
First recorded13 August 2026
Last confirmed live16 October 2026
Measurements held33
Confirmed unchanged1 time, most recently 16 October 2026
On Telegramt.me/Whatssmusiicbot

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 96% 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

27,62334,95431,288.510 August 2026 β€” 34,954 monthly users11 August 2026 β€” 34,876 monthly users12 August 2026 β€” 34,873 monthly users13 August 2026 β€” 34,467 monthly users13 August 2026 β€” 34,467 monthly users14 August 2026 β€” 34,333 monthly users16 August 2026 β€” 34,254 monthly users17 August 2026 β€” 33,908 monthly users18 August 2026 β€” 33,671 monthly users20 August 2026 β€” 33,433 monthly users21 August 2026 β€” 33,178 monthly users23 August 2026 β€” 32,628 monthly users25 August 2026 β€” 32,030 monthly users26 August 2026 β€” 31,744 monthly users27 August 2026 β€” 31,360 monthly users29 August 2026 β€” 31,145 monthly users30 August 2026 β€” 31,001 monthly users31 August 2026 β€” 30,667 monthly users1 September 2026 β€” 30,507 monthly users4 September 2026 β€” 30,306 monthly users6 September 2026 β€” 30,400 monthly users9 September 2026 β€” 29,984 monthly users12 September 2026 β€” 29,843 monthly users13 September 2026 β€” 29,737 monthly users15 September 2026 β€” 29,733 monthly users17 September 2026 β€” 29,533 monthly users28 September 2026 β€” 28,794 monthly users5 October 2026 β€” 28,764 monthly users9 October 2026 β€” 28,238 monthly users13 October 2026 β€” 28,014 monthly users14 October 2026 β€” 27,942 monthly users15 October 2026 β€” 27,818 monthly users16 October 2026 β€” 27,623 monthly users10 August 202616 October 2026
33 measurements spanning 67 days, net -7,331. 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,523–36,054 and does not start at zero.
Measurement log β€” every monthly users count we have recorded, most recent 20 of 33
Measured (UTC)Monthly usersChange
16 Oct 2026, 18:0627,623-195
15 Oct 2026, 19:3127,818-124
14 Oct 2026, 20:3627,942-72
13 Oct 2026, 14:4528,014-224
9 Oct 2026, 13:3828,238-526
5 Oct 2026, 03:5828,764-30
28 Sept 2026, 10:5928,794-739
17 Sept 2026, 17:5529,533-200
15 Sept 2026, 12:5829,733-4
13 Sept 2026, 21:1929,737-106
12 Sept 2026, 02:3629,843-141
9 Sept 2026, 21:1829,984-416
6 Sept 2026, 16:1630,400+94
4 Sept 2026, 06:1830,306-201
1 Sept 2026, 20:4230,507-160
31 Aug 2026, 19:0830,667-334
30 Aug 2026, 17:1531,001-144
29 Aug 2026, 14:3431,145-215
27 Aug 2026, 17:0831,360-384
26 Aug 2026, 17:2531,744first 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 1 registered channel β€” 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.

Named by

Channels on the register whose posts name this channel's handle.

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 16 October 2026 β€” this entry's latest reading, not the date you are reading this.

β€œSearch Music πŸ”β€ (@Whatssmusiicbot), 27,623 monthly users as measured 16 October 2026. Telegram Register, tgregister.com/channel/Whatssmusiicbot.

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.