Telegram RegisterThe public register of Telegram
Telegram profile photo for 查u @chaU

Bot

查u @chaU

@AUBot

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

38,853monthly users

+4,370 since we began measuring on 19 August 2026

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

Register entry

Telegram ID832838289
TypeBot
Username@AUBot
First recorded20 August 2026
Last confirmed live17 September 2026
Measurements held10
Confirmed unchanged3 times, most recently 17 September 2026
On Telegramt.me/AUBot

Topic

Other / unclassifiable — 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 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 why it has no browse page of its own yet.

Growth

32,42142,55837,489.519 August 2026 — 34,483 monthly users20 August 2026 — 34,483 monthly users21 August 2026 — 34,327 monthly users24 August 2026 — 34,119 monthly users26 August 2026 — 33,831 monthly users29 August 2026 — 33,634 monthly users31 August 2026 — 33,385 monthly users6 September 2026 — 32,421 monthly users9 September 2026 — 42,558 monthly users13 September 2026 — 38,853 monthly users38,85319 August 202613 September 2026
10 measurements spanning 25 days, net +4,370. 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 30,900–44,079 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
13 Sept 2026, 20:1938,853-3,705
9 Sept 2026, 14:3542,558+10,137
6 Sept 2026, 03:2032,421-964
31 Aug 2026, 12:1433,385-249
29 Aug 2026, 13:1333,634-197
26 Aug 2026, 11:3333,831-288
24 Aug 2026, 07:2234,119-208
21 Aug 2026, 08:4634,327-156
20 Aug 2026, 09:4234,483no change
19 Aug 2026, 23:0034,483first 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.

Mentions

Named by 2 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 13 September 2026 — this entry's latest reading, not the date you are reading this.

“查u @chaU” (@AUBot), 38,853 monthly users as measured 13 September 2026. Telegram Register, tgregister.com/channel/AUBot.

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.