Bot
ChatKeeperBot
@ChatKeeperBot
On this record: Topic · Growth · Engagement · Citations · Cite this entry
499,544monthly users
+8,364 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 316,228–1,000,000.
Register entry
| Telegram ID | 553147242 |
|---|---|
| Type | Bot |
| Username | @ChatKeeperBot |
| First recorded | 6 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 22 August 2026 |
| On Telegram | t.me/ChatKeeperBot |
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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Monthly users | Change |
|---|---|---|
| 22 Aug 2026, 00:37 | 499,544 | +4,343 |
| 19 Aug 2026, 20:33 | 495,201 | +2,982 |
| 18 Aug 2026, 17:15 | 492,219 | +707 |
| 17 Aug 2026, 19:43 | 491,512 | -3,126 |
| 16 Aug 2026, 15:46 | 494,638 | +14,057 |
| 14 Aug 2026, 23:34 | 480,581 | +3,464 |
| 13 Aug 2026, 15:36 | 477,117 | -12,491 |
| 12 Aug 2026, 15:58 | 489,608 | -403 |
| 11 Aug 2026, 18:38 | 490,011 | -2,959 |
| 10 Aug 2026, 19:31 | 492,970 | -1,912 |
| 8 Aug 2026, 20:20 | 494,882 | -537 |
| 7 Aug 2026, 17:37 | 495,419 | +3,038 |
| 6 Aug 2026, 18:21 | 492,381 | no change |
| 6 Aug 2026, 16:27 | 492,381 | +1,201 |
| 5 Aug 2026, 22:06 | 491,180 | 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
@mega_skidon · 14 postsfleur_delana
@fleurdelana · 71 post☠️From😢Rags🤔To😃Riches💰
@fromragstorichies · 391 postHAVAL M6 | ХАВАЛ М6
@havalm6ru · 1,1201 postИзбранное ВТрезвости (По методу Шичко)
@izbrannoe_vtrezvosti · 6261 postKapitalelectro
@kapitalelectro · 11 postМедПункт Cʜᴀɴᴇʟ
@MadPCh · 201 post•𝗠𝗲𝗹𝗶𝗼𝗱•
@meliodiii · 81 postPhuket4you - твой Пхукет! | Thailand Тайланд
@phuket2you · 51 postᛒᛊᚳᛜ℥ᚴᛊᛒᛜ
@velozuevo_OZ · 2001 post🇺🇦Военная Барахолка
@wartacticrheone · 21 postX-profit
@xprofitmk · 11 post
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 84 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.
@ChatKeeperBotNews · 16,40089 postsChatKeeperBot News
@ChatKeeperBotEN · 11,20478 postsСеть культурных каналов
@iturksar · 15218 postsтест пересылки
@transfertest89 · 214 postsBOTLIST
@botlist · 71,24713 postsChatKeeperBot Yangiliklar
@ChatKeeperBotUZ · 7213 postsКаналы Telegram - каталог
@chagram · 24,6536 postsОбзорчик+ | Боты и Mini Apps
@ObzorchikPlus · 5,3314 postsУголок админа | Дмитрий Толстой
@tg_adminpro · 6,5723 postsОбучающее 📽 видео • Видеоуроки, видеокурсы, вебинары, семинары, тренинги, конференции, мастер-классы, лекции, обзоры, подкасты
@videolessons · 1,1533 postsقروب تمليك النهدي
@aliradioxox · 72 postsYTK CAPITAL - Инвестиционное Аналитическое Агенство
@BinaryOptionsTradingSignal · 82 postsАдминские чаты в Telegram
@chatileo · 3,8222 postsНужное
@dachnygnoe · 12 postsEPIC 💩 FAIL
@epicfailz · 122 postsКРОТ
@krot_tg1 · 792 postsLIFE | НАУКА
@lifesciences · 902 postsМодератор | Пример
@ModerMedia · 102 posts🔶Невиданный AliExpress🔶
@nevidanniyaliexpress · 42 postsPressCode Новости
@PressCodeNewsRu · 5942 postsRADISLAV GANDAPAS
@radislav_gandapas · 992 postsTelegram advice
@TGAdvices · 1782 postsTrending Apps
@trendingapps · 3,965,6292 postsWonderful World
@WOWorld · 332 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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“ChatKeeperBot” (@ChatKeeperBot), 499,544 monthly users as measured 22 August 2026. Telegram Register, tgregister.com/channel/ChatKeeperBot.
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.