Bot
TGuard
@channel_guardian_bot
On this record: Growth · Engagement · Citations · Cite this entry
32,236monthly users
+15,477 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 ID | 6370966685 |
|---|---|
| Type | Bot |
| Username | @channel_guardian_bot |
| First recorded | 16 August 2026 |
| Last confirmed live | 17 August 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 17 August 2026 |
| On Telegram | t.me/channel_guardian_bot |
Growth
| Measured (UTC) | Monthly users | Change |
|---|---|---|
| 17 Aug 2026, 12:24 | 32,236 | +9,273 |
| 16 Aug 2026, 16:03 | 22,963 | no change |
| 16 Aug 2026, 03:53 | 22,963 | +4,594 |
| 14 Aug 2026, 13:14 | 18,369 | +427 |
| 11 Aug 2026, 23:31 | 17,942 | +857 |
| 9 Aug 2026, 01:11 | 17,085 | +301 |
| 6 Aug 2026, 23:40 | 16,784 | +25 |
| 6 Aug 2026, 12:16 | 16,759 | first 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 66 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.
Named by
Channels on the register whose posts name this channel's handle.
@Wicca_Pagan_Datings · 6,11836 posts缅甸风景 | မြန်မာရှုခင်း
@MyanMar980412 · 57,0354 posts全网华人悬赏-曝光-吃瓜
@qwhrxsbgcg · 264,4423 posts世界杯足球推单
@SJB00001 · 14,5323 postsУголок админа | Дмитрий Толстой
@tg_adminpro · 6,5793 postsрест!адский.
@ADSK1YY · 142 posts모아 .^ AMOAfam @ Fm.725
@amoafam · 142 postsзакрыт
@avroraa555 · 92 postsTGuard • Защита от накрутки
@channel_guardian_channel · 2,5212 posts( 蝕 )’ ξϲɭʝρʂε ᵐᶦˣ ᵍʳᵒᵘᵖ📷
@elipsero · 32 postsвинчестеры
@grekkaaf · 162 postsПЕРЕЕЗД
@Help_From_Meka · 362 posts#
@K1XA6 · 532 postsT1qwsss
@kakahalala1488 · 12 postsMadrıd
@MadrFam · 42 posts𝘷𝘪𝘳𝘵 𝘯𝘶𝘮𝘣𝘦𝘳 𝘮𝘢𝘵𝘵
@mitkills · 2382 postsRequag временно закрыты
@requag · 392 posts𝙍𝙐𝙎 𝘾𝙇𝘼𝙉 𝙄 𝙉𝙀𝙒𝙎
@RUS_CLAN_GB · 212 postsРЕСТᅠ𓏏𓏏 𝗌𝖾𝗆𝗂 𝖼𝖿 ﹠ 𝖽𝖺𝗂𝗅𝗒 ִ ۫
@semicfdaily · 692 posts神回 ; 𝖳9𝗦𝗘R⃨ 🗯️ ??!
@t9ser_gg · 212 postsSHYNGYSOVY
@VezdeShyngysovy · 72 postsВладимир | Подписчики в канал
@vladimirdanila_official · 4372 postsW̸̢̅Ĩ͡P̟ͬ͠L̷̯I̢͘D̡̰͡
@wiplidfm · 112 posts.
@zalkarskiee · 62 posts
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 17 August 2026 — this entry's latest reading, not the date you are reading this.
“TGuard” (@channel_guardian_bot), 32,236 monthly users as measured 17 August 2026. Telegram Register, tgregister.com/channel/channel_guardian_bot.
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.