📣新增騙子通報🆘 ⚠️原因:【買賣詐騙】 名稱:熊猫官方账号 用戶名: @xbooe 被騙說明: 在群里看见他发消息说收号,先给号他测试,测试没问题也不付款 受理編號 R20260920-0001 檢舉人:匿名 ⚖️ 如果你认为此条指认有误,请私信本机器人输入 /appeal S000030 提出申诉,受理期间本条将先暂时隐藏。 本則由社群檢舉、經人工審核後發布,僅供風險參考,請自行查證。 遇到騙子曝光 @haihuabaoguangbot

Channel
海华出海-全網騙子曝光頻道
@haihuabaoguan
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
33,056subscribers
+12,090 since we began measuring on 15 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1003214639081 |
|---|---|
| Type | Channel |
| Username | @haihuabaoguan |
| Description | 海華曝光僅限處理騙子信息 免費群騙子多謹防上當受騙 海華公告 @haihua_gg 海華一群 @hhchtrx 海華二群 @haihua_danbao 海華三群 @hhtrxxxx 海華供需 @haihuagongx 海華曝光 @haihuabaoguan 海華兌換 @haihuaTRXbo 海華新聞 @xinwen_News 客服華妹 @huameiok 客服華哥 @huageok 交流 資源 會員 廣告 供需 |
| Created | Between 1 October 2025 and 31 December 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 15 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/haihuabaoguan |
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 9 September 2026 and assigned it the closest of 31 fixed categories, at 90% 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 |
|---|---|---|
| 18 Sept 2026, 20:55 | 33,056 | -293 |
| 16 Sept 2026, 15:56 | 33,349 | -517 |
| 14 Sept 2026, 17:18 | 33,866 | -294 |
| 13 Sept 2026, 00:39 | 34,160 | -568 |
| 10 Sept 2026, 22:40 | 34,728 | -602 |
| 8 Sept 2026, 02:00 | 35,330 | -460 |
| 4 Sept 2026, 23:18 | 35,790 | -149 |
| 3 Sept 2026, 09:02 | 35,939 | +4,690 |
| 2 Sept 2026, 04:44 | 31,249 | -117 |
| 1 Sept 2026, 06:27 | 31,366 | +4,506 |
| 31 Aug 2026, 04:23 | 26,860 | -304 |
| 30 Aug 2026, 07:04 | 27,164 | -421 |
| 29 Aug 2026, 08:43 | 27,585 | -214 |
| 28 Aug 2026, 09:05 | 27,799 | -74 |
| 27 Aug 2026, 07:53 | 27,873 | -200 |
| 26 Aug 2026, 07:43 | 28,073 | -120 |
| 25 Aug 2026, 09:55 | 28,193 | +9,865 |
| 24 Aug 2026, 12:18 | 18,328 | -353 |
| 22 Aug 2026, 19:15 | 18,681 | -210 |
| 21 Aug 2026, 10:26 | 18,891 | first reading |
Engagement
23 posts held, back to 7 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 · 30 days
- 6.25%
- avg views ÷ 33,056 subscribers
- Avg views / post
- 2,070
- 17 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 17
- of 23 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 20 September 2026 |
|---|---|
| Posts held | 23 (7 August 2026 – 20 September 2026) |
| Views total | 35,150 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 22 Sept 2026, 06:01 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
- 544
- Videos
- 1
- Links
- 18
Lifetime counters from Telegram’s own channel header, read 22 September 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.
Recent posts
📣新增騙子通報🆘 ⚠️原因:【其他】 名稱:小猴紫 用戶名: @xhz8887 被騙金額:300 CNY 被騙說明: 偏粉!!!日本交友粉单价15,打了21个该结账的时候拉黑跑路 受理編號 R20260913-0001 檢舉人:@FDC8888886 ⚖️ 如果你认为此条指认有误,请私信本机器人输入 /appeal S000028 提出申诉,受理期间本条将先暂时隐藏。 本則由社群檢舉、經人工審核後發布,僅供風險參考,請自行查證。 遇到騙子曝光 @haihuabaoguangbot
📣新增騙子通報🆘 ⚠️原因:【買賣詐騙】 名稱:WhatsApp蓝标🚀 用戶名: @Xinxie1 騙子頻道: TEXtxRrrX7cRbtkyZj9xsQdXn8og9SpJSe 被騙說明: 对方出售蓝标号码的.付完款不给验证码. 然后又说打错地址 反正就是不发货 騙子地址:TNqdx91Ax9Fj2DkaWjQHZ8HP1DDm6C5GJT 受理編號 R20260912-0001 檢舉人:匿名 ⚖️ 如果你认为此条指认有误,请私信本机器人输入 /appeal S000027 提出申诉,受理期间本条将先暂时隐藏。 本則由社群檢舉、經人工審核後發布,僅供風險參考,請自行查證。 遇到騙子曝光 @haihuabaoguangbot
📣新增騙子通報🆘 ⚠️原因:【買賣詐騙】 名稱:花生 用戶名: @kkl66896 被騙金額:468 USDT 被騙說明: 给他打台湾色粉粉,不结账说老板被按了,最后核实款已经结给他了,不结给我,总说过几天过几天,最后跑路了,双清屏幕! 受理編號 R20260910-0001 檢舉人:@gwf668 ⚖️ 如果你认为此条指认有误,请私信本机器人输入 /appeal S000026 提出申诉,受理期间本条将先暂时隐藏。 本則由社群檢舉、經人工審核後發布,僅供風險參考,請自行查證。 遇到騙子曝光 @haihuabaoguangbot
📣新增騙子通報🆘 ⚠️原因:【盜帳號】 名稱:坤哥TG飞机号 用戶名: @cvipv 騙子頻道: https://shop.yunyfk.com/shop/5ICZC6R0 被騙金額:10,000 USD 被騙說明: 这个是职业骗子了,找他买账号会给你发网站,网站转账就是授权地址的,属于盗U的,很多群都曝光过,还是有人上当,擅长用一堆协议号在各种群发他的卖号广告,低价引流,其实就是骗子 騙子地址:@hkmam8 @aitongyiqianwen @desensitization @king_martin_luther @marketsushibot @rollspizzaburger 受理編號 R20260906-0001 檢舉人:匿名 ⚖️ 如果你认为此条指认有误,请私信本机器人输入 /appeal S000025 提出申诉,受理期间本条将先暂时隐藏。 本則由社群檢舉、經人工審核後發布,僅供風險參考,請自行查證。 遇到騙…
📣新增騙子通報🆘 ⚠️原因:【買賣詐騙】 名稱:🌐战神全球TT.FB引流 用戶名: @Zhanshen8881 騙子頻道: https://t.me/zhanshen88881 被騙金額:787 USD 被騙說明: 合作有段时间了,前面结算都正常后面这次一直拖着不结算,各种理由我都相信他,后面直接消息不回突然删除聊天记录, 騙子地址:TTwmsPA9y4wZZ48TTGQpECCkPJ9BRJXutp 受理編號 R20260831-0001 檢舉人:@MyCar8888 ⚖️ 如果你认为此条指认有误,请私信本机器人输入 /appeal S000024 提出申诉,受理期间本条将先暂时隐藏。 本則由社群檢舉、經人工審核後發布,僅供風險參考,請自行查證。 遇到騙子曝光 @haihuabaoguangbot
📣新增騙子通報🆘 ⚠️原因:【交友詐騙】 名稱:黑马 用戶名: @yy258369yt 被騙金額:170 USD 被騙說明: 之前说公司检查不能结款拖到8月29号现在在线也不回消息 騙子地址:TRiNqskxBXWcNF8Mn97ntZzPUQzUG1ftyB 受理編號 R20260829-0002 檢舉人:匿名 ⚖️ 如果你认为此条指认有误,请私信本机器人输入 /appeal S000023 提出申诉,受理期间本条将先暂时隐藏。 本則由社群檢舉、經人工審核後發布,僅供風險參考,請自行查證。 遇到騙子曝光 @haihuabaoguangbot
📣新增騙子通報🆘 ⚠️原因:【其他】 名稱:梦西游 逍遥生 用戶名: @RH_RHBST 被騙說明: 户商找他们拿户,余额剩20000不退 騙子地址:TNo3JKve9TW7qEYRTA9BzoZKgxsXgCzRjM 受理編號 R20260829-0001 檢舉人:@yaoyao88 ⚖️ 如果你认为此条指认有误,请私信本机器人输入 /appeal S000022 提出申诉,受理期间本条将先暂时隐藏。 本則由社群檢舉、經人工審核後發布,僅供風險參考,請自行查證。 遇到騙子曝光 @haihuabaoguangbot
📣新增騙子通報🆘 ⚠️原因:【買賣詐騙】 騙子用戶名 @yy102599 ID 7880655531 @Svip6668881 ID8962679786 @wan8610 ID 6961439499 PS:這個大哥也是真的慘,梅開三度,連續被騙三次,本來不想笑的,對不起實在沒忍住😂
📣新增騙子通報🆘 ⚠️原因:【投資詐騙】 名稱:绾绾🌸TG/WS/IM/源头机房 用戶名: @wan8610 被騙金額:258 USDT 被騙說明: WS投放测试数量5000条 诈骗金额258 受理編號 R20260828-0003 檢舉人:匿名 ⚖️ 如果你认为此条指认有误,请私信本机器人输入 /appeal S000021 提出申诉,受理期间本条将先暂时隐藏。 本則由社群檢舉、經人工審核後發布,僅供風險參考,請自行查證。 遇到騙子曝光 @haihuabaoguangbot
📣新增騙子通報🆘 ⚠️原因:【投資詐騙】 名稱:奇迹ws(专业拉群) 用戶名: @Svip6668881 被騙金額:276 USDT 被騙說明: WS投放测试数量5000条 诈骗金额276 受理編號 R20260828-0001 檢舉人:匿名 ⚖️ 如果你认为此条指认有误,请私信本机器人输入 /appeal S000020 提出申诉,受理期间本条将先暂时隐藏。 本則由社群檢舉、經人工審核後發布,僅供風險參考,請自行查證。 遇到騙子曝光 @haihuabaoguangbot
📣新增騙子通報🆘 ⚠️原因:【投資詐騙】 名稱:瑶瑶🎣全球IM/TG/WS超链RCS/LINE/VB群发 用戶名: @yy102599 被騙金額:258 USDT 被騙說明: WS投放测试数量5000条 诈骗金额258 受理編號 R20260828-0002 檢舉人:匿名 ⚖️ 如果你认为此条指认有误,请私信本机器人输入 /appeal S000019 提出申诉,受理期间本条将先暂时隐藏。 本則由社群檢舉、經人工審核後發布,僅供風險參考,請自行查證。 遇到騙子曝光 @haihuabaoguangbot
Showing the 12 most recent of 23 posts we hold for @haihuabaoguan. 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 1 registered channel — 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.
Handles this channel named that no longer answer
- Dead references
- 2
- 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
- 1
- vacant every time we have ever looked
@haihuabaoguan named 2 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 1 post, 27 August 2026 – 27 August 2026 · confirmed gone 28 August 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 2 posts, 18 August 2026 – 27 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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“海华出海-全網騙子曝光頻道” (@haihuabaoguan), 33,056 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/haihuabaoguan.
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.