Bot
TokenScan
@tokenscan
On this record: Growth · Engagement · Citations · Cite this entry
28,544monthly users
-785 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | 8436907499 |
|---|---|
| Type | Bot |
| Username | @tokenscan |
| First recorded | 14 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/tokenscan |
Growth
| Measured (UTC) | Monthly users | Change |
|---|---|---|
| 15 Aug 2026, 12:06 | 28,544 | -11 |
| 14 Aug 2026, 17:28 | 28,555 | no change |
| 14 Aug 2026, 00:13 | 28,555 | -272 |
| 12 Aug 2026, 15:37 | 28,827 | -381 |
| 11 Aug 2026, 14:33 | 29,208 | -33 |
| 10 Aug 2026, 15:45 | 29,241 | +21 |
| 9 Aug 2026, 17:01 | 29,220 | +3,494 |
| 7 Aug 2026, 14:26 | 25,726 | -3,603 |
| 6 Aug 2026, 17:49 | 29,329 | 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 55 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.
@Teslacallsofficial · 26,28228 postsTokenScan Ecosystem
@TokenScanHub · 18,24827 postsTesla Gamble
@TeslaGamble · 5,79018 postsBellick's Gallery
@BellickzGallery · 8,4518 postsCallFusion Support 🛜
@CallFusionSupport · 118 postsCryptoRaiders
@raidersofcrypto · 358 postsNextApe🦍 Alpha kalls
@Next_Ape · 1,9247 postsTokenScan Trending
@hotpairs · 17,7756 postsMATT FURIE CALLS
@mattfuriecalls1 · 6,1066 posts:)
@GemDynasty · 1,2244 postsStable Calls
@stabIe · 1304 postsCryptoMark Calls☎️
@CryptoMarkCalls · 93 posts💥🚀 BulLi$h TrEnChBulL$💥🚀
@DenPrintski · 1863 postsMoney Meths
@moneyngl · 1083 postsCANDLE CALLS
@CandleCallsOfficial1 · 6262 postsDXB - Gambel & Cooks
@dxb_og · 452 postsInfinityGainz Announcement Channel
@InfinityGainz · 8,1582 postsMeechi’s Degen Lab
@MeechisLab · 5502 posts𝐍ɪ❶ ⌯ ᴛᴏᴘ ᴄʀʏᴘᴛᴏ ɢᴇᴍs
@Ni1call · 1,6522 postsR's Alpha
@rayinAlpha · 1802 postsRobinhood Call
@robinhoodcall_official · 122 postsRobinhood Gem Call
@solanagemcall · 1,9632 postsRobinhood Gem Degen Call
@solanagemdegencall · 2552 postsSCC Ltd. CAPITAL
@TheCellSccCapital · 812 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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“TokenScan” (@tokenscan), 28,544 monthly users as measured 15 August 2026. Telegram Register, tgregister.com/channel/tokenscan.
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.