⭐公群广告⭐ 公群122 御男堂 专供 迷药/催情/伟哥/ 招收代理押金7000u 🙂公群频道: https://t.me/+yepS6kqX-6kzNDc1

Channel
公群 🥇@HBGGG 火币担保公群
@hbggg
On this record: Topic · Growth · Engagement · Posts · Posts edited after publishing · Citations · Cite this entry
9,623subscribers
+458 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001811128226 |
|---|---|
| Type | Channel |
| Usernames | @HBDBGQ @hbggg |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 9 October 2026 |
| Measurements held | 54 |
| Confirmed unchanged | 1 time, most recently 9 October 2026 |
| On Telegram | t.me/hbggg |
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 11 September 2026 and assigned it the closest of 31 fixed categories, at 65% 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 |
|---|---|---|
| 9 Oct 2026, 10:59 | 9,623 | no change |
| 9 Oct 2026, 09:02 | 9,623 | -389 |
| 5 Oct 2026, 02:40 | 10,012 | -35 |
| 4 Oct 2026, 20:02 | 10,047 | -1,017 |
| 28 Sept 2026, 06:59 | 11,064 | -31 |
| 27 Sept 2026, 08:38 | 11,095 | +2,211 |
| 19 Sept 2026, 03:36 | 8,884 | -204 |
| 17 Sept 2026, 21:02 | 9,088 | -769 |
| 14 Sept 2026, 09:21 | 9,857 | -90 |
| 13 Sept 2026, 21:01 | 9,947 | -121 |
| 12 Sept 2026, 20:02 | 10,068 | -136 |
| 12 Sept 2026, 02:18 | 10,204 | +45 |
| 10 Sept 2026, 22:21 | 10,159 | -54 |
| 9 Sept 2026, 21:00 | 10,213 | -102 |
| 7 Sept 2026, 21:01 | 10,315 | -124 |
| 6 Sept 2026, 13:41 | 10,439 | -105 |
| 4 Sept 2026, 23:00 | 10,544 | -50 |
| 4 Sept 2026, 06:15 | 10,594 | -34 |
| 3 Sept 2026, 10:06 | 10,628 | -41 |
| 2 Sept 2026, 21:58 | 10,669 | first reading |
Engagement
24 posts held, back to 7 August 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 37 pages 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 24 posts for this entry, the most recent from 27 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
⭐公群广告⭐ 公群111蓝天海外支付一手水房直通车 押金30000u 🙂公群频道: https://t.me/+dZLJvPTq9zFmNTU8
⭐公群广告⭐ 公群288 云顶各大软件点号解封 押金9000u 🙂公群频道: https://t.me/+WCbS6Wk0k0I2MGQ8
🙂公群广告🙂 公群333 黑U帝国黑U承兑1:2 押金16000u 公群频道🙂 https://t.me/+7bgxUz_MqwI2Y2Q1
🔰火币公群🔰 公群535 汇金支付微信支付宝现存承兑回U 押金16000u 公群频道🙂 https://t.me/+gaU1bB0lbksxNDU0
⭐公群广告⭐ 公群520 麻豆传媒1v1视频裸聊/举牌/语音连麦/原味衣物/群直播大秀/外围 押金8888u 🙂公群频道: t.me/Madoujt
⭐公群广告⭐ 公群222 拉法集团色料小额代收 押金16000u 🙂公群频道: https://t.me/+mfN7qpU5CfM3NmVl
⭐公群广告⭐ 公群110 星链全球查档招内部条子 押金12000u 🙂公群频道: https://t.me/+jYgXNf4qak80YTFk
⭐公群广告⭐ 公群444 帝恒集团共享充电宝投放 押金:20000u 🙂公群频道: https://t.me/+rmZTrKMIB-w0YjFl
⭐公群广告⭐ 公群666 好困78折虚拟业务代充 押金6000u 🙂公群频道: https://t.me/+COs3Ku3gjXwyMGE1
✅火币担保六周年庆✅ 六年前,我们种下一颗名为“信任”的种子;火币担保挑起信任的大旗 为交易保驾护航! 六年间,我们以风控为雨露,以责任为阳光,为您撑起资金安全的绿荫。 每年365²个日夜的坚守,我们见证了无数小微企业从幼苗成长为大树,也陪伴了众多伙伴在风浪中行稳致远。 感谢您六年的托付与相伴。未来,我们将继续以专业为舟,以诚信为桨,在普惠金融的浪潮中,为您保驾护航。 📣 活动1. 供需原价100u/条 六周年庆限时88u/条 包周500/u 包月1600/u 活动持续66天 📣活动2. 新公群限时免管理费月租66天 开公群就送六条供需(公群广告 供需广告都可) 已开公群同步免费66天公群管理费用 📣活动3. 火币担保六周年庆内部群送出 公群老板即可参与 抽奖 Top1 6666u 公群租金手续费抵用(或者折现3333u) Top2 1111u 公群租金手续费抵…
🔰火币公群🔰 公群518 顶汇集团 招收刷礼物做单人员 刷完秒结算押金20000u 🙂公群频道:https://t.me/+KRLbse5DUPNiMmI9
Showing the 12 most recent of 24 posts we hold for @hbggg. 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.
Posts edited after publishing
@hbggg edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
- First edit seen
- 18 August 2026
- Most recent edit
- 18 August 2026
Mentions
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 9 October 2026 — this entry's latest reading, not the date you are reading this.
“公群 🥇@HBGGG 火币担保公群” (@hbggg), 9,623 subscribers as measured 9 October 2026. Telegram Register, tgregister.com/channel/hbggg.
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.