近期很多骗子,拉真专群,中途模仿成担保人员,请大家注意认准 @qt66 @qt88 主号 认准 @qt77机器人发送的固定担保地址 七天从未有任何上押频道,骗子利用飞机可以自己编辑文字镶嵌自己想要的链接,让你肉眼看着是@qt55 实则跳转到自己的骗子频道 ,大家注意了 真@qt55 是我们的精品供需 主要防范 避免损失!!!!

Channel
七天担保-旧曝光频道🚫
@xiaoheiwu
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
23,034subscribers
-1,276 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1003520117743 |
|---|---|
| Type | Channel |
| Usernames | @hwdbma @xiaoheiwu |
| Created | Between 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 64 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/xiaoheiwu |
Topic
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 43% 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 |
|---|---|---|
| 19 Sept 2026, 08:15 | 23,034 | no change |
| 19 Sept 2026, 07:38 | 23,034 | -47 |
| 17 Sept 2026, 00:38 | 23,081 | +1 |
| 15 Sept 2026, 04:37 | 23,080 | -1 |
| 15 Sept 2026, 00:59 | 23,081 | -20 |
| 13 Sept 2026, 16:02 | 23,101 | no change |
| 13 Sept 2026, 06:56 | 23,101 | -56 |
| 11 Sept 2026, 17:55 | 23,157 | -11 |
| 11 Sept 2026, 06:38 | 23,168 | -42 |
| 9 Sept 2026, 08:01 | 23,210 | -15 |
| 8 Sept 2026, 11:19 | 23,225 | -52 |
| 6 Sept 2026, 01:41 | 23,277 | -10 |
| 5 Sept 2026, 02:57 | 23,287 | -9 |
| 3 Sept 2026, 20:17 | 23,296 | -2 |
| 3 Sept 2026, 09:37 | 23,298 | -4 |
| 2 Sept 2026, 10:33 | 23,302 | -14 |
| 2 Sept 2026, 05:23 | 23,316 | -27 |
| 1 Sept 2026, 09:14 | 23,343 | -5 |
| 1 Sept 2026, 06:35 | 23,348 | -49 |
| 31 Aug 2026, 08:57 | 23,397 | first reading |
Engagement
36 posts held, back to 12 July 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 54 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 0.798%
- avg views ÷ 23,034 subscribers
- Avg views / post
- 184
- 11 posts measured
- Reaction rate
- 0.656%
- reactions ÷ views · ER floor
- Posts in window
- 13
- of 36 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 2 of 11 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 3 September 2026 |
|---|---|
| Posts held | 36 (12 July 2026 – 3 September 2026) |
| Views total | 2,022 |
| Reactions total | 3 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 11:07 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Reaction mix
15 reactions across 9 posts, in 2 distinct kinds. The most used accounts for 80.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 12 | 80.0% | |
| 👍 | 3 | 20.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 10 of the 36 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 15 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 36 most recent posts we hold, published 12 July 2026 to 3 September 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
金宝鼎,混料四方 ,目前群里信息都不回复 ,已经跑路,大家注意避坑。 🤖 7535292830 👦🏻 金宝鼎查单机器人 🌐 @jbdcdjqr_bot 🕑 已更新 02/09/2026 👤 6755634039 👦🏻 运营 🌐 @jbd_yunying 🕑 已更新 02/05/2026 👤 6485264594 👦🏻 客服—001 🌐 @ghkcoin 🇨🇳 Chinese 🕑 已更新 30/08/2026
可乐一手号源 本月8月26日在他这购买wthsApp账号,支付宝扫码付款,掉号说我VPN的问题 调好VPN叫我喊他补 VPN弄好之后直接已读不回。用户名 @KL8B8 👤 6810757273 👦🏻 可乐一手号源 🌐 @KL8B8 🇨🇳 Chinese 🕑 已更新 26/08/2026
one这家狗娘养的 从我家合作先跑我家的全层原生 叫我多给他打预付 快过点了叫我跑他家十万内层 没注意给他跑超了三万多 商户预付还要四万多 有在合作的快卡预付 👤6130186070 👦🏻onepay运营-木偶 收一手原生 🌐 @onepay_muou 🕑 最後同步時間 22/08/2026 👤6260408344 👦🏻onepay-零零 🌐 @onepay_00 🕑 最後同步時間 26/08/2026 👤 5658942316 👦🏻早(座山雕)晚(下山虎) 🌐@onepay_zsd 🇨🇳 Chinese 🕑 最後同步時間 23/08/2026 👤 6277229937 👦🏻onepay-kiity 打款需双人确认 🌐@onepay_kiity 🇨🇳 Chinese 🕑 最後同步時間 23/08/2026
跑路狗狗 一个星期前停机 群里没人回复 到现在不读不回 清空钱包 有关联的卡住赚到! 钱包地址:THPo5LvN21ehot2BwcyCcXdVgG1Pu7yn8e 转出地址:TSSi43diGzRgN4fi3C4KBMV7MwZLjVNmaw 👤 7709843243 👦🏻 天行健-混江龙 🌐 @TXJ1111 🕑 已更新 12/06/2026 👤 8245322712 👦🏻 天行健- 林冲 🌐 @TXJ0001 🕑 已更新 29/08/2026 👤 8227866342 👦🏻 天行健-孙二娘 🌐 @TXJ99999 🕑 已更新 24/06/2026 👤 8349881267 👦🏻 天行健-玉麒麟 🌐 @TXJ8888888 🕑 已更新 24/06/2026
❤2
Channel photo updated
曝光宝塔 跑支付宝原声给我混料 出现混料不赔付扯七扯八 一直拖着不处理 说是给盘口跑的不会掺料子 你这个是什么屌鸡巴盘口 今天拖明天 明天拖后天 一下说来司法赔付 后面来司法就要纸质的 后面直接摆烂不处理 我司已经先行赔付通道了 要他处理单子的涉诈涉黄混料 但是一直推诿不处理 真的是跟狗一样18码了 有对接的直接卡 卡到就是赚到 骗子id 👤 6622894456 👦🏻 AC 🌐 @AC178168 🇨🇳 Chinese 🕑 已更新 26/08/2026 👤 6929825416 👦🏻 僵小鱼 🌐 @jiangxiaoyu187 🕑 已更新 28/08/2026 骗子地址 TTQJUqWNbQyAy3kQ1NtPxANMxj3ae7mH9v TNu8vBxoMFqY1ZbQF64F2Nj2vT23a9tf6E
👤 8221643372 👦🏻 COACH® 🌐 @fangdi9999 🕑 最後同步時間 27/08/2026 👤 8099905327 👦🏻 FENG 👪 FENG 🌐 @feng10232 🕑 最後同步時間 27/08/2026 👤 8718643925 👦🏻 MASERATI 🌐 @mrlouis999999999 🕑 最後同步時間 27/08/2026 👤 5477359100 👦🏻 交个朋友 🌐 @Jgpy888 🕑 最後同步時間 18/07/2026 👤 7335281365 👦🏻 东大 🌐 @jinxing77 🇨🇳 Chinese 🕑 最後同步時間 17/08/2026 这个盘口负责人说已经公司离职 公司其他人群消息不读 也不回 预付拖着一直不退 合作的可以卡一下预付 不然哪天就被吞钱 傻逼玩意一辈子吃不上三个菜 几千块钱当给你们全家买棺材了
此人 糖果 在飞机上骗吃骗喝,啥鸡吧不是装大哥,被骗3000u,已经消失不见,给你家买棺材的钱 联系地址 THuxNDCSZM5hiBrub9of54WbbLsm3BQppi 👤 6498211786 👦🏻 糖果爸爸 🌐 @tangguo1666888 🇨🇳 Chinese 🕑 最後同步時間 24/08/2026
❤1
拉的假担保来收的押 被骗了几百u 看清楚这几个人 ⚠️ 骗子地址:TQcxbH14qiWGpCRS88L2y5Hv9cxC3BSsWT 👤 8307334703 👦🏻 盛世–主管 啊海 🌐 @Jz1550 🕑 已更新 18/08/2026 👤 8430717174 👦🏻 盛世–客服 青青 🌐 @yxy07 🕑 已更新 18/08/2026 👤 8916714076 👦🏻 财神爷。 🌐 @yu08277 🕑 已更新 16/08/2026 👤 7453708597 👦🏻 七天担保负责人~~招财七 🌐 @qitianfuzeren 🇨🇳 Chinese 🕑 已更新 19/08/2026
事情经过:合作胖虎-红星支付 红星-耶耶耶耶,当时充值 32638u 没有下发记账,直接解算群组,清空私聊记录,私聊他们不回,人直接跑路。合作期间一直置顶地址 TUAyVrgueDg2Trno4Cd3ENjzE1r4BWNGb4 核实已经跑路最后转移地址 TGYqMiUcZHAv1yZ1THa5PuLUZYXBxjpEnm 有合作的直接卡了,卡到就是赚到!!! 骗子人员账号 hxzf88899 胖虎-红星支付 👤 5566591420 👦🏻 耶耶耶耶 🌐 @ltt90099 🕑 已更新 20/07/2026
两个狗东西一万多也跑 你是全家都等着这一点钱要吃药吧 小心别毒死了 👤 8978012563 👦🏻 汇鑫 👪 负责人 🌐 @huixinfuzeren 🕑 最後同步時間 26/08/2026 👤 8899758334 👦🏻 卡卡 🌐 @kaka77668 🕑 最後同步時間 23/08/2026
Showing the 12 most recent of 36 posts we hold for @xiaoheiwu. 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.
Mentions
Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
Handles this channel named that no longer answer
- Dead references
- 4
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 1
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 3
- vacant every time we have ever looked
@xiaoheiwu named 4 handles 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.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
named in 2 posts, 19 August 2026 – 20 August 2026 · confirmed gone 26 August 2026 (two independent sightings — see how we confirm a dead handle)evidenced
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 3 posts, 18 August 2026 – 20 August 2026
named in 1 post, 27 August 2026 – 27 August 2026
named in 1 post, 18 August 2026 – 18 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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“七天担保-旧曝光频道🚫” (@xiaoheiwu), 23,034 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/xiaoheiwu.
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.