#骗子曝光 ⚠骗子昵称:SGWIN商务 SGWIN SGWIN官方咨询中心 🤡骗子用户名:@SGWINSW @sgwin123 @sgwin 数字id:7335489563 5649491148 2144731765 被骗金额:4800u 被骗说明:sgwin假双赢彩票包网商是骗开版费的 我于2026年11月13日找@sgwin开版包网,对方给的流程如下,确定要开版的资料信息(网站名称/网站域名/增值服务/合作方式) ,然后我提交了,名称,域名我自己购买的,然后增值服务经过他们的介绍,加了 200U/年 3个坐席客服,加了500U/年的聊天室服务费,加了 苹果超级签1U/台 300U。U打过去后就被拉黑聊天记录全删了,一共被骗4800U。 要开双赢彩票包网的注意以下骗子信息,发出来是防止后来人被骗。 频道: https://t.me/sgwin1 网址: https://sgwin.com/ https://sg-win.co…

Channel
灰度曝光頻道✳️
@hddb_bg
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry
13,462subscribers
-24,453 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1001744852755 |
|---|---|
| Type | Channel |
| Username | @hddb_bg |
| Description | #骗子曝光 灰度官网: www.huidu.io 交流社群: @huidu_shequ 资源社群: @hddbdaqun 灰度公群: @hddbgongqun 供需信息: @hddbgongxu 公告频道: @hddbgg 曝光频道: @hddb_bg 担保规则: @hddb_guize 安全防范: @hddbaq 灰度Bot: @huidubot 担保客服: @huiducn 对接联系: @huiduTom8 |
| 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 | 17 November 2026 |
| Measurements held | 64 |
| Confirmed unchanged | 1 time, most recently 17 November 2026 |
| On Telegram | t.me/hddb_bg |
Topic
Marketing & affiliate — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 48% 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, 15:49 | 13,462 | -63 |
| 14 Nov 2026, 09:46 | 13,525 | +32 |
| 11 Nov 2026, 12:56 | 13,493 | +58 |
| 9 Nov 2026, 16:55 | 13,435 | -55 |
| 8 Nov 2026, 10:06 | 13,490 | -26 |
| 7 Nov 2026, 01:39 | 13,516 | -9 |
| 5 Nov 2026, 23:58 | 13,525 | +9 |
| 5 Nov 2026, 03:06 | 13,516 | -2 |
| 4 Nov 2026, 05:20 | 13,518 | +10 |
| 3 Nov 2026, 04:28 | 13,508 | +11 |
| 2 Nov 2026, 05:39 | 13,497 | +12 |
| 1 Nov 2026, 07:36 | 13,485 | -5 |
| 31 Oct 2026, 05:37 | 13,490 | -15 |
| 30 Oct 2026, 08:11 | 13,505 | -11 |
| 29 Oct 2026, 05:01 | 13,516 | +33 |
| 28 Oct 2026, 00:57 | 13,483 | -1 |
| 27 Oct 2026, 02:18 | 13,484 | +13 |
| 26 Oct 2026, 00:36 | 13,471 | +1 |
| 25 Oct 2026, 00:27 | 13,470 | +6 |
| 22 Oct 2026, 22:47 | 13,464 | first reading |
Engagement
65 posts held, back to 3 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 103 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 7.09%
- avg views ÷ 13,462 subscribers
- Avg views / post
- 954
- 15 posts measured
- Reaction rate
- 0.18%
- reactions ÷ views · ER floor
- Posts in window
- 15
- of 65 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 9 of 15 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 16 November 2026 |
|---|---|
| Posts held | 65 (3 August 2026 – 16 November 2026) |
| Views total | 14,312 |
| Reactions total | 16 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 18 Nov 2026, 09:55 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,860
- Videos
- ≈8
- Links
- ≈928
Lifetime counters from Telegram’s own channel header, read 18 November 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
63 reactions across 25 posts, in 10 distinct kinds. The most used accounts for 57.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 36 | 57.1% | |
| 👍 | 14 | 22.2% | |
| 🎉 | 4 | 6.35% | |
| 😱 | 2 | 3.17% | |
| 🤣 | 2 | 3.17% | |
| 👎 | 1 | 1.59% | |
| 👏 | 1 | 1.59% | |
| 🔥 | 1 | 1.59% | |
| 🤮 | 1 | 1.59% | |
| 🥰 | 1 | 1.59% |
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 33 of the 65 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 63 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 65 most recent posts we hold, published 3 August 2026 to 16 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 15 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).
#骗子曝光 ⚠骗子昵称:杰森 🤡骗子用户名:@jason126888 数字id:8293089005 被骗金额:50u 被骗说明:之前跟他合作过一次,说好是登录账号后付款,11月4日他介绍同事来我这购买了2个领英ck销售会员账号,结果他同事迟迟没有付款,我找到他,他说代替付款,拉了个群,财务也在里面。结果过去一个礼拜,始终不付款,消息已读不回。大家避雷 ✅ HUIDU.IO 灰度安全提醒 🆔 灰度官方公群查询:@huidubot 🚀 灰度官方担保客服: @huiducn 🤝 灰度担保公群频道:@hddbgongqun 🚨 诈骗 / 跑路 线索举报:@HDMerly ⚠ 未报备交易、私下交易,灰度官方不予认可。 ⚠ 付款前请核实群组、账号及交易身份,谨防假群假客服
#骗子曝光 ⚠骗子昵称:样子 🤡骗子用户名:@haipay5521 @shanquan66 @zhaoxi111 @wumeizi3 数字id:2060468420 8041406642 7325501270 7622698902 被骗金额 :100万 巴基斯坦 被骗说明:代付不行,一直让我们充值,我要下发也不行,,我通知停,等等代付出去在开代收,就说我侮辱和质疑他, 直接关闭我们后台登入,商户群也退出。 ✅ HUIDU.IO 灰度安全提醒 🆔 灰度官方公群查询:@huidubot 🚀 灰度官方担保客服: @huiducn 🤝 灰度担保公群频道:@hddbgongqun 🚨 诈骗 / 跑路 线索举报:@HDMerly ⚠ 未报备交易、私下交易,灰度官方不予认可。 ⚠ 付款前请核实群组、账号及交易身份,谨防假群假客服
❤1
#骗子曝光 ⚠骗子昵称:河豚工作室(支持担保交易) 🤡骗子用户名:@HETUN3 数字id:7798591022 被骗金额:1500.1U 被骗说明:群机器人瘫痪,我想找个机器人定制,此人私聊我,我们交流后他说可以建群试用,我们打了500U他建了群,然后把我们需要的机器人制作出来后给我们试用了一会,使用后觉得还可以,按照对方要求继续打了1000U,然后他发了链接让我们注册VIP链接后台(0.1U),我们花了1500U他居然0.1U都不舍得垫付(理由是我们需要用我们的钱包来当后台登录信息),我们创建新钱包进行付款,此人发现我们使用新钱包立马删除信息拉黑我们三个号跑路 ✅ HUIDU.IO 灰度安全提醒 🆔 灰度官方公群查询:@huidubot 🚀 灰度官方担保客服: @huiducn 🤝 灰度担保公群频道:@hddbgongqun 🚨 诈骗 / 跑路 线索举报:@HDMerly ⚠ 未报备交易、私下交易,灰度官方不予认可。 ⚠ …
#骗子曝光 ⚠骗子昵称:样子 🤡骗子用户名:@wer232121 数字id:7306256496 被骗金额:575U 被骗说明: 10月20日咨询缅甸打粉 11月8日才开始打 前面一直让他打预付就不打 说10个结 到了10个就一直托 消息一天才回一次 后面又说上报财务花了一天一夜也没个消息 台子曝光: 代理线:mmr5dx09 原链接:https://www.mmr555.com/?affiliateCode=mmr5dx09 短连接:https://shorturl.at/dQcUv ✅ HUIDU.IO 灰度安全提醒 🆔 灰度官方公群查询:@huidubot 🚀 灰度官方担保客服: @huiducn 🤝 灰度担保公群频道:@hddbgongqun 🚨 诈骗 / 跑路 线索举报:@HDMerly ⚠ 未报备交易、私下交易,灰度官方不予认可。 ⚠ 付款前请核实群组、账号及交易身份,谨防假群假客服
#骗子曝光 ⚠骗子昵称:Di Rios Sai Mini 🤡骗子用户名:@DILus0 @Saiminimall_245 数字id:7559145534 6209828540 被骗说明:该用户为骗子,以甲方名义,先是询问地址,然后查地址最近大金额P图假打款,还能录屏,搞得非常真,各位遇到这两个人多留个心眼 ✅ HUIDU.IO 灰度安全提醒 🆔 灰度官方公群查询:@huidubot 🚀 灰度官方担保客服: @huiducn 🤝 灰度担保公群频道:@hddbgongqun 🚨 诈骗 / 跑路 线索举报:@HDMerly ⚠ 未报备交易、私下交易,灰度官方不予认可。 ⚠ 付款前请核实群组、账号及交易身份,谨防假群假客服
👍2😱2
#骗子曝光 ⚠骗子昵称:夜雨科技 夜雨科技-小王🎊❤️🔥 🐮 夜雨科技-ACE 夜雨科技-小北 FB/TK/GG广告户代理 夜雨科技-萝拉 🤡骗子用户名:@YeYuV10 @Wk202518 @yeyuv8 @YeYuv12 被骗说明:1. 11 月 10 日 17:14,我方在和夜雨科技的正版合作群内,正式提交退款申请; 2. 17:24,我方在本正版群发送收款地址,夜雨科技小王核对账单,确认退款金额 521U,地址、余额在本群双方确认完成; 3. 后续出现骗子克隆了一模一样名字的高仿群,夜雨科技工作人员没有做身份、群聊二次核验,没有回到正版群核对地址,错误向骗子提供的地址转出 521USDT; 4. 我方在正版群询问退款进度,夜雨科技告知钱已经转出,打款对象是骗子; 5. 夜雨科技的处理方案:认定是克隆群风险不可控,以 “已经退款一次,不能重复退款” 为由,拒绝向真实付款的客户履约退款,将全部损失归责我方。自己没有核实清楚…
👍1
#骗子曝光 ⚠骗子昵称:吕品源 洋哥(海外数据)Asiv 泡面 Lucky 加多宝 阿Q 黄毛. 小乔 🤡骗子用户名:@bengfu @lucky12_3 @duobao369 @age678788 @wenwencds @xq16886 数字id:6842288598 6918887987 7761922560 6506813482 5814310340 7813672821 被骗说明:曝光跑路甲,不知道在哪问的要跑dsp,找到我来,跑之前也知道他们有过先列欠款跑路,想着小额跑无所谓,在10月5号对接群里让暂停,到10月5号不断性的催促补齐欠款,没人回复说提交财务,什么款提交了一个月下不来的,2000多不算多只是发出来让同行看看这种恶臭的甲方,心里ps:没钱开鸡毛台子,这钱不要了给你们几个买棺材不够买的话发地址给我 我再掏点给你 我方没有后台,后台截图为甲方自己截出,截图一共77个充值玩家数据,其中二冲三冲以上玩家一共32个…
#骗子曝光 ⚠骗子昵称:黑虎 / 珂少集团-虎 / 东皇太一 🤡骗子用户名:@hulaobanll @L5l5l5577 @tiandi444 数字id:7511428675 8316267030 8414270737 骗子地址:TH7CsKPBXfGbVWGKMsMbMZhwDuUHWdJopy 被骗金额:300U 被骗说明:10月15日咨询订单购BM*2个号,需求得到(珂少集团-虎)答复确认 被骗子关键词:whatsapp api 公司曾用名:创世出海 购买BM2000消息限额户*2并且支付打款。 10月19日售后(东皇太一)称技术联系不上/没上班,销售(黑虎)跳出来叫加钱500u开10000消息限额户。 被拒绝加钱后就不给户了。 骗了300换了个马甲过来要加钱500u继续骗。 10月20日骗不到钱联系售后群内信息不回,开始拖/不给户/不退款 理由就是老板出差,在忙,技术联系不上。 10月26日友好客气沟通了十天,不退钱…
#骗子曝光 ⚠骗子昵称:Asiv 🤡骗子用户名:@Zxiddr 数字id:6296859515 骗子地址:TNEPjWqmBmz2DxTqE9vuzKcGPHVWsGitv3 被骗说明:跟我说孟加拉打VB渠道w45+效果,最近打的效果都不错,最后0进粉,三天后查出原因说是料子的问题,只退我100U,需要我承担通道费用,后面还找一堆借口,又说自己说的不是孟加拉的效果,是其他国家的效果这伙人的诈骗手法相当隐蔽,而且很有套路。 首先,他们会主动联系从事广告投放的合作伙伴,假装要合作投放广告。 接着,他们会以“确保合作信誉和资金实力”为借口,要求查看广告投手的USDT钱包余额。 实际上,他们的目的就是摸清你钱包里有多少钱,确认你是否有足够的资金,值不值得他们下手诈骗。 然后,他们会利用USDT转账金额的小数点来设局。 比如,他们声称要转给你2475 USDT,但实际只转了2.475 USDT,也就是只有2.475个U,根本不是2475个…
👍2🤣1
#骗子曝光 ⚠骗子昵称:洋哥(海外数据) 吕品源 🤡骗子用户名:@lvpin888 @yangge45678 数字id:8730563158 6811432126 骗子地址:TT8HzpBFwjQCCbWFAhfTjTVLVN5jSKsfCC 被骗金额:268U 被骗说明:跟我说孟加拉打VB渠道w45+效果,最近打的效果都不错,最后0进粉,三天后查出原因说是料子的问题,只退我100U,需要我承担通道费用,后面还找一堆借口,又说自己说的不是孟加拉的效果,是其他国家的效果 ✅ HUIDU.IO 灰度安全提醒 🆔 灰度官方公群查询:@huidubot 🚀 灰度官方担保客服: @huiducn 🤝 灰度担保公群频道:@hddbgongqun 🚨 诈骗 / 跑路 线索举报:@HDMerly ⚠ 未报备交易、私下交易,灰度官方不予认可。 ⚠ 付款前请核实群组、账号及交易身份,谨防假群假客服
👍1🤣1🤮1
#骗子曝光 ⚠骗子昵称:LumPay_李易安 LumPay鱼鱼 LumPay_熙熙 LumPay_嘟嘟 LumPay_琪琪 LumPay_开心超人 LumPay_岁岁 LumPay西门 🤡骗子用户名:@LumPay_xixi @ziyou_dudu @Lumpay_3388 @LumPay_yuyu @lumpay_qiqi @kaixinCR @s5s8888 @Lumpay_XM 数字id:1894190698 8528845952 6777423686 1837508842 8016242044 6871692608 6271590349 7605633237 骗子地址:TRLSf28C3jRyMnP2gBcAoGat7qd236PmDP 被骗金额:50000卢比 被骗说明:印度游戏通道给我打卢比,出现滞留不处理,一开始说国庆放假轮休晚点处理,后面国庆节结束主管说在外面旅游,说回公司处理,后面说什么utr对不上,印…
❤3
Showing the 12 most recent of 65 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.
Posts recorded as deleted after publishing
We recorded 1 post on @hddb_bg as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
- First seen missing
- 13 August 2026
- Most recent seen missing
- 13 August 2026
- Median time before seen missing
- 19 hours
- Seen missing in the last 30 days
- 0
Mentions
Named by 6 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.
@hddbgongqun · 97,50964 posts欧易验群管家 @oyqg
@oyqg · 142,8271 post0.1Trx转u(推广 借用用户名)
@Saiminimall_245 · 11 postSGWIN双赢官方加盟公开群
@sgwin1 · 6,0951 post星河云控|WS云控|WS群发|WS拉群
@xingheyunkonga · 15,5631 post星河云控|群发拉群|WS云控
@xingheyunkongd · 7,5971 post刑天出海|TG老频道|频道代运营|TG广告|过审频道 🥇
@XTianchuhai · 1881 post欧易公群频道@XYXY
@xyxy · 116,6721 postWS云控|星河云控|TG云控
@yunkongws22 · 3,3571 post飞机代发 抖音引流 飞机群发 广告代发
@ZCNF66 · 8,7671 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
- 24
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 24
- vacant every time we have ever looked
@hddb_bg named 24 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 4 posts, 5 November 2026 – 11 November 2026
named in 2 posts, 19 August 2026 – 20 August 2026
named in 2 posts, 19 August 2026 – 20 August 2026
named in 2 posts, 19 August 2026 – 20 August 2026
named in 2 posts, 19 August 2026 – 20 August 2026
named in 2 posts, 19 August 2026 – 20 August 2026
named in 2 posts, 19 August 2026 – 20 August 2026
named in 2 posts, 19 August 2026 – 20 August 2026
named in 2 posts, 19 August 2026 – 20 August 2026
named in 2 posts, 19 August 2026 – 20 August 2026
named in 2 posts, 19 August 2026 – 20 August 2026
named in 2 posts, 8 August 2026 – 9 August 2026
named in 2 posts, 8 August 2026 – 9 August 2026
named in 2 posts, 8 August 2026 – 9 August 2026
named in 2 posts, 8 August 2026 – 9 August 2026
named in 2 posts, 8 August 2026 – 9 August 2026
named in 2 posts, 8 August 2026 – 9 August 2026
named in 2 posts, 8 August 2026 – 9 August 2026
named in 1 post, 27 August 2026 – 27 August 2026
named in 1 post, 13 August 2026 – 13 August 2026
named in 1 post, 11 August 2026 – 11 August 2026
named in 1 post, 11 August 2026 – 11 August 2026
named in 1 post, 8 August 2026 – 8 August 2026
named in 1 post, 8 August 2026 – 8 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.
“灰度曝光頻道✳️” (@hddb_bg), 13,462 subscribers as measured 17 November 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.