Channel
@SixpScan
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
257subscribers
-7 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002000940492 |
|---|---|
| Type | Channel |
| Username | @SixpScan |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 11 October 2026 |
| On Telegram | t.me/SixpScan |
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 23 September 2026 and assigned it the closest of 31 fixed categories, at 63% 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 |
|---|---|---|
| 11 Oct 2026, 09:18 | 257 | -1 |
| 1 Oct 2026, 15:22 | 258 | -2 |
| 17 Sept 2026, 09:56 | 260 | -1 |
| 10 Sept 2026, 02:39 | 261 | -1 |
| 31 Aug 2026, 07:33 | 262 | -2 |
| 24 Aug 2026, 13:55 | 264 | -1 |
| 16 Aug 2026, 18:35 | 265 | +1 |
| 8 Aug 2026, 09:03 | 264 | no change |
| 7 Aug 2026, 14:31 | 264 | first reading |
20 posts held, back to 8 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 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 8 August 2026. An engagement rate over an empty window would be a number about nothing.
🔴 Account Status Restored 👤 User ID: 28498 🔥 SIXP Burned: 28.0182 📈 Status Change: Watch Listed ➔ Sixpacker ⚠️ Note: Battery ID 632597 rechecked and rejected by Master Nodes. Burn unfair token earnings. 📆 Date: 8/8/2026 8:23:55 AM #Main
Signed SixpScan
✅ License Renewal 💎 Renewed: Node 6000 - ID 4908 👤 User ID: 29161 🟢 Paid: 0.65 DARIC 📆 Date: 08-08-26 08:18 #Main
Signed SixpScan
✅ License Renewal 💎 Renewed: Node 6000 - ID 4908 👤 User ID: 29161 🟢 Paid: 0.56 SIXP + 0 USDT + 5.16 DARIC 📆 Date: 08-08-26 08:14 #Main
Signed SixpScan
✅ License Renewal 💎 Renewed: Miner FourPack - ID 265 👤 User ID: 29161 🟢 Paid: 8.32 SIXP 📆 Date: 08-08-26 08:14 #Main
Signed SixpScan
✅ Trx Successful 🌎 Meta Shop: Node 4000 💲Rate: 1 SIXP = 0.241254 DARIC 👤 User ID: 28535 🟢 Paid: 7.720139 DARIC 🔴 Got: 32 SIXP 📆 Time: 08-08-26 07:22 🏦 Network Fee: 0.386007 DARIC 🔎 Discover Node 4000 #Main
Signed SixpScan
✅ Trx Successful 🌎 Meta Shop: Pancake Swap 💲Rate: 1 SIXP = 0.095376 USDT 👤 User ID: 28535 🟢 Paid: 10.484863 SIXP 🔴 Got: 1 USDT 📆 Time: 08-08-26 07:21 🏦 Network Fee: 0.524243 SIXP 🔎 Discover Pancake Swap #Main
Signed SixpScan
✅ Trx Successful 🌎 Meta Shop: Pancake Swap 💲Rate: 1 SIXP = 0.095486 USDT 👤 User ID: 18457 🟢 Paid: 10.472779 SIXP 🔴 Got: 1 USDT 📆 Time: 08-08-26 07:19 🏦 Network Fee: 0.523639 SIXP 🔎 Discover Pancake Swap #Main
Signed SixpScan
✅ Trx Successful 🌎 Meta Shop: Node 3000 💲Rate: 1 SIXP = 0.219531 DARIC 👤 User ID: 21747 🟢 Paid: 218.647991 SIXP 🔴 Got: 48 DARIC 📆 Time: 08-08-26 07:18 🏦 Network Fee: 10.9324 SIXP 🔎 Discover Node 3000 #Main
Signed SixpScan
✅ Trx Successful 🌎 Meta Shop: Pancake Swap 💲Rate: 1 SIXP = 0.095596 USDT 👤 User ID: 21747 🟢 Paid: 10.460716 SIXP 🔴 Got: 1 USDT 📆 Time: 08-08-26 07:17 🏦 Network Fee: 0.523036 SIXP 🔎 Discover Pancake Swap #Main
Signed SixpScan
✅ Trx Successful 🌎 Meta Shop: Pancake Swap 💲Rate: 1 SIXP = 0.095706 USDT 👤 User ID: 24078 🟢 Paid: 10.448674 SIXP 🔴 Got: 1 USDT 📆 Time: 08-08-26 07:16 🏦 Network Fee: 0.522434 SIXP 🔎 Discover Pancake Swap #Main
Signed SixpScan
✅ Trx Successful 🌎 Meta Shop: Node 5000 💲Rate: 1 SIXP = 0.255851 DARIC 👤 User ID: 27393 🟢 Paid: 8.954781 DARIC 🔴 Got: 35 SIXP 📆 Time: 08-08-26 07:12 🏦 Network Fee: 0.447739 DARIC 🔎 Discover Node 5000 #Main
Signed SixpScan
✅ Trx Successful 🌎 Meta Shop: Node 4000 💲Rate: 1 SIXP = 0.241225 DARIC 👤 User ID: 27393 🟢 Paid: 7.719202 DARIC 🔴 Got: 32 SIXP 📆 Time: 08-08-26 07:11 🏦 Network Fee: 0.38596 DARIC 🔎 Discover Node 4000 #Main
Signed SixpScan
Showing the 12 most recent of 20 posts we hold for @SixpScan. 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.
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.
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 11 October 2026 — this entry's latest reading, not the date you are reading this.
“SIXP Scan🔎” (@SixpScan), 257 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/SixpScan.
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.