
Bot
TON Airdrop
@TONGramAirdropBot
On this record: Growth · Engagement · Citations · Cite this entry
35,242monthly users
+365 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 ID | 8809251147 |
|---|---|
| Type | Bot |
| Username | @TONGramAirdropBot |
| First recorded | 13 August 2026 |
| Last confirmed live | 3 October 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 24 times, most recently 24 September 2026 |
| On Telegram | t.me/TONGramAirdropBot |
Growth
| Measured (UTC) | Monthly users | Change |
|---|---|---|
| 17 Aug 2026, 20:29 | 35,242 | +105 |
| 13 Aug 2026, 18:45 | 35,137 | no change |
| 10 Aug 2026, 19:43 | 35,137 | +260 |
| 7 Aug 2026, 12:16 | 34,877 | 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 18 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.
Named by
Channels on the register whose posts name this channel's handle.
@Crypto_Earn_TM · 6593 postsدرآمد از تلگرام
@dramad_dollari1 · 4,5613 postsMr Airdrop
@MrAirdropAlert · 485,9102 postsRUUBE TECH
@ruube_tech · 7,9002 posts💰𝗠𝗔𝗥𝗢𝗢𝗙𝗜 𝗜𝗗𝗥𝗢𝗣🛍
@shrhdhrjdhdh · 2,9652 postsEthio online work
@A_Z_09tech · 1741 postBingo Bonus
@BONUSBINGO1 · 3901 postEthio Free
@Ethiopianlinklayer · 1421 post𝑯𝑬𝑿𝑨 𝑪𝑹𝒀𝑷𝑻𝑶 𝒁𝑶𝑵𝑬
@FreeincomewithFahad · 2,3591 postKaliil Elais 💻💎⚖🛠🔑
@kaliilelais35 · 1691 postПромокод _كنز الربح الرقمي 💰
@MN_MA100 · 2181 postMaatii Poppo Live
@mypoppo · 3151 postJohn notice
@proofchannel22 · 1291 postPaying 100% telegramm bot and sites/Scambuster No.1
@ReferralsgroupbotsBitcoinandCo · 2031 postKon Win
@saww_ll · 1,9361 postSHIKELA(ሽቀላ) channel
@shikela2 · 2021 post🦁☀️ شیر و خورشید ☀️🦁
@SHIROKHORSHID11 · 3321 postربح المجاني
@VaultoUSDT · 1,4301 post
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.
“TON Airdrop” (@TONGramAirdropBot), 35,242 monthly users as measured 17 August 2026. Telegram Register, tgregister.com/channel/TONGramAirdropBot.
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.