Telegram RegisterThe public register of Telegram

Channel

灰度曝光頻道✳️

@hddb_bg

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

33,896subscribers

-4,019 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
TypeChannel
Username@hddb_bg
Description#骗子曝光 灰度官网: www.huidu.io 交流社群: @huidu_shequ 资源社群: @hddbdaqun 灰度公群: @hddbgongqun 供需信息: @hddbgongxu 公告频道: @hddbgg 曝光频道: @hddb_bg 担保规则: @hddb_guize 安全防范: @hddbaq 灰度Bot: @huidubot 担保客服: @huiducn 对接联系: @huiduTom8
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live12 August 2026
Measurements held7
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/hddb_bg

Growth

33,89637,91535,905.57 August 2026 — 37,915 subscribers7 August 2026 — 37,895 subscribers8 August 2026 — 37,861 subscribers9 August 2026 — 37,804 subscribers10 August 2026 — 37,749 subscribers11 August 2026 — 37,450 subscribers12 August 2026 — 33,896 subscribers7 August 202612 August 2026
7 measurements spanning 6 days, net -4,019. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 33,293–38,518 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 21:5333,896-3,554
11 Aug 2026, 22:4537,450-299
10 Aug 2026, 23:2137,749-55
9 Aug 2026, 19:5137,804-57
8 Aug 2026, 16:5537,861-34
7 Aug 2026, 17:1737,895-20
7 Aug 2026, 06:4537,915first reading

Engagement

16 posts held, back to 3 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 19 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
2.33%
avg views ÷ 33,896 subscribers
Avg views / post
789
16 posts measured
Reaction rate
0.17%
reactions ÷ views · ER floor
Posts in window
16
of 16 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 7 of 16 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 12 August 2026
Posts held16 (3 August 202612 August 2026)
Views total12,629
Reactions total11
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 10:52 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,410
Videos
8
Links
842

Lifetime counters from Telegram’s own channel header, read 13 August 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

11 reactions across 6 posts, in 2 distinct kinds. The most used accounts for 90.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1090.9%
👎19.09%

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 16 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 11reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 16 most recent posts we hold, published 3 August 2026 to 12 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

12 Aug 2026, 15:13 UTC577 viewsread 13 August 2026
Photo

#骗子曝光 ⚠骗子通道:zi 🤡骗子ID:@hiqiqi11 数字id:8273684213 交易金额:400u 被骗说明:巴西ws打a一开始说不相信我们 说怕我们是骗子 秉着是合作的态度给他打了400预付。打了预付后就不回信息了 0⃣官方担保:@huiducn 📱爆料发布:@HDMerly 灰度担保公群频道♻️:@hddbgongqun 🌐找资源,就上灰度官网 HUiDU.iO ‼️ HUIDU.IO全网首款供需提醒机器人 🤖 查询供需信息&TRC地址绑定查询 灰度公群汇总,不在此列表均为假群

12 Aug 2026, 10:20 UTC733 viewsread 13 August 2026
Photo

#骗子曝光 ⚠骗子昵称:小兰【主】🌸 国际短信 🤡骗子ID:@brro7booo 数字id:7570270843 骗子地址: TL1XpmfEfksC5Tszy9hEgLLNE71jZTWwYv TTE9SKscC9nXnFpDpNBVhxsY1pdNNCqXLY TLtkS9pWUndxhzpENzyBgtSkZRNynGtDxZ TAa8KdpuYmgWUqGxa5yEKYSHfDvFgvGZYa 交易金额:1130usdt 被骗说明:通过做短信通道,收到打款后会找原因说无法发送,退款的时候会把款退到OKpay,用钱包接收时需要向USDT收银台授权,一旦授权后钱包里的钱立即被全部转出。 因为骗子会跟你合作一段时间正常业务,让人降低防备心,后面遇到这种需要钱包操作的,都需要防备 0⃣官方担保:@huiducn 📱爆料发布:@HDMerly 灰度担保公群频道♻️:@hddbgongqun 🌐找资源,就上灰度官网 HUi

12 Aug 2026, 08:35 UTC696 views1 reactionsread 13 August 2026
Photo

#骗子曝光 ⚠骗子通道:以前叫鑫龙现在叫兴隆支付 重庆xlpay 🤡骗子ID:@work4free @xlpay999 @XlPayComBot 数字id:6122938991 6943152247 6895025570 交易金额:200万孟加拉达卡 被骗说明:重庆的孟加拉支付,现在趁孟加拉支付比较乱,开始搞事情,合作的注意,今天不吃钱明天也会吃的。听说一直吃钱只不过没人曝光 0⃣官方担保:@huiducn 📱爆料发布:@HDMerly 灰度担保公群频道♻️:@hddbgongqun 🌐找资源,就上灰度官网 HUiDU.iO ‼️ HUIDU.IO全网首款供需提醒机器人 🤖 查询供需信息&TRC地址绑定查询 灰度公群汇总,不在此列表均为假群

1

11 Aug 2026, 06:10 UTC890 views0 reactionsread 13 August 2026
Photo

#骗子曝光 ⚠骗子通道:KOpay 🤡骗子ID:@ko88666 @KOpaydachui @Kopay006 @qc17881 @Kopayliumang @Kopay1633 @Kopaydiana1368 @Kopay001 数字id:8761499687 8786817965 8678853939 8715725928 8405355068 8719969235 交易金额:20万孟加拉达卡 被骗说明:最开始是通过孟加拉合作的,报价是5+2,到20w 就直接跑路了,好几个人都是开了会员的,说有印度,巴西,巴铁,菲律宾等多个国家 今天跑我,明天就是跑你! 请各位同行提高警惕,切勿再与上述账号及收款地址发生任何资金往来! 0⃣官方担保:@huiducn 📱爆料发布:@HDMerly 灰度担保公群频道♻️:@hddbgongqun 🌐找资源,就上灰度官网 HUiDU.iO ‼️ HUIDU.IO全网首款供需提

11 Aug 2026, 01:18 UTC853 viewsread 13 August 2026
Photo

#骗子曝光 ⚠骗子昵称:雷军、小青、笑笑 🤡骗子ID:@leijun0001 (雷军) @xiaoqing850 (小青)@xiaoxiao6720 (笑笑) 数字id:7371900585 7643890436 6962099664 骗子地址:TACX9gcKGdVd56wBxCh4GjBRnUUvBwJdTE 交易金额:1891u 被骗说明:为了减轻乙方的代投资金压力,我们对雷军团队采取了预付模式,提前将款项备付给对方。 上个月我们暂停了广告投放,在与对方核对完余额后,要求对方将剩余款项退回给我们,结果对方一直在推脱 什么上报财务 财务审核 各种理由 一天拖一天。 目前已确认对方彻底跑路,直接卷走了剩下的 1891 U 预付款! 今天跑我,明天就是跑你! 请各位同行提高警惕,切勿再与上述账号及收款地址发生任何资金往来! 0⃣官方担保:@huiducn 📱爆料发布:@HDMerly 灰度担保公群频道♻️:@hddbg

10 Aug 2026, 09:06 UTC891 viewsread 13 August 2026
Photo

#骗子曝光 ⚠骗子昵称:鹏飞 瞬发 🤡骗子ID:@SMS7288 数字id:7743643355 骗子地址: TKoHrYJtG7PENCyDpA5tWxSqbQLdiC9BXp TVYTj4KWYsRUivxsJguLtSQSKuzYr9f3e9 骗子群:https://t.me/SF888988 交易金额:256u 被骗说明:收我246u,发5000条巴西,第一天说堵量,第二天:说涨价到540u,我没答应,说能发发不能发就给我退了,第三天直接拉黑跑路,现在已经隐藏id 0⃣官方担保:@huiducn 📱爆料发布:@HDMerly 灰度担保公群频道♻️:@hddbgongqun 🌐找资源,就上灰度官网 HUiDU.iO ‼️ HUIDU.IO全网首款供需提醒机器人 🤖 查询供需信息&TRC地址绑定查询 灰度公群汇总,不在此列表均为假群

10 Aug 2026, 08:27 UTC844 viewsread 13 August 2026
Photo

#骗子曝光 ⚠骗子昵称:火舞 不知 🤡骗子ID:@yongheng141319 数字ID:7952618265 被骗金额:40 被骗说明:上粉后结,上完粉之后要图,给图之后说图不行,不给结算 0⃣官方担保:@huiducn 📱爆料发布:@HDMerly 灰度担保公群频道♻️:@hddbgongqun 🌐找资源,就上灰度官网 HUiDU.iO ‼️ HUIDU.IO全网首款供需提醒机器人 🤖 查询供需信息&TRC地址绑定查询 灰度公群汇总,不在此列表均为假群

10 Aug 2026, 02:05 UTC701 views1 reactionsread 12 August 2026
Photo

#骗子曝光 ⚠骗子昵称:Gain、Kay 🤡骗子ID:@kay22888 @Galn7567 数字ID:8172120329 被骗金额:2000u 被骗说明:骗子在我这边下fb三不限广告账户,给他们下户之后,骗子先不充值,等我这边其他的客户给我充值的时候,他查到我地址上的其他客户的转账记录,ps一个同样的充值截图。假装是他这边给的的充值款。 0⃣官方担保:@huiducn 📱爆料发布:@HDMerly 灰度担保公群频道♻️:@hddbgongqun 🌐找资源,就上灰度官网 HUiDU.iO ‼️ HUIDU.IO全网首款供需提醒机器人 🤖 查询供需信息&TRC地址绑定查询 灰度公群汇总,不在此列表均为假群

1

10 Aug 2026, 02:01 UTC600 viewsread 12 August 2026
Photo

#骗子曝光 ⚠骗子昵称:小乐-WS图文超链 🤡骗子ID:@xxdh0008 数字ID:8068336787 骗子地址:TJEk3AtcF7qj1nT3yUdJzoDCDjLPZYxmcn 被骗金额:151u 被骗说明:WS群发 收钱了没发 一个点击都没有 谎称风控 。 0⃣官方担保:@huiducn 📱爆料发布:@HDMerly 灰度担保公群频道♻️:@hddbgongqun 🌐找资源,就上灰度官网 HUiDU.iO ‼️ HUIDU.IO全网首款供需提醒机器人 🤖 查询供需信息&TRC地址绑定查询 灰度公群汇总,不在此列表均为假群

10 Aug 2026, 01:50 UTC371 viewsread 10 August 2026
Photo

#骗子曝光 ⚠骗子昵称:官方唯一TG号TexBoos 🤡骗子ID:@TextBoostSMS 骗子ID:6804714667 骗子地址:TQXC7UqgNGDD3W3dKWUh3MZnvxOgg7tpTmC 骗子网址:https://cn.textboostsms.com 说明:曝光一下骗子公司,代发内容做假,数据做假,然后最后申请退款100u都不退,还把我拉黑账号封禁,在这个台子上要先充值才可以发,只有测试的时候才会敷衍你一下,给你用真的,所以请规避这种骗子 被骗:700(打数据金额)+100(退款金额) 0⃣官方担保:@huiducn 📱爆料发布:@HDMerly 灰度担保公群频道♻️:@hddbgongqun 🌐找资源,就上灰度官网 HUiDU.iO ‼️ HUIDU.IO全网首款供需提醒机器人 🤖 查询供需信息&TRC地址绑定查询 灰度公群汇总,不在此列表均为假群

10 Aug 2026, 01:45 UTC475 viewsread 10 August 2026
Photo

#骗子曝光 ⚠骗子昵称:权顺-请认准@Sshun6 🤡骗子ID: @Sshun6 数字id:5753748737 骗子地址:TTXzoJ8Lb8yLiPeqQiJefUxoL7kc88ViBk 被骗金额:67U 被骗说明:在他家跑墨西哥包料 打款了 脱了两天没有发送 说退款 过了两天还没退 过后跟我说我财务在忙 后面就说财务不知道那里去了 0⃣官方担保:@huiducn 📱爆料发布:@HDMerly 灰度担保公群频道♻️:@hddbgongqun 🌐找资源,就上灰度官网 HUiDU.iO ‼️ HUIDU.IO全网首款供需提醒机器人 🤖 查询供需信息&TRC地址绑定查询 灰度公群汇总,不在此列表均为假群

7 Aug 2026, 13:24 UTC828 viewsread 10 August 2026
Photo

#骗子曝光 ⚠骗子昵称:77pay 印度通道 🤡骗子ID: @Good77pay @xiaoxiaobbu @Luckyvip886 @ydpay77 @tdsk87 @jhnjkdal @qiqisp @kxh915 数字id: 6630735131 6533535303 6815728497 6638202590 8486402298 8740834299 8509461126 8563052932 骗子地址:TQuUHH62aSLqgchoFeChVR56nRxns87uJ1 被骗金额:6000u 被骗说明:8月2日,我方有多笔大额代付会员订单迟迟未收到款项。发现问题后,我们第一时间联系对方处理,但对方始终以各种理由推脱,一直未能给出明确解决方案,也没有对未到账资金进行妥善处理。 由于担心资金安全,我们提出将账户余额下发为U(USDT),但对方以各种理由拒绝,甚至提出必须继续跑满2万U流水才可以下发余额,这一要求我

Showing the 12 most recent of 16 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.

Citation-graph rank

Citation-graph rank — 456,432 of 1,176,251entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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.

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.

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 August 2026 — this entry's latest reading, not the date you are reading this.

“灰度曝光頻道✳️” (@hddb_bg), 33,896 subscribers as measured 12 August 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.