Telegram RegisterThe public register of Telegram
Telegram profile photo for Controller Bot

Bot

Controller Bot

@ControllerBot

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

306,557monthly users

+68,400 since we began measuring on 5 August 2026

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

Register entry

Telegram ID200942125
TypeBot
Username@ControllerBot
First recorded6 August 2026
Last confirmed live11 November 2026
Measurements held55
Confirmed unchanged1 time, most recently 11 November 2026
On Telegramt.me/ControllerBot

Topic

Other / unclassifiable — 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

223,399306,557264,9785 August 2026 — 238,157 monthly users6 August 2026 — 238,157 monthly users7 August 2026 — 228,237 monthly users9 August 2026 — 234,078 monthly users10 August 2026 — 232,918 monthly users11 August 2026 — 223,399 monthly users12 August 2026 — 229,107 monthly users14 August 2026 — 228,531 monthly users15 August 2026 — 227,389 monthly users16 August 2026 — 224,746 monthly users17 August 2026 — 224,535 monthly users19 August 2026 — 224,565 monthly users20 August 2026 — 224,408 monthly users22 August 2026 — 224,301 monthly users23 August 2026 — 224,224 monthly users25 August 2026 — 224,763 monthly users26 August 2026 — 228,281 monthly users27 August 2026 — 224,580 monthly users28 August 2026 — 226,798 monthly users30 August 2026 — 235,621 monthly users31 August 2026 — 236,803 monthly users2 September 2026 — 239,589 monthly users3 September 2026 — 240,469 monthly users5 September 2026 — 243,398 monthly users8 September 2026 — 244,506 monthly users11 September 2026 — 247,949 monthly users13 September 2026 — 248,920 monthly users14 September 2026 — 243,810 monthly users16 September 2026 — 252,434 monthly users19 September 2026 — 254,855 monthly users25 September 2026 — 257,056 monthly users3 October 2026 — 247,999 monthly users8 October 2026 — 247,414 monthly users12 October 2026 — 247,524 monthly users14 October 2026 — 247,506 monthly users15 October 2026 — 247,789 monthly users16 October 2026 — 246,594 monthly users18 October 2026 — 247,077 monthly users19 October 2026 — 247,989 monthly users21 October 2026 — 240,579 monthly users22 October 2026 — 249,002 monthly users23 October 2026 — 249,331 monthly users26 October 2026 — 243,612 monthly users26 October 2026 — 261,510 monthly users28 October 2026 — 264,290 monthly users29 October 2026 — 260,197 monthly users31 October 2026 — 277,125 monthly users1 November 2026 — 282,375 monthly users2 November 2026 — 287,947 monthly users3 November 2026 — 286,197 monthly users5 November 2026 — 301,768 monthly users7 November 2026 — 303,954 monthly users8 November 2026 — 304,421 monthly users9 November 2026 — 304,859 monthly users11 November 2026 — 306,557 monthly users5 August 202611 November 2026
55 measurements spanning 98 days, net +68,400. 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 210,925–319,031 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 55
Measured (UTC)Monthly usersChange
11 Nov 2026, 11:18306,557+1,698
9 Nov 2026, 18:01304,859+438
8 Nov 2026, 10:37304,421+467
7 Nov 2026, 03:05303,954+2,186
5 Nov 2026, 03:17301,768+15,571
3 Nov 2026, 07:07286,197-1,750
2 Nov 2026, 10:16287,947+5,572
1 Nov 2026, 07:18282,375+5,250
31 Oct 2026, 06:55277,125+16,928
29 Oct 2026, 04:30260,197-4,093
28 Oct 2026, 00:26264,290+2,780
26 Oct 2026, 23:17261,510+17,898
26 Oct 2026, 02:45243,612-5,719
23 Oct 2026, 20:34249,331+329
22 Oct 2026, 20:50249,002+8,423
21 Oct 2026, 19:59240,579-7,410
19 Oct 2026, 16:16247,989+912
18 Oct 2026, 14:28247,077+483
16 Oct 2026, 14:39246,594-1,195
15 Oct 2026, 11:28247,789first 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 135 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

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 11 November 2026 — this entry's latest reading, not the date you are reading this.

“Controller Bot” (@ControllerBot), 306,557 monthly users as measured 11 November 2026. Telegram Register, tgregister.com/channel/ControllerBot.

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.