
Bot
KOLscope Alerts
@KOLscopeAlertsBot
On this record: Growth · Engagement · Citations · Cite this entry
10,554monthly users
+102 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 | 7691262780 |
|---|---|
| Type | Bot |
| Username | @KOLscopeAlertsBot |
| First recorded | 22 August 2026 |
| Last confirmed live | 25 August 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 25 August 2026 |
| On Telegram | t.me/KOLscopeAlertsBot |
Growth
| Measured (UTC) | Monthly users | Change |
|---|---|---|
| 25 Aug 2026, 04:49 | 10,554 | +21 |
| 22 Aug 2026, 17:07 | 10,533 | no change |
| 22 Aug 2026, 06:18 | 10,533 | +1 |
| 20 Aug 2026, 23:54 | 10,532 | +2 |
| 20 Aug 2026, 01:04 | 10,530 | +39 |
| 17 Aug 2026, 19:24 | 10,491 | +11 |
| 16 Aug 2026, 18:56 | 10,480 | +9 |
| 12 Aug 2026, 17:54 | 10,471 | +12 |
| 11 Aug 2026, 19:32 | 10,459 | +3 |
| 9 Aug 2026, 18:44 | 10,456 | +16 |
| 7 Aug 2026, 21:42 | 10,440 | -5 |
| 6 Aug 2026, 23:51 | 10,445 | -7 |
| 6 Aug 2026, 03:46 | 10,452 | 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 101 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.
@KOLscope · 32,429371 postsBATMAN GAMBLE 🦇
@bat_gamble · 21,839121 postsChristopher’s Alpha Chads™️
@christophersalpha · 31,20554 postsBruiser’s Gambles🍜⛩️
@bruisersgambles · 8,35353 postsMicha 电话 - Micha Calls
@michacalls · 8,04227 posts🔱 Marvels Call 🔱
@Marvels_Calls · 4,53725 postsBATMAN GEMS 🦇
@batman_gem · 26,17913 postsBruisers Calls
@bruiserscalls · 21,75010 postsAladdin calls 月龍 {TSUKI}
@Aladdincall · 12,7988 postsCryptoWolves Call🦊
@CryptoWolvesCall · 10,1518 postsPirate Calls 💎
@PirateGemsCall · 6,6788 posts𝗟𝗶𝘇𝗮𝗿𝗱 𝗖𝗮𝗹𝗹𝘀 🧪🎯
@LizardCall · 43,5897 postsMayers official calls
@mayerscallz · 21,4277 postsMOONBOYS PLAYS
@moonboysplay · 2177 posts𝗟𝘂𝗰𝗶𝗳𝗲𝗿 𝗖𝗮𝗹𝗹𝘀
@LucifersCalls · 39,3536 postsThe_GreenPrint
@The_Greenprint · 1,7166 postsBlind Ape 🥀
@blindapein · 1165 postsCOOK DEV-IL CALL-CHANNEL
@COOK_DEV_IL · 7725 postsDobbermanchad Calls
@dobbermanchadcalls · 9925 postsEvee cook’s
@ghastlygems · 14,7305 posts- SOL -
@lowtaxsolana · 48,5695 postsRam’s Gems Calls ✨
@ramscalls · 6,2515 postsYungezy’s cooks👨🏽🍳
@YungezysCooks · 4365 postsZorin Calls
@ZorinCalls · 2,0234 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 25 August 2026 — this entry's latest reading, not the date you are reading this.
“KOLscope Alerts” (@KOLscopeAlertsBot), 10,554 monthly users as measured 25 August 2026. Telegram Register, tgregister.com/channel/KOLscopeAlertsBot.
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.