机主今晚2u一单,速速来报❗️❗️❗️ @MHOVO888
Signed 星

Channel
@ZEGAO666
On this record: Topic · Growth · Engagement · Posts · Handles named that no longer answer · Cite this entry
182subscribers
-22 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002241364890 |
|---|---|
| Type | Channel |
| Username | @ZEGAO666 |
| Created | Between 1 June 2024 and 18 August 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/ZEGAO666 |
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 24 September 2026 and assigned it the closest of 31 fixed categories, at 81% 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 |
|---|---|---|
| 5 Nov 2026, 20:57 | 182 | -5 |
| 29 Oct 2026, 00:35 | 187 | -3 |
| 21 Oct 2026, 00:57 | 190 | -1 |
| 12 Oct 2026, 23:26 | 191 | -2 |
| 2 Oct 2026, 00:40 | 193 | -17 |
| 16 Sept 2026, 12:18 | 210 | +2 |
| 9 Sept 2026, 00:56 | 208 | +3 |
| 15 Aug 2026, 17:46 | 205 | +1 |
| 8 Aug 2026, 11:18 | 204 | no change |
| 7 Aug 2026, 12:53 | 204 | first reading |
4 posts held, back to 18 August 2024 — 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 4 posts for this entry, the most recent from 3 November 2024. An engagement rate over an empty window would be a number about nothing.
机主今晚2u一单,速速来报❗️❗️❗️ @MHOVO888
Signed 星
机主今晚2u一单,速速来报❗️❗️❗️ @MHOVO888
Signed 星
支机,法人,码反,口反,身份证号补齐,来单,在线秒 @tongta002 出售几份批量三要素,支持测试,支持春江担保 出售几份二要素补齐,不是库补,支持测试,支持春江担保
Signed 同塔
Posted without readable text
Signed 许中之意
Showing the 4 most recent of 4 posts we hold for @ZEGAO666. 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.
@ZEGAO666 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.
References a handle that is not a live channel — we have no record it ever was one.
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 November 2026 — this entry's latest reading, not the date you are reading this.
“无趣查档 律所/催收/侦探” (@ZEGAO666), 182 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/ZEGAO666.
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.