五年开同回完,继续收,密码找我拿,世上最全的开同,保真,不包遗漏,遗漏不大,官员,党员,干部敏感不接,50单之内都是3天回单,出差除外,一条同住也收费,有质量问题包售后,有原图,一条同住没有可以选择出不出。

Channel
AK天眼查三年老牌天眼查|极速查
@xxiongmaooo
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
51subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003597317149 |
|---|---|
| Type | Channel |
| Username | @xxiongmaooo |
| Created | Between 1 December 2025 and 25 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/xxiongmaooo |
Topic
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 29 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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, 22:11 | 51 | -1 |
| 2 Oct 2026, 23:38 | 52 | +5 |
| 17 Sept 2026, 07:41 | 47 | -1 |
| 9 Sept 2026, 21:38 | 48 | -2 |
| 15 Aug 2026, 02:57 | 50 | -1 |
| 10 Aug 2026, 11:01 | 51 | no change |
| 7 Aug 2026, 19:39 | 51 | first reading |
Engagement
20 posts held, back to 25 May 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 5 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 1m 02s
- Average length
- 1m 02s
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
7 reactions across 4 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 7 | 100.0% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 7 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 7 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 25 May 2026 to 5 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Recent posts
强登12306 姓名身份证手机号+大头报单 出近半年12306高铁火车订票记录 无遗漏 包含未出行订票信息 以及同行人
警务通人脸识别 提供照片:默认出最高相似度5头 提供照片+名字:对上默认出 提供照片+名字+地区:对上一条默认出 提供照片+名字+地区+年龄:对上一条默认出 有备注不对可以不出 不出不收费 精准人脸点射 美颜 照片不清晰 可能会识别错误 出单不扯皮 接受了报 晚上8点开秒 批量来拿优势
老版本开同一体,私家车,每天3个名额,已埋雷 每天都发车,发车后3个工作日内回 敏感收费不给单,密码找我拿
⚠️立案详情⚠️ 降价! 🔽出最新案件 全部同案人 🔽🈳收一半 🔽支持案件编号查询 当天隔天 ✔️源头出单✔️
❤3
半年外卖10条前面的今晚全部回单,新单继续来,2-3天回 半年内外卖回单,继续来,美团订房也有 给最新十条,一条也收费 半年内美团外卖地址 带时间➕地址➕订单名字 每天限量 身份证号码或者手机号都可以报单 敏感收费不给单
又即将迎来周末,流水成本大,压款是所有项目中最高的,我们也需要周转,看到地址结款,谢谢领导们支持🤝 主动清账增进感情‼️
网逃回
❤1
自家条 公网网逃,并非数据库 空给图收费 每天限量收先到先得 此版网逃带详情➕撤销详情(查到有什么给什么)
水电宽带 回完,都是隔天回 水电有户号,宽带有账号。 🔥随时可以打电话验证真假。🔥不是外面的邮政拼出来的假单。
市场没有统一价格 不同渠道收费不同,你总能遇到比我便宜的 也会有比我贵的 暴利是不存在的 认准一个靠谱且保质保真的人最重要
历时两天,接近1000单无盲流水回完,稳定俩月0翻车 周日晚上12点准时发车,下周四前回,全网最快流水 二月 四月 七月 一年 二年 三年 无遗漏流水特殊活动,1/2/3年全部按一年的价格走,报1年也给三年 利息短信费一样收费,有记录就收费,没记录不收 批量百单以上谈价,500单以上的盘口可以申请超低价
Showing the 12 most recent of 20 posts we hold for @xxiongmaooo. 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.
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.
“AK天眼查三年老牌天眼查|极速查” (@xxiongmaooo), 51 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/xxiongmaooo.
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.