Telegram RegisterThe public register of Telegram
Telegram profile photo for Whatsmusicbot | واتس موزیک

Bot

Whatsmusicbot | واتس موزیک

@What_smusic_Bot

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

11,642monthly users

-4,106 since we began measuring on 12 August 2026

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

Register entry

Telegram ID6484522393
TypeBot
Username@What_smusic_Bot
First recorded18 August 2026
Last confirmed live31 October 2026
Measurements held37
Confirmed unchanged1 time, most recently 31 October 2026
On Telegramt.me/What_smusic_Bot

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 10 September 2026 and assigned it the closest of 31 fixed categories, at 60% 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

11,64215,77913,710.512 August 2026 — 15,748 monthly users14 August 2026 — 15,715 monthly users15 August 2026 — 15,729 monthly users16 August 2026 — 15,742 monthly users17 August 2026 — 15,715 monthly users18 August 2026 — 15,715 monthly users19 August 2026 — 15,684 monthly users20 August 2026 — 15,641 monthly users23 August 2026 — 15,598 monthly users25 August 2026 — 15,497 monthly users26 August 2026 — 15,474 monthly users27 August 2026 — 15,491 monthly users28 August 2026 — 15,631 monthly users30 August 2026 — 15,759 monthly users31 August 2026 — 15,779 monthly users1 September 2026 — 15,421 monthly users2 September 2026 — 14,847 monthly users3 September 2026 — 14,765 monthly users5 September 2026 — 14,454 monthly users8 September 2026 — 14,098 monthly users11 September 2026 — 13,655 monthly users13 September 2026 — 13,079 monthly users16 September 2026 — 12,927 monthly users19 September 2026 — 12,948 monthly users25 September 2026 — 13,406 monthly users4 October 2026 — 13,548 monthly users8 October 2026 — 13,401 monthly users13 October 2026 — 13,379 monthly users15 October 2026 — 13,409 monthly users18 October 2026 — 13,412 monthly users19 October 2026 — 13,353 monthly users20 October 2026 — 13,160 monthly users23 October 2026 — 12,879 monthly users24 October 2026 — 12,650 monthly users27 October 2026 — 12,416 monthly users29 October 2026 — 11,983 monthly users31 October 2026 — 11,642 monthly users12 August 202631 October 2026
37 measurements spanning 80 days, net -4,106. 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 11,021–16,400 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 37
Measured (UTC)Monthly usersChange
31 Oct 2026, 02:1811,642-341
29 Oct 2026, 23:4711,983-433
27 Oct 2026, 04:2012,416-234
24 Oct 2026, 23:5712,650-229
23 Oct 2026, 00:3812,879-281
20 Oct 2026, 16:5613,160-193
19 Oct 2026, 16:4813,353-59
18 Oct 2026, 15:1113,412+3
15 Oct 2026, 16:3713,409+30
13 Oct 2026, 07:0513,379-22
8 Oct 2026, 23:1613,401-147
4 Oct 2026, 09:5613,548+142
25 Sept 2026, 19:5613,406+458
19 Sept 2026, 07:5612,948+21
16 Sept 2026, 22:4012,927-152
13 Sept 2026, 06:3613,079-576
11 Sept 2026, 05:5613,655-443
8 Sept 2026, 08:0114,098-356
5 Sept 2026, 00:2214,454-311
3 Sept 2026, 07:0514,765first 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 31 October 2026 — this entry's latest reading, not the date you are reading this.

“Whatsmusicbot | واتس موزیک” (@What_smusic_Bot), 11,642 monthly users as measured 31 October 2026. Telegram Register, tgregister.com/channel/What_smusic_Bot.

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.