Telegram RegisterThe public register of Telegram

Bot

Whatmusicbot

@Whatbehibot

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

39,184monthly users

-1,135 since we began measuring on 7 August 2026

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

Register entry

Telegram ID6776543588
TypeBot
Username@Whatbehibot
First recorded12 August 2026
Last confirmed live14 November 2026
Measurements held60
Confirmed unchanged1 time, most recently 14 November 2026
On Telegramt.me/Whatbehibot

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

38,17140,31939,2457 August 2026 — 40,319 monthly users8 August 2026 — 39,962 monthly users9 August 2026 — 40,303 monthly users11 August 2026 — 40,257 monthly users12 August 2026 — 40,200 monthly users12 August 2026 — 40,200 monthly users13 August 2026 — 40,137 monthly users14 August 2026 — 40,145 monthly users15 August 2026 — 40,265 monthly users17 August 2026 — 40,276 monthly users18 August 2026 — 40,313 monthly users19 August 2026 — 40,295 monthly users20 August 2026 — 39,917 monthly users21 August 2026 — 40,063 monthly users22 August 2026 — 40,059 monthly users24 August 2026 — 39,986 monthly users25 August 2026 — 39,848 monthly users26 August 2026 — 39,751 monthly users27 August 2026 — 39,716 monthly users28 August 2026 — 39,703 monthly users29 August 2026 — 39,686 monthly users30 August 2026 — 39,635 monthly users1 September 2026 — 39,561 monthly users2 September 2026 — 39,492 monthly users4 September 2026 — 39,502 monthly users6 September 2026 — 39,602 monthly users9 September 2026 — 39,600 monthly users12 September 2026 — 39,567 monthly users13 September 2026 — 39,587 monthly users15 September 2026 — 39,137 monthly users17 September 2026 — 39,358 monthly users19 September 2026 — 39,322 monthly users26 September 2026 — 39,192 monthly users4 October 2026 — 38,754 monthly users9 October 2026 — 38,740 monthly users13 October 2026 — 38,726 monthly users14 October 2026 — 38,710 monthly users15 October 2026 — 38,484 monthly users16 October 2026 — 38,772 monthly users17 October 2026 — 38,765 monthly users18 October 2026 — 38,783 monthly users19 October 2026 — 38,744 monthly users20 October 2026 — 38,685 monthly users22 October 2026 — 38,569 monthly users23 October 2026 — 38,571 monthly users24 October 2026 — 38,253 monthly users25 October 2026 — 38,247 monthly users26 October 2026 — 38,171 monthly users27 October 2026 — 38,348 monthly users29 October 2026 — 38,306 monthly users30 October 2026 — 38,316 monthly users31 October 2026 — 38,456 monthly users2 November 2026 — 38,445 monthly users3 November 2026 — 38,483 monthly users5 November 2026 — 38,506 monthly users7 November 2026 — 38,666 monthly users8 November 2026 — 38,775 monthly users9 November 2026 — 38,967 monthly users11 November 2026 — 38,979 monthly users14 November 2026 — 39,184 monthly users39,1847 August 202614 November 2026
60 measurements spanning 100 days, net -1,135. 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 37,849–40,641 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 60
Measured (UTC)Monthly usersChange
14 Nov 2026, 16:1539,184+205
11 Nov 2026, 15:0838,979+12
9 Nov 2026, 20:0938,967+192
8 Nov 2026, 09:1938,775+109
7 Nov 2026, 03:5938,666+160
5 Nov 2026, 01:0538,506+23
3 Nov 2026, 21:5638,483+38
2 Nov 2026, 18:2038,445-11
31 Oct 2026, 19:1838,456+140
30 Oct 2026, 16:1738,316+10
29 Oct 2026, 12:3938,306-42
27 Oct 2026, 15:2138,348+177
26 Oct 2026, 12:4038,171-76
25 Oct 2026, 09:5538,247-6
24 Oct 2026, 08:4738,253-318
23 Oct 2026, 07:1938,571+2
22 Oct 2026, 07:3438,569-116
20 Oct 2026, 22:1938,685-59
19 Oct 2026, 20:2738,744-39
18 Oct 2026, 17:4938,783first 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 6 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 14 November 2026 — this entry's latest reading, not the date you are reading this.

“Whatmusicbot” (@Whatbehibot), 39,184 monthly users as measured 14 November 2026. Telegram Register, tgregister.com/channel/Whatbehibot.

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.