Telegram RegisterThe public register of Telegram
Telegram profile photo for ↻ DIGI ANTI ⇦

Bot

↻ DIGI ANTI ⇦

@digianti0bot

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

92,294monthly users

-570 since we began measuring on 6 August 2026

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

Register entry

Telegram ID691147834
TypeBot
Username@digianti0bot
First recorded10 August 2026
Last confirmed live3 September 2026
Measurements held18
Confirmed unchanged1 time, most recently 3 September 2026
On Telegramt.me/digianti0bot

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 21 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 why it has no browse page of its own yet.

Growth

92,29494,58193,437.56 August 2026 — 92,864 monthly users9 August 2026 — 93,166 monthly users10 August 2026 — 93,166 monthly users10 August 2026 — 93,190 monthly users11 August 2026 — 93,746 monthly users12 August 2026 — 93,826 monthly users14 August 2026 — 93,898 monthly users16 August 2026 — 93,950 monthly users18 August 2026 — 94,581 monthly users21 August 2026 — 94,496 monthly users23 August 2026 — 94,375 monthly users24 August 2026 — 94,087 monthly users26 August 2026 — 93,893 monthly users27 August 2026 — 93,505 monthly users29 August 2026 — 93,203 monthly users31 August 2026 — 92,405 monthly users1 September 2026 — 92,362 monthly users3 September 2026 — 92,294 monthly users6 August 20263 September 2026
18 measurements spanning 28 days, net -570. 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 91,951–94,924 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
3 Sept 2026, 23:1892,294-68
1 Sept 2026, 13:4692,362-43
31 Aug 2026, 10:3792,405-798
29 Aug 2026, 13:1893,203-302
27 Aug 2026, 19:3493,505-388
26 Aug 2026, 18:0693,893-194
24 Aug 2026, 17:5494,087-288
23 Aug 2026, 01:0394,375-121
21 Aug 2026, 11:4794,496-85
18 Aug 2026, 11:5694,581+631
16 Aug 2026, 08:1793,950+52
14 Aug 2026, 20:5593,898+72
12 Aug 2026, 16:0493,826+80
11 Aug 2026, 16:0893,746+556
10 Aug 2026, 19:3693,190+24
10 Aug 2026, 17:0293,166no change
9 Aug 2026, 16:0293,166+302
6 Aug 2026, 19:1592,864first 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.

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

“↻ DIGI ANTI ⇦” (@digianti0bot), 92,294 monthly users as measured 3 September 2026. Telegram Register, tgregister.com/channel/digianti0bot.

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.