Channel
@HDBQZX
On this record: Growth · Engagement · Posts · Citations · Cite this entry
22,998subscribers
-1,647 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001658452326 |
|---|---|
| Type | Channel |
| Username | @HDBQZX |
| 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 | 5 September 2026 |
| Measurements held | 28 |
| Confirmed unchanged | 1 time, most recently 5 September 2026 |
| On Telegram | t.me/HDBQZX |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Sept 2026, 08:40 | 22,998 | -52 |
| 3 Sept 2026, 14:20 | 23,050 | -32 |
| 2 Sept 2026, 09:48 | 23,082 | -73 |
| 1 Sept 2026, 12:05 | 23,155 | -65 |
| 31 Aug 2026, 14:55 | 23,220 | -48 |
| 30 Aug 2026, 17:23 | 23,268 | -70 |
| 29 Aug 2026, 14:35 | 23,338 | -113 |
| 28 Aug 2026, 11:27 | 23,451 | -57 |
| 27 Aug 2026, 11:15 | 23,508 | -19 |
| 26 Aug 2026, 12:34 | 23,527 | -38 |
| 25 Aug 2026, 15:53 | 23,565 | -44 |
| 24 Aug 2026, 17:14 | 23,609 | -49 |
| 23 Aug 2026, 04:59 | 23,658 | -38 |
| 21 Aug 2026, 16:05 | 23,696 | -26 |
| 20 Aug 2026, 14:53 | 23,722 | -22 |
| 19 Aug 2026, 15:02 | 23,744 | -61 |
| 18 Aug 2026, 13:07 | 23,805 | -44 |
| 17 Aug 2026, 10:04 | 23,849 | -145 |
| 15 Aug 2026, 16:47 | 23,994 | -51 |
| 14 Aug 2026, 06:54 | 24,045 | first reading |
671 posts held, back to 6 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 58 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 3 September 2026 |
|---|---|
| Posts held | 671 (6 August 2026 – 3 September 2026) |
| Views total | 803 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 11:10 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.
#付费广告 ⭐️ Huidu × Darpha Studios｜全新上架 通过 Darpha Studios 的优质老虎机游戏，助力您的业务增长。精美的视觉效果、刺激的游戏体验，以及丰富的游戏组合，持续提升玩家参与度。为玩家打造难忘的娱乐体验，让他们不断回归。欢迎联系 HUiDU 官方代表，洽谈合作机会。 🥇 热门游戏： Nordic Raiders（北欧掠夺者） Cosmic Crazies（宇宙狂热） Vampires Lair（吸血鬼巢穴） 🌎 热门推荐地区： 印度尼西亚: 泰国 马来西亚 墨西哥 菲律宾 ❤️ 相关收费 请洽您的业务经理 现在立即联络: @ErenUlr 官方网站：https://darphastudios.com/ ⭐️Huidu × Darpha Studios | Now Available Grow your business with Darpha Studios' premium…
#付费广告 🎰🔴🟠🟡🟢🔵 🔤🔤🔤🔤🔤🔤🔤🔤 🐜 🖱 主站网址： U站 UZ娱乐城 UZ.COM 💵 🎰 东南亚最大线上博彩平台欢迎您。敢赢就敢出，累计出款超5亿U！ 🎰 东南亚最公平，资金实力最雄厚，最安全有保障的线上娱乐平台！ 🎰 长期现金储备高达2亿U，告别虚假出款、异常扣款、无故封号！ 🎰 1000万U担保金 NO钱包官方担保 可前往官网 no.com 查验！ 😀😀😀😀😀😀😀😀 😀😀😀😀😀😀😀😀 💵 【不记名】【全自动】【去中心化】【完全匿名】【隐私无忧】 ⚽️ 球赛未开，奖金已爆！UZ世界杯福利抢跑上线 ⚪ 🎰 【体育热战开启】 每日投注赢豪礼，最高领 38,888U 🎰 【世界杯连胜不断】 每日连赢奖金最高达 18,888U 🎰 【世界杯预言之战】 神预测可瓜分 8,888,888U 奖池 🎰 【世界杯独赢包赔】 无忧享 2,888U 🎰 【体育救援基金】 体育救援金最高返 5%，助您逆风翻盘 ⚠️ UZ娱乐…
#付费广告 灰度公群1️⃣2️⃣4️⃣-WDPay美国🇺🇸一类原生支付-上押5000u 🇺🇸 WDPay 美国一类代收付 一、收款通道 🔹 CashApp 收款 金额支持： 1—999(单笔) 代收成功率90+ 二、付款通道 🔹Sol链USDC 金额支持：5—2000(单笔) 三、结算说明 D+0结算周期：24H 结算方式：USDT 提现结算回U：2000U起 四、风控要求 拒付率不得超过 0.3%。 拒付订单按 $30 / 笔 + 投诉金额 扣除。 仅接受 Slots 游戏 BC 客户交易。 禁止下挂或跑其他类型业务，一经查出，相关资金将全部冻结。 停止交易后，若 15天内无拒付或投诉，则安排结算清账。 📩 使用 WDPay 服务，即默认同意并接受以上全部规则 公群老板:@MAX_99799 公群商务:@wdzf610 公群链接：https://t.me/+T7X7mnz_Mg8xMmZi
#付费广告 1️⃣1️⃣1️⃣｜亚洲领先游戏供应商 游戏API集成 × 国际包网 × 中国支付方案 👍我们不仅是游戏供应商，更是值得信赖的运营伙伴！ 从平台建置、游戏整合、支付串接到运营支持，提供一站式解决方案，助您快速拓展市场，实现业务持续增长。 🩷❤🧡为什么选择 DB Gaming？ ✅一站式包网平台，快速打造专属娱乐品牌 ✅体育、真人等热门游戏，一键API接入 ✅智能商户后台，实时数据分析及管理 ✅专业技术团队，7×24小时技术支持 👍立即咨询专属方案，7 天内上线您的娱乐平台！ ➡2026开站优惠方案 · 火热开放中 🤥官方咨询：@dbgmBot 📱游戏API集成 🌐国际包网系统 🔡中国支付方案 🌐官网：www.dbgaming.com 📢官方诚聘菁英人才 🔔官方招聘：@dbgaminghr
0️⃣灰度公群汇总0️⃣ ⚠️注意：不在此导航里面的群都是假公群，必须在公群内先报备再交易，我们只担保公群内已报备过的交易，不担保群老板个人信誉，私下交易后果自负，不是在公群内交易发生的纠纷一律不受理，切勿私发地址等关键交易信息。 #官方通知 #付费广告 一、需求类公群 1、流量需求 2、海外资源需求 二、国际支付、承兑类 1、国际支付 2、支付系统 3、国际承兑 4、虚拟卡 三、流量投放类 1、广告户 2、海外引流粉 3、海外流量代投 四、群发引流/APP拉群/海外数据 1、tg/ws等拉群/群发 2、国际短信 3、各类软件群发 4、邮箱群发 5、海外数据 6、数据筛选 五、社媒账号/实卡接码/虚拟账号 1、海外社媒账号 2、实卡接码/邮寄 3、海外社媒会员充值 六、搭建/平台/云控类公群 1、博彩游戏包网 2、博彩游戏API 3、平台搭建 4、云控软件 5、软件技术 6、海外服务器 七、附加服务类公群 1、美…
#官方通知 🔥灰度企业营销方案——助力品牌腾飞！🔥 专属推广+顶级资源 （6000U/年） 🔹 品牌广告位 + 资源置顶曝光 🔹 TG群推送 + 行业资讯独家报道 🔹 VIP群交流 + 业务合作优先对接 💡 加入灰度，助力品牌腾飞！ 🔗 联系我们获取更多合作详情！
#官方通知 ⚖️灰度公群推广季 福利大派送！🐂 1.开群即送广告位 推广季活动期间开群 赠送 1个月灰度官网资源置顶，价值200U 2. 广告折扣 开群群主可享受 灰度社群及官网广告8折优惠 3. 季度管理费套餐 一次性缴纳3个月公群管理费，可享公群管理费8折优惠,并赠送灰度嘉宾席名额一位 4. 半年管理费套餐 一次性缴纳6个月公群管理费，可享公群管理费8折优惠，并赠送公群供需季度发布权益 灰度公群列表:@hddbgongqun 公群开设咨询:@huiduTom8
#付费广告 #官方通知 Wynso Fantasy Sports 正式上线！ 打造梦幻战队，体验实时竞技与全球排行榜挑战 结合真实赛事数据、策略玩法及丰厚奖励 为平台带来更高玩家活跃度与留存率，助力运营创造更多价值。 馬上安排串接 : @HDJames @HDaries
灰度平台链接全球海外资源❗️ 💎开通灰度会员，解锁海量资源 💎曝光拉满，发布 / 刷新 / 名片查看全权限 💎月 / 季 / 年多档会员任选 💎要包网、找甲方、觅靠谱服务商、交易担保，灰度一站式解决！ 会员权益在手，海外资源不愁！ 🌐灰度官网： www.huidu.io ➡️详情咨询：@HDmax933 @huiduTiya
🚀 GGC 2027再度登陆斯里兰卡，活动规模人数全面升级！立即预购展位！ 继首届大会成功举办后，Global Game Connect (GGC) 2027 将于2027年3月24–25 日重返斯里兰卡，以更大的规模、更丰富的国际资源和更高质量的商务对接，为全球游戏行业打造高价值合作平台 本届大会预计汇聚 150+ 参展商及赞助商、5000+ 参展代表，覆盖 30+ 国家和地区，其中 35% 为行业核心决策者 想要寻找合作伙伴、拓展国际市场，探索行业新趋势？GGC 2027 都将带来更多商业机遇 🌐官方网站：https://www.ggcgame.com/ 📍展位预定： @GGCKyle @GGCDixson 💌门票预定：@GGCTicket 🌈媒体合作：@GGCNetwork 🔈展会交流：@GGCglobal 2027 年 3 月，让我们相约斯里兰卡，共创全球游戏产业新未来！
✅ 灰度担保 | 官方认证公群 ✅ 公群名：灰度公群1️⃣2️⃣7️⃣-顶呱呱支付/菲律宾/越南/缅甸/香港/各国直通车-上押10000U 🚩当前押金：10000u【已上押入账】 业务介绍： 全球支付水房，接全球科技料，各种毒料 冰点价格收量，无视料 对接联系 @DGG_555 @DGG_000 @DGG_222 公群链接：https://t.me/+iQTvMNz_N6pjYWRi 🛡 【灰度担保交易保障】 本群已在灰度担保全额缴纳押金，交易过程中如遇纠纷，平台介入优先处理！ 🚫 切勿私下交易，交易请拉报备群 📌认准担保客服ID @huiducn 🔗 验群链接： 灰度公群频道 点击跳转灰度官网核验本群 灰度担保 —— 为全球游戏行业搭建信任桥梁，让每一笔交易都值得信赖
🇵🇹葡萄牙里斯本 SBC Summit 2026展位ME110，我们不见不散！ 9月29日-10月1日，HDAPI即将亮相展位ME110，为全球伙伴助力打造新一代的游戏体验 📍无论您是寻求可靠的技术支持、高效的系统集成，还是可扩展的API 解决方案，我们的团队都将在现场为您介绍最新动态并解答您的疑问 🌟9月29日-10月1日| 展位ME110｜葡萄牙里斯本 🎟️ 使用7折门票优惠码：HUIDUPARTNERVIP 👉 报名链接： https://tickets.sbcevents.com/home?promo=HUIDUPARTNERVIP 期待和你相聚里斯本 @HDRAY777 @HDKyle14
Showing the 12 most recent of 671 posts we hold for @HDBQZX. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 4 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.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“灰度幣圈資訊♻️” (@HDBQZX), 22,998 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/HDBQZX.
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.