
Bot
Tonkeeper
@tonkeeper
On this record: Growth · Engagement · Citations · Cite this entry
33,094monthly users
-1,711 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | 6549302342 |
|---|---|
| Type | Bot |
| Username | @tonkeeper |
| First recorded | 13 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 4 |
| On Telegram | t.me/tonkeeper |
Growth
| Measured (UTC) | Monthly users | Change |
|---|---|---|
| 13 Aug 2026, 19:56 | 33,094 | no change |
| 11 Aug 2026, 07:45 | 33,094 | -877 |
| 8 Aug 2026, 10:18 | 33,971 | -834 |
| 5 Aug 2026, 22:02 | 34,805 | 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.
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 67 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.
@tonkeeper_farsi · 195,734104 postsTonkeeper News
@tonkeeper_news · 5,067,45862 postsTonkeeper中文频道
@Tonkeeper_Chinese · 11,83559 postsGram of TON
@gram · 7,028,25125 postsTonkeeper Yangiliklari
@tonkeeper_uzbek · 1,72818 postsTON Community العربية
@toncoin_ar · 945,30515 postsGetgems NFT
@getgems · 278,29512 postsGetgems NFT RU
@getgemsrus · 110,93412 postsTON Community
@toncommunitychannel · 812,3898 postsSpacAd ENG 🇺🇲
@earnings_metaverse · 266 postsToncoin فارسی
@toncoin_fa · 420,6036 postsToncoin 🇹🇷
@toncoin_tur · 53,5496 postsToncoin 🇻🇳
@toncoin_vn · 44,4106 postsTon Console
@tonconsole_com · 12,1646 postsНовости Тонкипера
@tonkeeper_ru · 472,9236 postsETHIO WALET 🇪🇹
@ethio_wallet · 8,8635 postsХомяк с TON’а
@homyak_s_tona · 26,4135 postsToncoin 🇮🇹
@toncoin_it · 58,2605 posts中文资讯 中文频道 中文设置
@zh_cnk8 · 11,5565 postsToncoin 🇮🇩
@toncoin_id · 201,0964 postsToncoin 🇧🇷🇵🇹
@toncoin_pt · 55,0494 postsToncoin 中文頻道
@Toncoin_tc · 18,2094 postsToncoin 🇺🇿
@toncoin_uz · 55,5524 postsWizards Island
@wizzwoods_game · 1,308,0214 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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“Tonkeeper” (@tonkeeper), 33,094 monthly users as measured 13 August 2026. Telegram Register, tgregister.com/channel/tonkeeper.
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.