Telegram RegisterThe public register of Telegram
Telegram profile photo for Telegram Watchdog

Bot

Telegram Watchdog

@WatchdogVerifyBot

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

34,967monthly users

+1,117 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 ID1171095858
TypeBot
Username@WatchdogVerifyBot
First recorded13 August 2026
Last confirmed live5 September 2026
Measurements held16
Confirmed unchanged2 times, most recently 5 September 2026
On Telegramt.me/WatchdogVerifyBot

Growth

33,39834,96734,182.57 August 2026 — 33,850 monthly users10 August 2026 — 34,320 monthly users12 August 2026 — 34,447 monthly users13 August 2026 — 34,447 monthly users14 August 2026 — 34,680 monthly users17 August 2026 — 33,525 monthly users18 August 2026 — 33,678 monthly users19 August 2026 — 34,054 monthly users21 August 2026 — 33,398 monthly users24 August 2026 — 34,699 monthly users26 August 2026 — 34,599 monthly users27 August 2026 — 34,573 monthly users28 August 2026 — 33,730 monthly users30 August 2026 — 34,793 monthly users1 September 2026 — 34,780 monthly users3 September 2026 — 34,967 monthly users7 August 20263 September 2026
16 measurements spanning 28 days, net +1,117. 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 33,163–35,202 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
3 Sept 2026, 18:0034,967+187
1 Sept 2026, 15:5434,780-13
30 Aug 2026, 12:1634,793+1,063
28 Aug 2026, 11:3533,730-843
27 Aug 2026, 14:0534,573-26
26 Aug 2026, 13:5334,599-100
24 Aug 2026, 18:0834,699+1,301
21 Aug 2026, 16:2533,398-656
19 Aug 2026, 16:3434,054+376
18 Aug 2026, 13:3333,678+153
17 Aug 2026, 14:2433,525-1,155
14 Aug 2026, 17:3734,680+233
13 Aug 2026, 19:1034,447no change
12 Aug 2026, 04:3334,447+127
10 Aug 2026, 01:0434,320+470
7 Aug 2026, 02:1633,850first 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 5 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 3 September 2026 — this entry's latest reading, not the date you are reading this.

“Telegram Watchdog” (@WatchdogVerifyBot), 34,967 monthly users as measured 3 September 2026. Telegram Register, tgregister.com/channel/WatchdogVerifyBot.

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.