Channel
@vanpelt_tokenhunter
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
772subscribers
-19 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001552187397 |
|---|---|
| Type | Channel |
| Username | @vanpelt_tokenhunter |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 October 2026 |
| Last confirmed live | 8 October 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 8 October 2026 |
| On Telegram | t.me/vanpelt_tokenhunter |
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 6 October 2026 and assigned it the closest of 31 fixed categories, at 95% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Oct 2026, 13:17 | 772 | -4 |
| 6 Oct 2026, 02:22 | 776 | no change |
| 27 Sept 2026, 02:21 | 776 | -3 |
| 14 Sept 2026, 03:00 | 779 | -2 |
| 6 Sept 2026, 20:18 | 781 | -2 |
| 28 Aug 2026, 16:17 | 783 | -2 |
| 20 Aug 2026, 16:54 | 785 | -1 |
| 13 Aug 2026, 14:36 | 786 | -5 |
| 7 Aug 2026, 01:18 | 791 | first reading |
20 posts held, back to 5 November 2023 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 29 August 2025. An engagement rate over an empty window would be a number about nothing.
❌ Maru the Shiba MARU 📊 https://www.dextools.io/app/en/ether/pair-explorer/0xeeb4fac22e3bbcb81471fe08effc7c7fb6abafb8?t=1756490044289 TLDR: hidden mint The function transfer contains a piece of code that can mint token. The wallet defined as Gklok in the sc can trigger the scam and double its own token. Care.
Hey guys, how you doing? I wanted to inform you that I will probably start posting something inherent to scams again in the next few days. You may have noticed that I disappeared and wasn't very consistent in the last period of activity so I won't lie to you, I probably won't be as active as I was in the early days of the channel. But I still feel like posting something, more calmly. I hope you will appreciate it. St…
❌ Bitcoin Mascot (ALPACA) 📊 https://www.dextools.io/app/en/ether/pair-explorer/0x0e368c4b35ba9dbe9d62db70a9240f48bc230942 TLDR: backdoor implemented The function setfee, declared as external and callable from the _FeeAddress1 wallet, can be executed even after the renounce and can change without any control the contract taxes. Care.
❌ CompareAi (CAI) 📊 https://dextools.io/app/en/ether/pair-explorer/0x4554d36d462599ebb1ecc82a79391965774488a9 TLDR: misleading function, can modify taxes and honeypot The function TaxRemove (2), callable even after the renounce from dev wallet dev wallet, triggers the function _RemeveTax that can be used to change the taxes withouth any limit. Avoid it.
❌ ZergRush (RUSH) 📊 https://www.dextools.io/app/en/ether/pair-explorer/0x8e66b3cf6bea4526ec8823c2d858b4e7def59451 TLDR: hidden mint The portion of code in the image (1) contained in the transfer function of the contract can be used to mint token directly into the contract address thanks to the function RUSHlotaawteryer (2) Care.
❌ GIB Token (GIB) 📊 https://www.dextools.io/app/en/ether/pair-explorer/0x74db9d61fc0f02726441b41d9ae9a258114daf0b TLDR: backdoor function, can mint token The function _setGIBCoin (1 - callable even after the renounce from a dev wallet) can be used to honeypot and mint token. This function modifies the values BurnFigure and ConfirmFigure used in the transfer method of the sc (2) Avoid it.
❌ Hello Kitty (KITTY) 📊 https://www.dextools.io/app/en/ether/pair-explorer/0xefd1eda2a6235b6e2d943c56a4d34ef13ac1bdf6 TLDR: misleading function, can modify taxes and honeypot The function TaxRemove (2), callable even after the renounce from dev wallet dev wallet, triggers the function _remeveTax that can be used to change the taxes withouth any limit. Avoid it.
❌ Grok Cyber ($GrokCyber) 📊 https://etherscan.io/address/0x22aCB1b4969517A0B1a50F8d54291d1481A9B504#code TLDR: Hidden Mint The function enquiryBalance, callable even after the renounce from the _safu wallet, can be used to mint token and drain the liquidity Avoid it.
❌ Groooook.io (Groooook) 📊 https://www.dextools.io/app/en/ether/pair-explorer/0x2433d5b09052bfafe278d83453825a852ea6cd79 TLDR: backdoor function, can mint token The function _setRedeemBurn (1 - callable even after the renounce from a dev wallet) can be used to honeypot and mint token. This function modifies the values BurnFigure and ConfirmFigure used in the transfer method of the sc (2) Avoid it.
❌ Magic Grok Money ($BITCOIN) 📊 https://www.dextools.io/app/en/ether/pair-explorer/0x99f37797ada67a1ed00d6034b562e5c7982b9095 TLDR: hidden mint The portion of code in the image (1) contained in the transfer function of the contract can be used to mint token directly into the contract address thanks to the function greggle (2) Care.
⚠️ The Dogefather (DOGEFATHER) 📊 https://www.dextools.io/app/en/ether/pair-explorer/0x1b708004995ecf64020c9a22d0c0b13fba7a1b3f TLDR: backdoor function The function reduceTax is a potential backdoor function that can be used to modify the sell tax without any limit even after the renounce. Care.
❌ Money Laundering Machine (MLM) 📊 https://www.dextools.io/app/en/ether/pair-explorer/0x0466fec2f3c8c532ff114988c81f90ca37e4b037 TLDR: mint function This happened some minutes ago. The function swapTokensForEth (usually used to collect token taxes) was modified by the dev in order to set the amount of token in the contract to the total supply (highlighted in the image) and dump it, thus draining all the liquidity
Showing the 12 most recent of 20 posts we hold for @vanpelt_tokenhunter. 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.
Named by 3 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.
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.
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 8 October 2026 — this entry's latest reading, not the date you are reading this.
“Van Pelt (ETH Token Hunter)” (@vanpelt_tokenhunter), 772 subscribers as measured 8 October 2026. Telegram Register, tgregister.com/channel/vanpelt_tokenhunter.
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.