Channel
@loon008
On this record: Topic · Growth · Engagement · Posts · Cite this entry
779subscribers
-4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001697131493 |
|---|---|
| Type | Channel |
| Username | @loon008 |
| Created | 26 March 2022 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 31 October 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 6 times, most recently 31 October 2026 |
| On Telegram | t.me/loon008 |
Hacking & security — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 70% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Sept 2026, 16:35 | 779 | -1 |
| 19 Aug 2026, 19:38 | 780 | -3 |
| 7 Aug 2026, 06:01 | 783 | no change |
| 7 Aug 2026, 05:50 | 783 | first reading |
8 posts held, back to 26 March 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 8 posts for this entry, the most recent from 14 March 2023. An engagement rate over an empty window would be a number about nothing.
The owner of this channel has been inactive for the last 5 months. If they remain inactive for the next 7 days, they may lose their account and admin rights in this channel. The channel will remain accessible for all users.
The owner of this channel has been inactive for the last 5 months. If they remain inactive for the next 17 days, they may lose their account and admin rights in this channel. The channel will remain accessible for all users.
联系不到我的，点击关注我联系你https://t.me/oppo666
@oppo666
这只是一个跳转窗口 请点击下方ID联系我业务号细聊 ↓↓↓↓↓↓↓↓↓↓↓
棋牌跑分 绝无三黑 1–高价回收USDT｛骗子绕道｝ 2–免押金 跑分 （一笔一结） 3–新手可教，日赚5000￥-20000￥ 4–卡接回U模式 点位百分之10-15 5–要求：先把U准备好，财务先转钱和佣金给你，你秒回我U 6.接着你可继续购买U。继续交易。滚雪球。 7.你离成功只是差一个机会。。 发财加我 @oppo666
‼️‼️重要通知‼️‼️ 1️⃣扫码授权 骗子给你二维码，让你钱包扫码给对方转1个TRX或者1个USDT。测试你的钱包能否给对方转账。 都是骗子让你们钱包授权，盗你们U。切勿上当受骗‼️‼️ 2️⃣链接DAPP授权 骗子给你链接，让你转少量虚拟货币到这个链接地址。让你在钱包搜索栏打开这个地址转少量虚拟货币给对方。这并不是正常转账！ 都是骗子让你们钱包授权，盗你们U，切勿上当受骗‼️‼️ 3️⃣测U查安全报告DAPP授权。例如：中石化油卡‼️‼️ 骗子给你链接，让你在钱包搜索栏打开该链接地址，扣取少量虚拟货币作为手续费生成钱包安全报告。这并不是检测钱包安全与虚拟货币真实！ 都是骗子让你们钱包授权，盗你们U！切勿上当受骗‼️‼️ 4️⃣代买USDT 都是骗子为了骗取押金所用的说辞‼️‼️切勿上当受骗‼️‼️ 5️⃣高风险钱包：strat钱包、TP钱包（TokenPoc…
Channel created
Showing the 8 most recent of 8 posts we hold for @loon008. 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.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“跑分、卡接回U、招聘车队散户、小白可培养” (@loon008), 779 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/loon008.
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.