👺 Sold 255.174.795 VANCAT for 0,195848 BNB on PancakeSwap 🔴 1 M VANCAT =$0,2300060 🥞 Buy VANCAT | 📶 Tx Hash |📈 Chart Do You Know @BotAVAX_Channels?🔥

Channel
BSCRocket VANCAT
@bscrocketVancat
On this record: Topic · Growth · Engagement · Posts · Handles named that no longer answer · Cite this entry
149subscribers
-9 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001166176620 |
|---|---|
| Type | Channel |
| Username | @bscrocketVancat |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/bscrocketVancat |
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 25 September 2026 and assigned it the closest of 31 fixed categories, at 68% 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 |
|---|---|---|
| 12 Oct 2026, 06:01 | 149 | -3 |
| 1 Oct 2026, 21:56 | 152 | -2 |
| 13 Sept 2026, 08:15 | 154 | -1 |
| 5 Sept 2026, 23:37 | 155 | -1 |
| 21 Aug 2026, 02:06 | 156 | -2 |
| 8 Aug 2026, 18:01 | 158 | no change |
| 6 Aug 2026, 23:54 | 158 | first reading |
Engagement
20 posts held, back to 14 November 2022 — 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 24 November 2022. An engagement rate over an empty window would be a number about nothing.
Recent posts
🚀 Bought 31.347.260 VANCAT for 0,027560 BNB on PancakeSwap 🟢 1 M VANCAT =$0,2366679 🥞 Buy VANCAT | 📶 Tx Hash |📈 Chart Do You Know @BotAVAX_Channels?🔥
🚀 Bought 132.356.468 VANCAT for 0,115975 BNB on PancakeSwap 🟢 1 M VANCAT =$0,2148507 🥞 Buy VANCAT | 📶 Tx Hash |📈 Chart Do You Know @BotAVAX_Channels?🔥
🚀 Bought 4.486.838 VANCAT for 0,003920 BNB on PancakeSwap 🟢 1 M VANCAT =$0,2079545 🥞 Buy VANCAT | 📶 Tx Hash |📈 Chart Do You Know @BotAVAX_Channels?🔥
👺 Sold 996.171.988 VANCAT for 0,776039 BNB on PancakeSwap 🔴 1 M VANCAT =$0,2047117 🥞 Buy VANCAT | 📶 Tx Hash |📈 Chart Do You Know @BotAVAX_Channels?🔥
🚀 Bought 4.341.802 VANCAT for 0,003933 BNB on PancakeSwap 🟢 1 M VANCAT =$0,2070720 🥞 Buy VANCAT | 📶 Tx Hash |📈 Chart Do You Know @BotAVAX_Channels?🔥
🚀 Bought 133.769.591 VANCAT for 0,120828 BNB on PancakeSwap 🟢 1 M VANCAT =$0,2064230 🥞 Buy VANCAT | 📶 Tx Hash |📈 Chart Do You Know @BotAVAX_Channels?🔥
🚀 Bought 16.658.840 VANCAT for 0,015000 BNB on PancakeSwap 🟢 1 M VANCAT =$0,2105950 🥞 Buy VANCAT | 📶 Tx Hash |📈 Chart Do You Know @BotAVAX_Channels?🔥
👺 Sold 72.652.387 VANCAT for 0,057337 BNB on PancakeSwap 🔴 1 M VANCAT =$0,2066238 🥞 Buy VANCAT | 📶 Tx Hash |📈 Chart Do You Know @BotAVAX_Channels?🔥
🚀 Bought 57.702.156 VANCAT for 0,052288 BNB on PancakeSwap 🟢 1 M VANCAT =$0,2212095 🥞 Buy VANCAT | 📶 Tx Hash |📈 Chart Do You Know @BotAVAX_Channels?🔥
👺 Sold 406.817.379 VANCAT for 0,324831 BNB on PancakeSwap 🔴 1 M VANCAT =$0,2167191 🥞 Buy VANCAT | 📶 Tx Hash |📈 Chart Do You Know @BotAVAX_Channels?🔥
🚀 Bought 31.585.251 VANCAT for 0,029000 BNB on PancakeSwap 🟢 1 M VANCAT =$0,2253496 🥞 Buy VANCAT | 📶 Tx Hash |📈 Chart Do You Know @BotAVAX_Channels?🔥
Showing the 12 most recent of 20 posts we hold for @bscrocketVancat. 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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@bscrocketVancat named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 20 posts, 9 August 2026 – 9 August 2026
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 12 October 2026 — this entry's latest reading, not the date you are reading this.
“BSCRocket VANCAT” (@bscrocketVancat), 149 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/bscrocketVancat.
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.