Bot
KOLscope Bot
@KOLscopeBot
On this record: Topic · Growth · Engagement · Citations · Cite this entry
33,618monthly users
+2,165 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | 7946549390 |
|---|---|
| Type | Bot |
| Username | @KOLscopeBot |
| First recorded | 13 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/KOLscopeBot |
Topic
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 9 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 |
|---|---|---|
| 17 Sept 2026, 23:39 | 33,618 | +52 |
| 14 Sept 2026, 01:36 | 33,566 | +3 |
| 12 Sept 2026, 05:20 | 33,563 | +30 |
| 9 Sept 2026, 22:16 | 33,533 | -29,935 |
| 6 Sept 2026, 15:21 | 63,468 | +31,661 |
| 2 Sept 2026, 19:57 | 31,807 | +83 |
| 29 Aug 2026, 13:13 | 31,724 | +46 |
| 26 Aug 2026, 13:42 | 31,678 | +57 |
| 24 Aug 2026, 14:18 | 31,621 | +12 |
| 21 Aug 2026, 13:23 | 31,609 | +58 |
| 17 Aug 2026, 10:54 | 31,551 | -25 |
| 14 Aug 2026, 07:25 | 31,576 | +24 |
| 13 Aug 2026, 21:05 | 31,552 | no change |
| 11 Aug 2026, 01:27 | 31,552 | +63 |
| 6 Aug 2026, 07:51 | 31,489 | +36 |
| 6 Aug 2026, 03:38 | 31,453 | 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 191 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 · 30,8141,594 postsBATMAN GAMBLE 🦇
@bat_gamble · 19,781379 postsChris Journal ™️
@christophersalpha · 44,395292 postsBruiser’s Gambles🍜⛩️
@bruisersgambles · 7,693161 posts𝐂𝐥𝐚𝐬𝐢𝐞𝐫 𝐂𝐚𝐥𝐥𝐬 🇺🇸
@ClasierCalls · 40,83491 postsMicha 电话 - Micha Calls
@michacalls · 8,01889 postsBruisers Calls
@bruiserscalls · 33,24169 postsWoods Gem calls
@WoodGemscalls · 13,61467 postsObitos Casino (lowcap calls/gambles)
@obitoscasino · 11,14764 posts🔱 Marvels Call 🔱
@Marvels_Calls · 4,46159 postsBATMAN GEMS 🦇
@batman_gem · 21,29657 postsMayers official calls
@mayerscallz · 23,79157 postsBigBull Official Calls™
@Bigbulloficial · 83,74249 postsAngry Birds Calls™📢
@Angrybirdscalls · 29,74148 posts𝗟𝗶𝘇𝗮𝗿𝗱 𝗖𝗮𝗹𝗹𝘀 💎 📞
@LizardCall · 51,11643 posts𝐂𝐑𝐘𝐏𝐓𝐎 𝐑𝐀𝐕𝐄𝐍 𝐂𝐀𝐋𝐋 🇯🇴
@CRYPTO_RAVEN_CALL · 49,76940 posts𝗟𝘂𝗰𝗶𝗳𝗲𝗿 𝗖𝗮𝗹𝗹𝘀
@LucifersCalls · 53,21640 postsTesla Calls Official
@Teslacallsofficial · 67,63840 postsAladdin calls 月龍 {TSUKI}
@Aladdincall · 5,48338 posts𝘾𝙧𝙮𝙥𝙩𝙤 𝙋𝙖𝙣𝙙𝙖 𝙂𝙚𝙢𝙨💎
@CryptoPandaGems_1 · 37,39936 posts𝗖𝗮𝗽𝗿𝗶 𝗖𝗮𝗹𝗹𝘀 💎🎯
@CapriCalls · 40,12031 postsКрипто Инсайдер
@CH1RO0 · 9,23824 postsEvee cook’s ❄️
@ghastlygems · 14,74822 postsICEMAN COOKS
@CoIdGamble · 44,73721 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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“KOLscope Bot” (@KOLscopeBot), 33,618 monthly users as measured 17 September 2026. Telegram Register, tgregister.com/channel/KOLscopeBot.
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.