🔮 @Cook_dev_il Dropped a Call 🔮 🔮Token Symbol 🔮 $AISWIM 🔮Current MC 🔮 238.5K 🔮Chain Symbol 🔮 SOL We've started tracking it and will continue to send performance alerts as the token progresses. Stay tuned! Ca: A6ABDPoWvYSy5PC6a68G6eByXSu7mteqPkXCoEVGpump 🔮MAE 🔮KOL 🔮BOT

Channel
WIZARD SCAN Live
@WizardScan
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
20,750subscribers
+15,172 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 | -1002202651538 |
|---|---|
| Type | Channel |
| Username | @WizardScan |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 5 October 2026 |
| Measurements held | 37 |
| Confirmed unchanged | 1 time, most recently 5 October 2026 |
| On Telegram | t.me/WizardScan |
Topic
Crypto & trading — 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 100% 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) | Subscribers | Change |
|---|---|---|
| 5 Oct 2026, 07:18 | 20,750 | -3,242 |
| 29 Sept 2026, 00:36 | 23,992 | -3,134 |
| 17 Sept 2026, 23:18 | 27,126 | -1,381 |
| 15 Sept 2026, 19:17 | 28,507 | +1,945 |
| 14 Sept 2026, 03:20 | 26,562 | -6,437 |
| 12 Sept 2026, 07:55 | 32,999 | -5,611 |
| 10 Sept 2026, 04:20 | 38,610 | -6,331 |
| 6 Sept 2026, 20:35 | 44,941 | -1,888 |
| 4 Sept 2026, 10:42 | 46,829 | -299 |
| 2 Sept 2026, 20:56 | 47,128 | -33 |
| 1 Sept 2026, 17:35 | 47,161 | -134 |
| 31 Aug 2026, 19:36 | 47,295 | -14,749 |
| 30 Aug 2026, 16:47 | 62,044 | -2,216 |
| 29 Aug 2026, 18:15 | 64,260 | -11,101 |
| 28 Aug 2026, 20:08 | 75,361 | -9,403 |
| 27 Aug 2026, 21:28 | 84,764 | +55,151 |
| 26 Aug 2026, 23:39 | 29,613 | -105 |
| 26 Aug 2026, 01:16 | 29,718 | -204 |
| 25 Aug 2026, 02:23 | 29,922 | -2,517 |
| 23 Aug 2026, 17:35 | 32,439 | first reading |
Engagement
1,900 posts held, back to 6 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 95 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 0.222%
- avg views ÷ 20,750 subscribers
- Avg views / post
- 46.0
- 560 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 560
- of 1,900 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 4 October 2026 |
|---|---|
| Posts held | 1,900 (6 August 2026 – 4 October 2026) |
| Views total | 25,762 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 4 Oct 2026, 21:24 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
What this channel posts
- Video runtime
- 8m 00s
- Average length
- 6s
Measured directly from 86 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Recent posts
🔮 @Earlycallsalert Dropped a Call 🔮 🔮Token Symbol 🔮 $XSI 🔮Current MC 🔮 21.6K 🔮Chain Symbol 🔮 ETH We've started tracking it and will continue to send performance alerts as the token progresses. Stay tuned! Ca: 0x285c38d3e992a2d6a173733dfb38ffba9a6df966 🔮MAE 🔮KOL 🔮BOT
🔮 @Cook_dev_il Dropped a Call 🔮 🔮Token Symbol 🔮 $NIGGAPUBES 🔮Current MC 🔮 108.4K 🔮Chain Symbol 🔮 SOL We've started tracking it and will continue to send performance alerts as the token progresses. Stay tuned! Ca: A1Ciq7NGoCdd3wYb5HQTcenE2wyMRKPpebKWGD3Bkdn4 🔮MAE 🔮KOL 🔮BOT
🔮 @Doxxedguygambles Dropped a Call 🔮 🔮Token Symbol 🔮 $SGSI 🔮Current MC 🔮 71.8K 🔮Chain Symbol 🔮 SOL We've started tracking it and will continue to send performance alerts as the token progresses. Stay tuned! Ca: 8FffCcpYMCTc3QC6FmafKq4JGmo4UmsvfHtGZxQWNTKv 🔮MAE 🔮KOL 🔮BOT
🔮 @Cook_dev_il Dropped a Call 🔮 🔮Token Symbol 🔮 $ELONEMON 🔮Current MC 🔮 105.1K 🔮Chain Symbol 🔮 SOL We've started tracking it and will continue to send performance alerts as the token progresses. Stay tuned! Ca: 2qtUmY7H7LazRKQ7wQUWaA4W1QtSBfu1eLFCba6Wpump 🔮MAE 🔮KOL 🔮BOT
🔮 @Earlycallsalert KOL Hit 3X+ $PANDAKEY RH called at 296.4K. Now at 889.1K. Clean execution. CHAMP KOL - Rank # 🔮 🔮 296.4K 🔮 889.1K 🔮Caller 🔮Twitter 🔮Trade 🔮DEX 🔮Details 🔮DEV
🔮 @Cook_dev_il KOL Hit 4X+ $HUMAN SOL called at 162.5K. Now at 653.9K. Clean execution. 🔮 162.5K 🔮 653.9K 🔮Caller 🔮Twitter 🔮Trade 🔮DEX 🔮Details 🔮DEV
🔮 @Cook_dev_il KOL Hit 3X+ $HUMAN SOL called at 162.5K. Now at 500.1K. Clean execution. 🔮 162.5K 🔮 500.1K 🔮Caller 🔮Twitter 🔮Trade 🔮DEX 🔮Details 🔮DEV
🔮 @Cook_dev_il KOL Hit 2X+ $HUMAN SOL called at 162.5K. Now at 359.6K. Clean execution. 🔮 162.5K 🔮 359.6K 🔮Caller 🔮Twitter 🔮Trade 🔮DEX 🔮Details 🔮DEV
🔮 @Defiapegamble KOL Hit 5X+ $SIF ETH called at 163.1K. Now at 852.6K. Clean execution. 🔮 163.1K 🔮 852.6K 🔮Caller 🔮Twitter 🔮Trade 🔮DEX 🔮Details 🔮DEV
🔮 @Cook_dev_il Dropped a Call 🔮 🔮Token Symbol 🔮 $SHIBALISA 🔮Current MC 🔮 716.2K 🔮Chain Symbol 🔮 SOL We've started tracking it and will continue to send performance alerts as the token progresses. Stay tuned! Ca: G939riCWgdnZyRSZwJm44nPr1SocioKcWH41w8JLpump 🔮MAE 🔮KOL 🔮BOT
🔮 @Cook_dev_il Dropped a Call 🔮 🔮Token Symbol 🔮 $HUMAN 🔮Current MC 🔮 162.5K 🔮Chain Symbol 🔮 SOL We've started tracking it and will continue to send performance alerts as the token progresses. Stay tuned! Ca: 8nPoBHiBM6pybxMws9PA2JRb9BjkppBfqcZGmot4DMBC 🔮MAE 🔮KOL 🔮BOT
Showing the 12 most recent of 1,900 posts we hold for @WizardScan. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
@pandacallslonge3 · 56,10365 posts ᗰᗩYᗷᗩᑕᕼ 鲸鱼 💮
@maybac_whales · 62,02652 posts𝐂𝐑𝐘𝐏𝐓𝐎 𝐑𝐀𝐕𝐄𝐍 𝐂𝐀𝐋𝐋 🇯🇴
@CRYPTO_RAVEN_CALL · 59,45836 postsChinese Pump 我会啊了啊 alpha calls
@Chinesewhalespump · 33,28929 posts𝐒𝐈𝐍𝐀 #𝐓𝐑𝐄𝐍𝐃𝐈𝐍𝐆 广告
@sinatrending · 23,34322 postsAcid Call { 跨链项目推广者 }
@Acid_Call · 7,42820 posts𝗕𝗜𝗚 𝗪𝗛𝗔𝗟𝗘𝗦 𝗖𝗔𝗟𝗟™
@Big_Whale_call · 52,66314 postsTesla Calls Official
@Teslacallsofficial · 68,92413 postsLoyal
@lOOoyalLlLl · 312 postsLizard Calls 💎 📞
@LizardCall · 43,00411 postsROBINHOOD DEGEN CALLS BOT
@robinhoodcallsbot · 9608 posts𝐂𝐫𝐲𝐩𝐭𝐨 𝐃𝐞𝐅𝐢 𝐂𝐚𝐥𝐥𝐬 ☎💯
@CryptoDefi_Calls · 26,2367 postsDeFi Doxx Calls
@Defidoxxcalls · 33,9317 postsCryptoGem Calls 💎
@Cryptogemmcalls · 2,9026 postsGlobal Explore Calls 📉📈
@GlobalExploreCalls · 33,5505 posts𝗖𝗮𝗽𝗿𝗶 𝗖𝗮𝗹𝗹𝘀 💎🎯
@CapriCalls · 39,8814 posts洛德国王喊单 (LORD_KINGCALL
@LORD_KINGCALL · 24,2333 postsBigBangCalls
@BigBangCall · 17,6672 postsDefiape Gamble
@DeFiApeGamble · 14,7092 postsPikachu Calls
@PikachuCallsGirls · 7,5812 postsChris Journal ™️
@christophersalpha · 48,4122 posts𝙋𝙖𝙥𝙥𝙞 𝙘𝙧𝙮𝙥𝙩𝙤 𝐂𝐚𝐥𝐥 𝐠𝐞𝐦𝐬
@pappicallsgems · 90,4992 postsCryptoWolves Call🦊
@CryptoWolvesCall · 11,9931 post太初链纪 $GCC
@GenesisChainLog · 20,4851 post𝗣𝘆𝘁𝗵𝗼𝗻 𝗖𝗮𝗹𝗹 🐍 🚀
@PYTHONCALL · 21,6071 post
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 28 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.
@pandacallslonge3 · 56,10355 posts ᗰᗩYᗷᗩᑕᕼ 鲸鱼 💮
@maybac_whales · 62,02641 posts𝐂𝐑𝐘𝐏𝐓𝐎 𝐑𝐀𝐕𝐄𝐍 𝐂𝐀𝐋𝐋 🇯🇴
@CRYPTO_RAVEN_CALL · 59,45835 postsChinese Pump 我会啊了啊 alpha calls
@Chinesewhalespump · 33,28923 posts𝐒𝐈𝐍𝐀 #𝐓𝐑𝐄𝐍𝐃𝐈𝐍𝐆 广告
@sinatrending · 23,34319 postsAcid Call { 跨链项目推广者 }
@Acid_Call · 7,42814 postsTesla Calls Official
@Teslacallsofficial · 68,92411 posts𝗕𝗜𝗚 𝗪𝗛𝗔𝗟𝗘𝗦 𝗖𝗔𝗟𝗟™
@Big_Whale_call · 52,6639 postsROBINHOOD DEGEN CALLS BOT
@robinhoodcallsbot · 9608 posts𝗖𝗮𝗽𝗿𝗶 𝗖𝗮𝗹𝗹𝘀 💎🎯
@CapriCalls · 39,8817 postsGlobal Explore Calls 📉📈
@GlobalExploreCalls · 33,5507 postsLoyal
@lOOoyalLlLl · 37 postsDeFi Doxx Calls
@Defidoxxcalls · 33,9316 postsLizard Calls 💎 📞
@LizardCall · 43,0046 posts𝐂𝐫𝐲𝐩𝐭𝐨 𝐃𝐞𝐅𝐢 𝐂𝐚𝐥𝐥𝐬 ☎💯
@CryptoDefi_Calls · 26,2363 postsCryptoGem Calls 💎
@Cryptogemmcalls · 2,9023 posts𝙋𝙖𝙥𝙥𝙞 𝙘𝙧𝙮𝙥𝙩𝙤 𝐂𝐚𝐥𝐥 𝐠𝐞𝐦𝐬
@pappicallsgems · 90,4993 postsBigBangCalls
@BigBangCall · 17,6672 postsChris Journal ™️
@christophersalpha · 48,4122 posts洛德国王喊单 (LORD_KINGCALL
@LORD_KINGCALL · 24,2332 postsPikachu Calls
@PikachuCallsGirls · 7,5812 postsTON Drops Me Gift Giveaway Aggregator
@ton_drops_me_airdrop · 1,8162 postsCryptoWolves Call🦊
@CryptoWolvesCall · 11,9931 post太初链纪 $GCC
@GenesisChainLog · 20,4851 post
Names
Channels on the register whose handles appear in this channel's posts.
@maestro · 47,5581,885 postsWIZARD SCAN
@WIZARD_SCAN_BOT · 14,1141,885 postsKLEVER CALLS 🦅
@klevercalls · 2,780249 postsSolana Degen Calls Bot
@degencultcalls · 1,076226 postsROBINHOOD DEGEN CALLS BOT
@robinhoodcallsbot · 960226 postsCOOK DEV-IL CALL-CHANNEL
@COOK_DEV_IL · 940159 postsZorin Calls
@ZorinCalls · 2,362156 postsKOL SignalX
@kolsignal · 3,063115 postsPikachu Calls
@PikachuCallsGirls · 7,58190 posts21Savage Alpha Cooks
@cryptwallstreetcalls · 2,64157 postsMini Bang Calls
@MiniBangCall · 7,70054 posts ᗰᗩYᗷᗩᑕᕼ 鲸鱼 💮
@maybac_whales · 62,02644 postsJem's Degen Calls ( Take Profit is the key )
@jemsdegens · 3,10239 postsSonic Calls
@Soniccall · 4,19929 posts⏳Vortex Gamble 🐳🐳
@Vortex_Gamble · 5,42327 postsChris Journal ™️
@christophersalpha · 48,41223 postsNicks Trade Journal (ALL plays)
@nicksdegens · 1,33222 postsSolana Early Trending 💵
@solearlytrending · 106,35520 postsAcid Call { 跨链项目推广者 }
@Acid_Call · 7,42816 postsDefiape Gamble
@DeFiApeGamble · 14,70916 posts太初链纪 $GCC
@GenesisChainLog · 20,48516 postsPrintWith AlphaGems Calls💎
@AlphaTaylorGems · 2,48914 postsVORTEX COIN TALK
@Vortex_Calls · 6,36714 posts𝐂𝐑𝐘𝐏𝐓𝐎 𝐑𝐀𝐕𝐄𝐍 𝐂𝐀𝐋𝐋 🇯🇴
@CRYPTO_RAVEN_CALL · 59,45813 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 5 October 2026 — this entry's latest reading, not the date you are reading this.
“WIZARD SCAN Live” (@WizardScan), 20,750 subscribers as measured 5 October 2026. Telegram Register, tgregister.com/channel/WizardScan.
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.