皇冠公群频道 @hggq pinned «开设公群联系:@hghh @hggg @hgkk @hgpp 卡商公群:1.卡卡/pos/信用卡 2.盾卡/公户 3.无卡+取现 4.卡商公群 代收付公群:1.一道卡接 2.二道卡接 3.码接回U 4.三方四方 5.收U放料 6.救火NFc扣款 7.群引导/app跑分 白资公群:1.白资收U 2.白资代付 3.白资收U出U 4.海外白资代付 承兑类公群:1.滴滴现金 2.滴滴承兑 3.三方承兑 4.POS承兑 5.实物承兑 6.礼品卡核销 7.平台币核销 招商引流类公群:1招车队/招料主.…»

Channel
皇冠公群频道 @hggq
@lSBSB
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Domains linked from posts · Cite this entry
135,496subscribers
+19,329 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
Register entry
| Telegram ID | -1001895075778 |
|---|---|
| Type | Channel |
| Usernames | @badbbbgq @hhggq @lSBSB |
| Created | Between 1 October 2022 and 31 August 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 28 October 2026 |
| Measurements held | 108 |
| Confirmed unchanged | 1 time, most recently 28 October 2026 |
| On Telegram | t.me/lSBSB |
Topic
Gambling & betting — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 9 August 2026 and assigned it the closest of 31 fixed categories, at 67% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Oct 2026, 11:15 | 135,496 | no change |
| 28 Oct 2026, 11:06 | 135,496 | -161 |
| 27 Oct 2026, 20:51 | 135,657 | -25 |
| 27 Oct 2026, 13:14 | 135,682 | -28 |
| 27 Oct 2026, 10:45 | 135,710 | -147 |
| 26 Oct 2026, 18:38 | 135,857 | -16 |
| 26 Oct 2026, 15:22 | 135,873 | no change |
| 26 Oct 2026, 13:45 | 135,873 | -2 |
| 26 Oct 2026, 12:00 | 135,875 | -121 |
| 25 Oct 2026, 14:27 | 135,996 | -7 |
| 25 Oct 2026, 11:45 | 136,003 | -89 |
| 24 Oct 2026, 15:10 | 136,092 | -30 |
| 24 Oct 2026, 11:06 | 136,122 | -264 |
| 23 Oct 2026, 15:05 | 136,386 | -2 |
| 23 Oct 2026, 14:18 | 136,388 | -103 |
| 22 Oct 2026, 17:30 | 136,491 | -6 |
| 22 Oct 2026, 16:06 | 136,497 | -159 |
| 21 Oct 2026, 14:19 | 136,656 | -9 |
| 21 Oct 2026, 09:39 | 136,665 | -117 |
| 20 Oct 2026, 12:10 | 136,782 | first reading |
Engagement
42 posts held, back to 27 December 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 169 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 3.84%
- avg views ÷ 135,496 subscribers
- Avg views / post
- 5,200
- 19 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 20
- of 42 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.
| Window | Rolling 30 days · latest post in window 25 October 2026 |
|---|---|
| Posts held | 42 (27 December 2024 – 25 October 2026) |
| Views total | 98,810 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 28 Oct 2026, 03:48 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
- Video runtime
- 7m 58s
- Average length
- 3m 59s
Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
12 reactions across 7 posts, in 5 distinct kinds. The most used accounts for 25.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👏 | 3 | 25.0% | |
| 🔥 | 3 | 25.0% | |
| 🥰 | 3 | 25.0% | |
| 😎 | 2 | 16.7% | |
| 🦄 | 1 | 8.33% |
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 8 of the 42 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 12 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 42 most recent posts we hold, published 27 December 2024 to 25 October 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
皇冠担保 官方公告: 代收付公群交易机器人正式上线 为解决拉私群交易双删记录的问题,同时进一步提升跑分类型公群的交易效率与安全性,皇冠担保特推出公群专属 交易机器人。 核心优势 1. 全程隐私保护 单独给每个公群配置一个交易群,群内所有聊天均受隐私保护,不会透露任何客户信息,保障双方安全。 2. 报备流程简单高效 群内加减账操作与公群押金关联,供方报备、需方确认即可自动更新押金状态,减少沟通成本,超押风险。 使用方法 公群方:联系当组担保拉单独交易群,生成专属本群的交易机器人,群里仅拉入公群供方人员 客 户:私聊对应公群专属机器人报单,喊卡,公群贴卡,料方发进款发图,公群查账后,报备加帐,料方确认加帐,公群报备下发,料方确认下发 注意:每个客户设有单独对接窗口,通过群专属机器人可直接联系供方工作人员,全程隐私保护,交易必须进行机器人加减账单 加减账指令 开始作业:报备:+100u(直接填写作业金额,无需报汇率) …
1.有业务的客户免费进皇冠资源群 联系 @hgqq 2.有博彩记录的联系 @dora 进博彩群 游戏中心 3. @hgqb 个人设置中心新增到帐号提醒功能,收款可以通知到其帐号 4. 所有需要引流的公群 博彩群,游戏中心频道 @hgyx 不低于五万人民币的现金或者彩金即可发布! 5.游戏中心除夕抽100个888u VIP老板群抽奔驰E300!
24小时在线客服 @hgkf 皇冠供需 皇冠公告 新开公群 游戏中心 皇冠博彩 海外业务交流群 ⚡️皇冠担保一键收藏⚡️
开设公群联系:@hghh @hggg @hgkk @hgpp 卡商公群:1.卡卡/pos/信用卡 2.盾卡/公户 3.无卡+取现 4.卡商公群 代收付公群:1.一道卡接 2.二道卡接 3.码接回U 4.三方四方 5.收U放料 6.救火NFc扣款 7.群引导/app跑分 白资公群:1.白资收U 2.白资代付 3.白资收U出U 4.海外白资代付 承兑类公群:1.滴滴现金 2.滴滴承兑 3.三方承兑 4.POS承兑 5.实物承兑 6.礼品卡核销 7.平台币核销 招商引流类公群:1招车队/招料主. 2.跟车承兑窗口 3.彩票 4.六合彩/蛇货 5.招聊手/代打 6.司法救援 7.包养窗口 8.背债 9.多种类业务窗口 服务类公群:1.天眼查 2.票务口令 3.租社交账号 4.PS美工 5.接码注册 6.解封账号 7.代办业务/VPN 8.代办证件 9.外围/倮聊 10.ID贷款 11.其他服务 搭建类公群:…
退押招商: 天行组:3971 微信小额红包车(窗口)公群 天行组 : 3961-直盘招手机实物车小时达次日达(窗口)公群 H:563-天眼查人公群 H:693-卡商公群 H;691--领航车队公群 天行组:3947-招车窗口 K:126-海通一道精聊大区常规卡/码接回U公群 K:1028--老牌猎鹰调查员司法公群 K:595--8989看图王/p图软件/模拟器公群 天行组:3855-常规色料公群 天行组:3944-户外用品 天行: 3967 招募窗口车/料 K:1154--长昇全国拆机卡三网卡公群 K:657--高价收增值税专用发票粉公群 K:981--桔子科技/价格低服务好公群 K:562--听风拉码软件/拉码定制公群 K:116--好富贵卖四网厅卡/电销/虚拟/注册流量公群
暂停作业/留群:以下列表请勿作业,押金补齐后再正常作业,仅供示例 天行组: 3984 供押1万U-八方生活缴费热力电费信用卡代还公群(诚信金5000u) 天行组:4258 供押5000U/王权富贵(宾汉)保司法tg嫖娼一道放料公群(诚信金5000u) 天行组:2080 供押1940U-夏天知识付费招企业微信收款码车(窗口)公群 天行组 :531 供押2080U 暴富收香港/海外华人数据公群 天行组:3953 供押650U-谷歌打粉引流全行业/交友/兼职/股民/币粉等公群 H:5678-暂停作业供押500U-2026美加墨世界杯官方投注公群 ⚡️ K:557-暂停作业供押500U-余温一道无视料公群 H:276 供押15000U-冠军大混大区精聊一道无视料公群 K:875-暂停作业供押5000U-红牛一二道保时/进算放料收U公群(诚信金5000U) K:8988-暂停作业供押500U-字: 无双支付微信Q…
注意:不在此导航里面的群都是假公群,我们只担保游戏公群内的游戏能正常上下分,不担保群老板个人信誉,不担保代理、拉手、代收付等和群老板的其他交易或合作。 ———体育/哈希28娱乐公群——— H:444-供押100万U-恒信集团公群 ⚡️ H:5566-供押68万唐朝哈希游戏群【1.98赔率】 ⚡️
注意:我们只担保游戏公群内的游戏能正常上下分,不担保群老板个人信誉,不担保代理、拉手、代收付等和群老板的其他交易或合作。 ———综合盘/电子——— H:皇冠自营-皇冠娱乐综合盘 ⚡️ H:222-供押100万U-ETGame【综合盘】公群 ⚡️ H:801-供押3万U-无忧波克3d猎鱼达人公群 K:1136-供押3万U-船长波克3D捕鱼娱乐公群
注意:我们只担保游戏公群内的游戏能正常上下分,不担保群老板个人信誉,不担保代理、拉手、代收付等和群老板的其他交易或合作。 ———百家乐游戏公群——— 待更新
注意:我们只担保游戏公群内的游戏能正常上下分,不担保群老板个人信誉,不担保代理、拉手、代收付等和群老板的其他交易或合作。 ———红包游戏——— 待更新
注意:我们只担保游戏公群内的游戏能正常上下分,不担保群老板个人信誉,不担保代理、拉手、代收付等和群老板的其他交易或合作。 ———赛车飞艇弹珠类——— 待更新
Showing the 12 most recent of 42 posts we hold for @lSBSB. 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 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.
@bian · 184,7903 posts必安担保 @BADB 防伪认证
@badb · 44,3502 posts必安担保@BADB防伪认证
@ibadbbot · 21,3132 posts赌牌 @DuPai
@BADBBAGQ · 43,6691 post📣必安担保•网赚中心
@BAGQXE · 8,7631 post皇冠博彩频道 @bbbbc
@bbbbc · 15,9951 post必安担保公群业务注意事项
@bianzhuyishixiang · 7,5261 post皇冠担保-公告频道
@hgii · 20,6191 post皇冠-新开公群
@hgxx · 14,0721 post皇冠 假押反馈频道
@hyf789 · 12,9821 post必安担保转接区
@zbagx · 281 post
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
- 1
- 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
- 0
- vacant every time we have ever looked
@lSBSB named 1 handle 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 3 posts, 8 August 2026 – 10 August 2026 · confirmed gone 26 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
Domains linked from posts
One domain this channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.
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 28 October 2026 — this entry's latest reading, not the date you are reading this.
“皇冠公群频道 @hggq” (@lSBSB), 135,496 subscribers as measured 28 October 2026. Telegram Register, tgregister.com/channel/lSBSB.
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.