#来自粉丝投稿曝光 骗子用户名:@h3793 骗子飞机永久ID:726965175 骗子用户名:@zg682 骗子飞机永久ID: 8481533968 被骗经过:在供需群里发布招人信息,然后又让我去联系一个猪哥的,后面给他干了几天,不结工资,只接跑路,他们招人的目的就是为了骗押金,他不提让你上押,让你看到他们的收益,让你心痛,搞钱上押给他,来骗押金的,附上我还有别人的被骗记录 ——————————————————— ⚠️皇冠担保在此提醒大家⚠️ 任何业务往来/资金交易一定选择走担保,给自己一份保障,此类案例遍地全网,已经有诸多受害者用亲身经历告诫大家了!选择担保是为了确保每一笔合作、每一个环节都清晰透明、可追溯,让信任有据可依! ⚠️全网紧急防骗提醒⚠️ 现目前工作组只有 公群组;@hghh @hgkk @hggg @hgff @hgjj @hgpp 专群组;@hgaa @hgbb @hgcc @hgdd @hgee …

Channel
皇冠担保-曝光频道
@hguu
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
17,556subscribers
+7,875 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1003781622983 |
|---|---|
| Type | Channel |
| Usernames | @hgbaoguang @hguu |
| Description | 皇冠客服 @hgkf 供需频道 @hggx 官方大群 @hgdb 皇冠公群 @hggq 皇冠曝光 @hguu 皇冠海外 @hghw 皇冠专群组 @hgaa @hgbb @hgcc @hgdd @hgee @hgll 皇冠公群组 @hghh @hgkk @hgjj @hgff 皇冠天行组 @hgpp 皇冠海外组 @hggg @hgjj 皇冠娱乐 6i.com 娱乐机器人 @hgiiiiii_bot 投诉建议 @huidu 欲戴皇冠 必承其重 |
| Created | Between 1 February 2026 and 29 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 17 November 2026 |
| Measurements held | 52 |
| Confirmed unchanged | 1 time, most recently 17 November 2026 |
| On Telegram | t.me/hguu |
Topic
Gambling & betting — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 52% 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 |
|---|---|---|
| 17 Nov 2026, 11:18 | 17,556 | -234 |
| 14 Nov 2026, 04:18 | 17,790 | -442 |
| 11 Nov 2026, 06:40 | 18,232 | -757 |
| 9 Nov 2026, 15:36 | 18,989 | -633 |
| 8 Nov 2026, 09:56 | 19,622 | -574 |
| 7 Nov 2026, 06:07 | 20,196 | -616 |
| 6 Nov 2026, 08:09 | 20,812 | -1,209 |
| 5 Nov 2026, 05:30 | 22,021 | +8,720 |
| 4 Nov 2026, 02:01 | 13,301 | -112 |
| 3 Nov 2026, 04:59 | 13,413 | -1,608 |
| 2 Nov 2026, 02:57 | 15,021 | -6,233 |
| 1 Nov 2026, 04:09 | 21,254 | -1,199 |
| 31 Oct 2026, 05:20 | 22,453 | -59 |
| 30 Oct 2026, 05:57 | 22,512 | -102 |
| 29 Oct 2026, 03:05 | 22,614 | -62 |
| 28 Oct 2026, 03:59 | 22,676 | -48 |
| 27 Oct 2026, 06:20 | 22,724 | -55 |
| 26 Oct 2026, 05:15 | 22,779 | -75 |
| 25 Oct 2026, 03:41 | 22,854 | -146 |
| 24 Oct 2026, 02:27 | 23,000 | first reading |
Engagement
68 posts held, back to 29 July 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 86 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 9.66%
- avg views ÷ 17,556 subscribers
- Avg views / post
- 1,700
- 21 posts measured
- Reaction rate
- 0.2%
- reactions ÷ views · ER floor
- Posts in window
- 21
- of 68 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 20 of 21 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 17 November 2026 |
|---|---|
| Posts held | 68 (29 July 2026 – 17 November 2026) |
| Views total | 35,632 |
| Reactions total | 69 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Nov 2026, 18:30 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
- 624
- Videos
- 15
- Links
- 26
Lifetime counters from Telegram’s own channel header, read 17 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
- Video runtime
- 11m 11s
- Average length
- 1m 15s
Measured directly from 9 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
127 reactions across 40 posts, in 3 distinct kinds. The most used accounts for 89.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 113 | 89.0% | |
| 👍 | 12 | 9.45% | |
| 👎 | 2 | 1.57% |
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 46 of the 68 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 127 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 68 most recent posts we hold, published 29 July 2026 to 17 November 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
Telegram’s own ‘edited’ marker: 0 of 21 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
#来自粉丝投稿曝光 骗子用户名:@weige666888 骗子飞机永久ID:8401023409 骗子用户名:@sshj88 骗子飞机永久ID;7665401707 骗子用户名:@ce5783 骗子用户名:@hehe5780 骗子用户名:@pujing1588 被骗经过:在我这打了一笔线下邮寄,合作两年了,之前打也没有跑过,可能是胃口比较大,这次邮寄了一笔价值十三万的手机,货收到人就失联了 ——————————————————— ⚠️皇冠担保在此提醒大家⚠️ 任何业务往来/资金交易一定选择走担保,给自己一份保障,此类案例遍地全网,已经有诸多受害者用亲身经历告诫大家了!选择担保是为了确保每一笔合作、每一个环节都清晰透明、可追溯,让信任有据可依! ⚠️全网紧急防骗提醒⚠️ 现目前工作组只有 公群组;@hghh @hgkk @hggg @hgff @hgjj @hgpp 专群组;@hgaa @hgbb @hgcc @…
❤2
#来自粉丝投稿曝光 骗子用户名:@xiaoxiong404 骗子飞机永久ID:8225192938 注意此类骗术: 1.码接回u或者代收付订单码回 ,引导下载app,问鼎平台,利用app中植入木马文件,盗号! ——————————————————— ⚠️皇冠担保在此提醒大家⚠️ 任何业务往来/资金交易一定选择走担保,给自己一份保障,此类案例遍地全网,已经有诸多受害者用亲身经历告诫大家了!选择担保是为了确保每一笔合作、每一个环节都清晰透明、可追溯,让信任有据可依! ⚠️全网紧急防骗提醒⚠️ 现目前工作组只有 公群组;@hghh @hgkk @hggg @hgff @hgjj @hgpp 专群组;@hgaa @hgbb @hgcc @hgdd @hgee @hgll @hgpp 请大家仔细甄别,注意查看用户名+上押方式+888号码三重核实,我们客服人员不会主动私聊各位老板 唯一上押方式皇冠钱包 : @hgqb 上押内…
❤1
#来自粉丝投稿曝光 骗子用户名:@HJJT111 骗子飞机永久ID:6846237037 骗子用户名:@Tangguo1188 骗子飞机永久ID:7561521339 被骗经过:假冒盘口要求垫付,实际上就是为了骗通道的押金和垫付,避雷,所有的东西都是为了骗通道而做的,大家小心恒景 ——————————————————— ⚠️皇冠担保在此提醒大家⚠️ 任何业务往来/资金交易一定选择走担保,给自己一份保障,此类案例遍地全网,已经有诸多受害者用亲身经历告诫大家了!选择担保是为了确保每一笔合作、每一个环节都清晰透明、可追溯,让信任有据可依! ⚠️全网紧急防骗提醒⚠️ 现目前工作组只有 公群组;@hghh @hgkk @hggg @hgff @hgjj @hgpp 专群组;@hgaa @hgbb @hgcc @hgdd @hgee @hgll @hgpp 请大家仔细甄别,注意查看用户名+上押方式+888号码三重核实,我们…
❤3
骗子用户名:@XHDShy 骗子飞机永久ID:8458466702 骗子用户名:@hgkko 骗子飞机永久ID:7475747454 被骗经过:抖音刷礼物日赚5000都是假的 拉我进公群,转70u开始做业 没注意看客服真假。本以为70U没必要骗 后面又说要150押金费 我看公群规则里面有这条就转了,我以为可以开始做业了。 又拉一个专群说皇冠钱包被攻击了还需要交250U皇冠收的担保费我就去问客服验群 假群。希望大家注意 ——————————————————— ⚠️全网紧急防骗提醒⚠️ 近期大量用户反馈,有人利用相似用户名长期假冒皇冠担保工作人员实施网络诈骗,特此统一提醒全体老板,请各位老板扩散本条警示,提醒身边生意伙伴、同行避开骗局,避免财产受损。 ⚠️全网紧急防骗提醒⚠️ 现目前工作组只有 公群组;@hghh @hgkk @hggg @hgff @hgpp @hgjj 专群组;@hgaa @hgbb @hgcc @hgd…
❤3
#来自粉丝投稿曝光 骗子用户名: @vlpzq 骗子飞机永久ID:8962125886 骗子钱包:@hgqb_blbot 被骗经过:这个客服,当时是他们给我拉的专群,然后上押要求我用皇冠钱包上押,我充值后想提现就一直提现不了,我刚开始上押时候是1200U,后续因为各种原因说我提现失误流水不够的借口,诱导我反复充值,总计2900U ,骗子客服 @vlpzq 骗子假钱包 @hgqb_blbot ,上押流程全部跟你们的一样,因为我当时不知道皇冠没有vip组。后面因为没钱再充值了,才去问了 @hgkf ,才知道是假的。希望能曝光一下,不要让更多的人上当受骗了,骗子的担保机器人做的实在太像了,当时他们给我发客服用户名的时候是以超链的方式发的,我被骗我认了,希望以后不要有再多的兄弟被骗了 ——————————————————— ⚠️全网紧急防骗提醒⚠️ 近期大量用户反馈,有人利用相似用户名长期假冒皇冠担保工作人员实施网络诈骗,特…
❤6👍3
#来自粉丝投稿曝光 骗子用户名:@hgpay0040 骗子飞机永久ID:8212397627 ⚠️全网紧急防骗提醒⚠️ 近期大量用户反馈,有人利用相似用户名长期假冒皇冠担保工作人员实施网络诈骗,特此统一提醒全体老板,请各位老板扩散本条警示,提醒身边生意伙伴、同行避开骗局,避免财产受损。 ⚠️全网紧急防骗提醒⚠️ 现目前工作组只有 公群组;@hghh @hgkk @hggg @hgff @hgpp @hgjj 专群组;@hgaa @hgbb @hgcc @hgdd @hgee @hgll 请大家仔细甄别,注意查看用户名+上押地址+888号码三重核实,我们客服人员不会主动私聊各位老板 注意:皇冠钱包客服唯一用户名 @hgpay ——————————————————— ⚡️投稿曝光澄清联系⚡️:@HGQQ
❤4
#来自粉丝投稿曝光 骗子用户名: @TG333A3 骗子飞机永久ID:7395834852 骗子用户名: @AJ773377 骗子飞机永久ID:6356884640 被骗经过:跟他们认识了段时间,信任他们,给他们放料,空放打贝宝有八千多U不回款,一男一女。让他们回款,男的说回款给女的了,让女的回款过来。女的收钱了一直联系不上,实则商量好了跑路。他们是同一个工作室的,都互相认识,互相沟通好了跑路。 ——————————————————— ⚠️皇冠担保在此提醒大家⚠️ 任何业务往来/资金交易一定选择走担保,给自己一份保障,此类案例遍地全网,已经有诸多受害者用亲身经历告诫大家了!选择担保是为了确保每一笔合作、每一个环节都清晰透明、可追溯,让信任有据可依! ⚠️全网紧急防骗提醒⚠️ 现目前工作组只有 公群组;@hghh @hgkk @hggg @hgff @hgjj @hgpp 专群组;@hgaa @hgbb @hgcc …
❤8👍1
#来自粉丝投稿曝光 骗子用户名:@hghhh 骗子永久ID:7810743061 ⚠️全网紧急防骗提醒⚠️ 近期大量用户反馈,有人利用相似用户名长期假冒皇冠担保工作人员实施网络诈骗,特此统一提醒全体老板,请各位老板扩散本条警示,提醒身边生意伙伴、同行避开骗局,避免财产受损。 ⚠️全网紧急防骗提醒⚠️ 现目前工作组只有 公群组;@hghh @hgkk @hggg @hgff @hgpp @hgjj 专群组;@hgaa @hgbb @hgcc @hgdd @hgee @hgll 请大家仔细甄别,注意查看用户名+上押地址+888号码三重核实,我们客服人员不会主动私聊各位老板 ——————————————————— ⚡️投稿曝光澄清联系⚡️:@HGQQ
👍1
#来自粉丝投稿曝光 骗子用户名:@Idd266 骗子飞机永久ID:8336031063 骗子用户名:@Idd268 骗子飞机永久ID:5497115835 骗子用户名:@Idd267 骗子飞机永久ID:7349975446 骗子用户名:@Idd269 骗子飞机永久ID:7349975446 骗子用户名:@Idd265 骗子飞机永久ID:6447448286 骗子用户名:@Idd268 骗子飞机永久ID:8583855167 被骗经过:骗子把真群链接发给了我 然后群是真的 我报备的一笔36万的香港料快杀 他贴给我了 然后我说公群报备 公群我看见报备了也是我的地址 然后我才进的 进去后就退群完了 骗子的ID和真群里面人的ID几乎一模一样根本看不出来 ——————————————————— ⚠️皇冠担保在此提醒大家⚠️ 任何业务往来/资金交易一定选择走担保,给自己一份保障,此类案例遍地全网,已经有诸多受害者用亲身经历告诫…
❤3👍1
#来自粉丝投稿曝光 骗子用户名:@aaa00877 骗子飞机永久ID:6224039469 骗子用户名:@H80066888 骗子飞机永久ID:5828204647 被骗经过:曝光两个跑路狗,一开始押金打满一直让我空放,说几百U这么点信任都没有,后来给他们打超押170U也给跑了,哈哈哈,属实被笑到了 ——————————————————— ⚠️皇冠担保在此提醒大家⚠️ 任何业务往来/资金交易一定选择走担保,给自己一份保障,此类案例遍地全网,已经有诸多受害者用亲身经历告诫大家了!选择担保是为了确保每一笔合作、每一个环节都清晰透明、可追溯,让信任有据可依! ⚠️全网紧急防骗提醒⚠️ 现目前工作组只有 公群组;@hghh @hgkk @hggg @hgff @hgjj @hgpp 专群组;@hgaa @hgbb @hgcc @hgdd @hgee @hgll @hgpp 请大家仔细甄别,注意查看用户名+上押方式+888…
❤3
#来自粉丝投稿曝光 骗子用户名:@HJJT111 骗子飞机永久ID:6846237037 骗子用户名:@Tangguo1188 骗子飞机永久ID:7561521339 被骗经过:假冒盘口要求垫付,实际上就是为了骗通道的押金和垫付,避雷,所有的东西都是为了骗通道而做的,大家小心恒景 ——————————————————— ⚠️皇冠担保在此提醒大家⚠️ 任何业务往来/资金交易一定选择走担保,给自己一份保障,此类案例遍地全网,已经有诸多受害者用亲身经历告诫大家了!选择担保是为了确保每一笔合作、每一个环节都清晰透明、可追溯,让信任有据可依! ⚠️全网紧急防骗提醒⚠️ 现目前工作组只有 公群组;@hghh @hgkk @hggg @hgff @hgjj @hgpp 专群组;@hgaa @hgbb @hgcc @hgdd @hgee @hgll @hgpp 请大家仔细甄别,注意查看用户名+上押方式+888号码三重核实,我们客…
❤2
Showing the 12 most recent of 68 posts we hold for @hguu. 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 11 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.
@goood · 5,8798 posts比心大食堂
@fanguo · 32,6452 posts皇冠公群流程
@hggqlc · 4,1102 posts香奈儿滴滴现金全摑招车🚘
@chanle607 · 4841 post皇冠担保中转频道
@hgdbzzpd · 471 post皇冠滴滴现金助手流程
@hgddzhushou · 2,4921 post皇家学院-智库/防骗指南
@hggsmj · 3,7481 post皇冠担保-公告频道
@hgii · 12,7371 post皇冠担保-官方频道
@hgvv · 6,5621 post皇冠专群流程
@hgzqlc · 4,2761 post小白防骗指南 @xiaobai
@xiaobai · 1,6701 post
Names
Channels on the register whose handles appear in this channel's posts.
@hgvv · 6,5626 posts皇冠项目交流群 @hgdb
@awpgqun · 89,9512 posts皇冠海外交流群 频道 @hghw
@haiwai666 · 5,4802 posts皇冠发虎粮
@LHFHL8 · 4942 posts鉴劳中心中转群
@lwzj · 2,6932 posts比心大食堂 @miss
@miss · 16,9592 posts皇冠博彩频道 @bbbbc
@bbbbc · 16,9151 post小米机器人定制开发
@crownzhuanqurguani_bot · 11 postCVV 暴利技术教学 通道料源 收徒
@id266 · 6,6841 post学习CVV 关于cvv这行的了解
@iililiiiliii · 3,8621 postjhs49
@jhs49 · 41 post海外曝光
@laicai726 · 11 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
- 7
- 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
- 6
- vacant every time we have ever looked
@hguu named 7 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.
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, 18 October 2026 – 20 October 2026 · confirmed gone 1 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 4 posts, 19 August 2026 – 25 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 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 17 November 2026 — this entry's latest reading, not the date you are reading this.
“皇冠担保-曝光频道” (@hguu), 17,556 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/hguu.
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.