#骗子曝光 ⚠ 骗子公司:纵横 外号土龙 安溪人 🤡骗子用户名:@ZHYQ888 @yuxi22689 @cctv13999 @QQQ06666 骗子ID:5627315882 2120148164 7393090816 钱包地址:TYTkqXiNVjetjDXbftiXE45ggoev1WrdWs TCWKUSyddpWptvtLfaUmzMFkFebsZR8deV TMTgPE7EkKtnHt1HpvYfEGHLWe9ZUioZ7L 被骗金额:2795 被骗说明:从25号开始拖欠代付 因为是朋友介绍的才一直放额度 目前人在柬埔寨西港 东方民墅斜对面的酒店,旁边有条小路进去里面的联排别墅 ✅ HUIDU.IO 灰度安全提醒 🆔 灰度官方公群查询:@huidubot 🚀 灰度官方担保客服: @huiducn 🤝 灰度担保公群频道:@hddbgongqun 🚨 诈骗 / 跑路 线索举报:@HDMerly ⚠ 未报备交易…

Channel
灰度曝光頻道✳️
@hddb_bg
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
33,498subscribers
-4,417 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1001744852755 |
|---|---|
| Type | Channel |
| Username | @hddb_bg |
| Description | #骗子曝光 灰度官网: www.huidu.io 交流社群: @huidu_shequ 资源社群: @hddbdaqun 灰度公群: @hddbgongqun 供需信息: @hddbgongxu 公告频道: @hddbgg 曝光频道: @hddb_bg 担保规则: @hddb_guize 安全防范: @hddbaq 灰度Bot: @huidubot 担保客服: @huiducn 对接联系: @huiduTom8 |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 6 September 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 6 September 2026 |
| On Telegram | t.me/hddb_bg |
Topic
Marketing & affiliate — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 48% 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 |
|---|---|---|
| 6 Sept 2026, 15:38 | 33,498 | -57 |
| 4 Sept 2026, 04:00 | 33,555 | -17 |
| 2 Sept 2026, 18:18 | 33,572 | -50 |
| 1 Sept 2026, 14:48 | 33,622 | +1,027 |
| 31 Aug 2026, 15:53 | 32,595 | +22,554 |
| 30 Aug 2026, 13:03 | 10,041 | -62 |
| 29 Aug 2026, 10:36 | 10,103 | -50 |
| 28 Aug 2026, 09:48 | 10,153 | -7 |
| 27 Aug 2026, 11:53 | 10,160 | -6 |
| 26 Aug 2026, 08:25 | 10,166 | -34 |
| 25 Aug 2026, 06:11 | 10,200 | -15 |
| 24 Aug 2026, 09:07 | 10,215 | -66 |
| 22 Aug 2026, 13:37 | 10,281 | -17,878 |
| 21 Aug 2026, 01:49 | 28,159 | -3,807 |
| 20 Aug 2026, 00:13 | 31,966 | -28 |
| 18 Aug 2026, 21:12 | 31,994 | -71 |
| 17 Aug 2026, 20:03 | 32,065 | -24 |
| 16 Aug 2026, 20:34 | 32,089 | -79 |
| 15 Aug 2026, 12:04 | 32,168 | -14 |
| 14 Aug 2026, 01:17 | 32,182 | first reading |
Engagement
41 posts held, back to 3 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 65 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 2.90%
- avg views ÷ 33,498 subscribers
- Avg views / post
- 970
- 30 posts measured
- Reaction rate
- 0.202%
- reactions ÷ views · ER floor
- Posts in window
- 30
- of 41 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 15 of 30 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 9 September 2026 |
|---|---|
| Posts held | 41 (3 August 2026 – 9 September 2026) |
| Views total | 29,112 |
| Reactions total | 29 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Sept 2026, 14:19 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.
What this channel posts
- Photos
- ≈3,520
- Videos
- ≈8
- Links
- ≈865
Lifetime counters from Telegram’s own channel header, read 9 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Reaction mix
39 reactions across 15 posts, in 7 distinct kinds. The most used accounts for 59.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 23 | 59.0% | |
| 👍 | 8 | 20.5% | |
| 🎉 | 4 | 10.3% | |
| 👎 | 1 | 2.56% | |
| 👏 | 1 | 2.56% | |
| 🔥 | 1 | 2.56% | |
| 🥰 | 1 | 2.56% |
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 20 of the 41 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 39 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 41 most recent posts we hold, published 3 August 2026 to 9 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
#骗子曝光 ⚠ 骗子昵称:刑天代投 🤡 骗子用户名:@lululemonnm @xthaonet @anjovan @xingtianpindao 数字id:7600273353 7143464011 884909236 7227057636 骗子频道:@XTianchuhai 骗子地址:TBqFxKmX4eKia5VjEsRUZdRSPTeV6yBuXH 被骗金额:1000u 被骗说明: 真的被这家搞恶心了,发出来给同行避个雷。 找他们做菲律宾 BC 投放,前面谈的时候说得挺好,日消耗200U左右,1000U大概能进频道最少几千人。 结果实际跑起来以后,我看频道人数,3天从7420涨到7520左右,也就进了100个人。 我就问了一句: 你们说的量呢? 对方开始跟我说什么“有时候多、有时候少”“根据市场来”“现在频道已经进了不少人,好好做转化”。 我听这些解释有什么用? 我花钱找你们投广告,不是花钱听你们教我怎么做转化的…
❤1
💎💎💎💎💎💎💎 关于灰度公群95 捷付PAY 赔付处理 经灰度担保核实及协调处理,灰度公群95相关纠纷款项现已全部赔付完毕,本次纠纷处理正式结束。 同时再次提醒所有商户及交易用户: 交易前务必先报备,确认后再付款、再合作。 未经过灰度官方报备、私下完成的交易,由于平台无法确认双方交易条件、金额、责任约定及实际履约情况,发生纠纷后将极大增加取证及处理难度,甚至可能无法纳入灰度担保处理范围。 请大家在交易过程中务必做到: 交易前确认对方是否为灰度官方公群 合作内容、金额、周期及关键条件提前报备 付款前确认灰度官方人员及收款信息 重要沟通及履约过程尽量在报备群内留痕 出现异常第一时间暂停交易并联系灰度官方处理 报备不是多一道流程,而是为交易多留一份保障。 灰度也将持续完善公群认证、交易报备、风险预警及纠纷处理机制,为正常经营、诚信合作的商户提供更加透明、可追溯的交易环境。 交易前先验群 · 付款前先报备 交易报备:@h…
❤2🔥1🥰1
#骗子曝光 ⚠ 骗子昵称:捷付PAY 🤡 骗子用户名:@jiefupay693 @jiefupay366 @jiefupayCS @jiefupay013 @jiefupayLD @jiefupay663 @jiefupayND @jiefupay005 @jiefupay001 @jiefupay04 @jiefupay03 @jiefupay006 @jiefupayCS1 @jiefupayGUS @jiefupay07 @jiefupay008 数字ID: 6540907609 1903342732 7796259374 6302433093 6126348328 5771272580 7231350093 8708514834 8611324772 5579681798 8295753713 8644019632 骗子地址:TBXVmsp3ZEaWwSrvZG7L9VDS27Hi…
❤7🎉4👍3👏1
#骗子曝光 ⚠ 骗子昵称:皮娅 ┃专业代开会员┃TG礼物代购┃白资代付@piyavlp 🤡 骗子用户名:@piyavlp 数字ID:7643469279 骗子地址:TWrS9fjWVixh9sPN2Rtr646pc69g1GSVVT 被骗金额:222 被骗说明:找她开两个飞机会员,打款之后给我发了个什么自助取货的,那个取货要0.1u的验证,说第一次取货都要这样,后面就不用了,付了之后拉黑清聊天记录了,把地址里的u全套走了 0⃣官方担保:@huiducn 📱爆料发布:@HDMerly 灰度担保公群频道♻️:@hddbgongqun 🌐找资源,就上灰度官网 HUiDU.iO ‼️ HUIDU.IO全网首款供需提醒机器人 🤖 查询供需信息&TRC地址绑定查询 灰度公群汇总,不在此列表均为假群
#骗子曝光 ⚠ 骗子昵称:马里奥 🤡 骗子用户名:@Ws735 数字ID:8652372304 骗子地址:TUdkPUnTKRkuqpCNthWZmYT3VhfvtW9exJ 被骗金额:612 被骗说明:找他发ws超链 前面有发 后面在合作直接删记录 拉黑 0⃣官方担保:@huiducn 📱爆料发布:@HDMerly 灰度担保公群频道♻️:@hddbgongqun 🌐找资源,就上灰度官网 HUiDU.iO ‼️ HUIDU.IO全网首款供需提醒机器人 🤖 查询供需信息&TRC地址绑定查询 灰度公群汇总,不在此列表均为假群
#骗子曝光 ⚠ 骗子昵称:超威 航子 🤡骗子用户名:@chovv001 @hangzi0927 数字ID:7563988806 8736118366 骗子地址:TRy8di2DmD594pBeSPeySLodxdNxRGxmDZ 被骗说明:收了钱不发也不退,每天都在拖 0⃣官方担保:@huiducn 📱爆料发布:@HDMerly 灰度担保公群频道♻️:@hddbgongqun 🌐找资源,就上灰度官网 HUiDU.iO ‼️ HUIDU.IO全网首款供需提醒机器人 🤖 查询供需信息&TRC地址绑定查询 灰度公群汇总,不在此列表均为假群
#骗子曝光 ⚠ 骗子昵称:宸狩-WS一手机房 🤡骗子用户名:@YHCS0000001 @YHSJ888666 数字ID:6255754632 7393060677 被骗金额:1037.00U 被骗说明:一开始说巴西ws 当天能发 下了五万得单 接了之后两天没发出去,又说打真机 让他打了两万试试 结果全是水军 让退剩余得钱就玩失踪 之后 消息都不敢回复,直接玩失踪 0⃣官方担保:@huiducn 📱爆料发布:@HDMerly 灰度担保公群频道♻️:@hddbgongqun 🌐找资源,就上灰度官网 HUiDU.iO ‼️ HUIDU.IO全网首款供需提醒机器人 🤖 查询供需信息&TRC地址绑定查询 灰度公群汇总,不在此列表均为假群
#骗子曝光 ⚠ 骗子昵称:梦西游户商 🤡骗子用户名:@RH_RHBST @GuoG_996 @AA_MXY 数字id:6573189211 6949371879 6668696630 被骗金额:2w U 骗子地址:TNo3JKve9TW7qEYRTA9BzoZKgxsXgCzRjM 被骗说明:打款6w,消耗4w,剩余2w不核对金额直接移除群聊 0⃣官方担保:@huiducn 📱爆料发布:@HDMerly 灰度担保公群频道♻️:@hddbgongqun 🌐找资源,就上灰度官网 HUiDU.iO ‼️ HUIDU.IO全网首款供需提醒机器人 🤖 查询供需信息&TRC地址绑定查询 灰度公群汇总,不在此列表均为假群
#骗子曝光 ⚠ 骗子昵称:Alesso等四人 🤡骗子用户名:@mplay1009 @megaparisupport1 @preety_kwin @Alesso_9999 骗子站点信息: Megaplay.qzz.io 被骗金额:30000inr 被骗说明:印度盘口骗子 专门找支付商 接入后只发起代付 若有授信额度则会掏空代付不回u也不代收 揭穿后直接跑路 请各位印度支付商小心以上几人及站点 0⃣官方担保:@huiducn 📱爆料发布:@HDMerly 灰度担保公群频道♻️:@hddbgongqun 🌐找资源,就上灰度官网 HUiDU.iO ‼️ HUIDU.IO全网首款供需提醒机器人 🤖 查询供需信息&TRC地址绑定查询 灰度公群汇总,不在此列表均为假群
👍3
#骗子曝光 ⚠ 骗子昵称:Paul ∞ 🤡骗子用户名:@paulIam69 数字id:8617433001 骗子地址:TAu8tHLbxm16qUyJSMPmahirmyZtcjccgs 被骗说明:这个人P图来骗我们。转的11.87U然后去P图,弄成11871U 0⃣官方担保:@huiducn 📱爆料发布:@HDMerly 灰度担保公群频道♻️:@hddbgongqun 🌐找资源,就上灰度官网 HUiDU.iO ‼️ HUIDU.IO全网首款供需提醒机器人 🤖 查询供需信息&TRC地址绑定查询 灰度公群汇总,不在此列表均为假群
👍1
#骗子曝光 ⚠ 骗子昵称:奥特曼 芋泥💕源头机房巴西ws群发 🤡骗子用户名:@lucifer_lp @aoao666688886 数字ID:8432117678 8015583381 骗子地址:用他人地址代收 被骗金额:2200.00📝 被骗说明:一开始说巴西ws 当天能发 下了五万得单 接了之后两天没发出去,又说打真机 让他打了两万试试 结果全是水军 让退剩余得钱就玩失踪了 0⃣官方担保:@huiducn 📱爆料发布:@HDMerly 灰度担保公群频道♻️:@hddbgongqun 🌐找资源,就上灰度官网 HUiDU.iO ‼️ HUIDU.IO全网首款供需提醒机器人 🤖 查询供需信息&TRC地址绑定查询 灰度公群汇总,不在此列表均为假群
❤1
Showing the 12 most recent of 41 posts we hold for @hddb_bg. 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 5 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
- 23
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 23
- vacant every time we have ever looked
@hddb_bg named 23 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 2 posts, 19 August 2026 – 20 August 2026
named in 2 posts, 19 August 2026 – 20 August 2026
named in 2 posts, 19 August 2026 – 20 August 2026
named in 2 posts, 19 August 2026 – 20 August 2026
named in 2 posts, 19 August 2026 – 20 August 2026
named in 2 posts, 19 August 2026 – 20 August 2026
named in 2 posts, 19 August 2026 – 20 August 2026
named in 2 posts, 19 August 2026 – 20 August 2026
named in 2 posts, 19 August 2026 – 20 August 2026
named in 2 posts, 19 August 2026 – 20 August 2026
named in 2 posts, 8 August 2026 – 9 August 2026
named in 2 posts, 8 August 2026 – 9 August 2026
named in 2 posts, 8 August 2026 – 9 August 2026
named in 2 posts, 8 August 2026 – 9 August 2026
named in 2 posts, 8 August 2026 – 9 August 2026
named in 2 posts, 8 August 2026 – 9 August 2026
named in 2 posts, 8 August 2026 – 9 August 2026
named in 1 post, 27 August 2026 – 27 August 2026
named in 1 post, 13 August 2026 – 13 August 2026
named in 1 post, 11 August 2026 – 11 August 2026
named in 1 post, 11 August 2026 – 11 August 2026
named in 1 post, 8 August 2026 – 8 August 2026
named in 1 post, 8 August 2026 – 8 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 6 September 2026 — this entry's latest reading, not the date you are reading this.
“灰度曝光頻道✳️” (@hddb_bg), 33,498 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/hddb_bg.
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.