Channel name was changed to «皇冠海外频道(备用)»

Channel
皇冠海外频道(备用)
@hgww
On this record: Topic · Growth · Engagement · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
24,084subscribers
-2,825 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 | -1003910551244 |
|---|---|
| Type | Channel |
| Usernames | @haiwai1 @hgww |
| Created | Between 1 April 2026 and 7 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 10 September 2026 |
| Measurements held | 28 |
| Confirmed unchanged | 1 time, most recently 10 September 2026 |
| On Telegram | t.me/hgww |
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 91% 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 |
|---|---|---|
| 10 Sept 2026, 15:21 | 24,084 | +72 |
| 7 Sept 2026, 12:38 | 24,012 | -38 |
| 4 Sept 2026, 15:02 | 24,050 | -10 |
| 3 Sept 2026, 01:35 | 24,060 | -23 |
| 1 Sept 2026, 20:14 | 24,083 | -9 |
| 31 Aug 2026, 19:45 | 24,092 | -5 |
| 30 Aug 2026, 16:38 | 24,097 | -29 |
| 29 Aug 2026, 15:16 | 24,126 | -37 |
| 28 Aug 2026, 16:02 | 24,163 | -3 |
| 27 Aug 2026, 16:08 | 24,166 | -2,657 |
| 26 Aug 2026, 17:55 | 26,823 | -1,299 |
| 25 Aug 2026, 15:52 | 28,122 | +1 |
| 24 Aug 2026, 17:13 | 28,121 | +18 |
| 22 Aug 2026, 23:23 | 28,103 | +9 |
| 21 Aug 2026, 12:57 | 28,094 | +79 |
| 20 Aug 2026, 10:02 | 28,015 | +92 |
| 19 Aug 2026, 12:02 | 27,923 | +64 |
| 18 Aug 2026, 15:13 | 27,859 | +65 |
| 17 Aug 2026, 13:23 | 27,794 | +83 |
| 16 Aug 2026, 03:26 | 27,711 | first reading |
Engagement
24 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 55 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 12.4%
- avg views ÷ 24,084 subscribers
- Avg views / post
- 2,980
- 1 post measured
- Reaction rate
- 0.201%
- reactions ÷ views · ER floor
- Posts in window
- 2
- of 24 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 2 September 2026 |
|---|---|
| Posts held | 24 (7 August 2026 – 2 September 2026) |
| Views total | 2,980 |
| Reactions total | 6 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 10: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.
Reaction mix
29 reactions across 11 posts, in 2 distinct kinds. The most used accounts for 93.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 27 | 93.1% | |
| 👍 | 2 | 6.90% |
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 12 of the 24 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 29 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 24 most recent posts we hold, published 7 August 2026 to 2 September 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
皇冠担保 官方公告 原万邦海外公群频道已完成交接转移。 现正式更改用户名为:@hghw (取自「皇冠海外」首字母拼音) 后续海外公群相关信息与通知,请以新账号 @hghw 为准。 感谢大家的支持与配合! 公群客服:@hggg 皇冠担保客服:@HGKF
❤4👍2
1,皇冠官方永久联系方式公示 2,皇冠海外上押规则
❤2
皇冠海外板块直通车 ⚡️亚洲:1.亚洲直通车 2.亚洲放料 3.亚洲二道 ⚡️欧洲:1.欧洲直通车 2.欧洲放料 3.欧洲二道 ⚡️美洲:1.美洲直通车 2.美洲放料 3.美洲二道 ⚡️非洲:1.非洲直通车 2.非洲放料 3.非洲二道 ⚡️大洋洲:1.大洋洲直通车 2.大洋洲放料 3.大洋洲二道 ⚡️全球综合:全球综合直通车 ⚡️海外窗口公群:1.招车 2.招料 ⚡️引流类公群:1.海外收粉出粉 2.海外数据 原万邦海外待租公群: 1.①未分类第一页 2.②未分类第二页 3.③未分类第三页 1.亚洲直通车 2.全球综合直通车 原万邦海外其他类别招租点击此处
❤4
1
❤1
全球综合直通车 2258 全球出入金海外直通车公群 1812 海外全球直通车公群 120 海外直通车电子钱包/卡接回U公群 388 国际支付海外直通车公群 510 印度接大额全类/日本/欧洲/海外直通车公群 1501 缅甸/柬埔寨/印尼/马来/欧洲海外直通车公群 1579 全球支付海外直通车公群
❤4
亚洲直通车 525 日本马来印尼直通车 790 阿联酋/阿曼/约旦/文莱/源头直通车公群 1079 日本真一手车队海外直通车公群 1126 菲律宾一手车可接一切无视料直通车公群 1648 泰国 老挝 直通车 G:283 台湾日本直通车公群
❤2
皇冠海外退押招商 注意:不在此导航里面的群都是假公群,我们只担保属于公群中的业务,不担保群老板的其他业务与群老板的个人信誉,必须在公群内先报备再交易,我们只担保公群内已报备过的交易,不在公群内发生的纠纷一律不受理,私聊或其他地方交易后果自负 原万邦海外待租公群:第二页 286 516 596 801 242 936 780 2225 484 1125 505 937 817 969 282 718 828 209 546 1048 204 325 1088 681 1057 159 269 805 955 319 203 390 3094 2963 3072 3023 135 3096 2956 2608 906 569 213 677 148 1529 1565 1032 1760 1631 2825 3058 9997 1177 3043 1928 1725 1531 1378 1586 1555 2998 2581 988…
皇冠海外退押招商 注意:不在此导航里面的群都是假公群,我们只担保属于公群中的业务,不担保群老板的其他业务与群老板的个人信誉,必须在公群内先报备再交易,我们只担保公群内已报备过的交易,不在公群内发生的纠纷一律不受理,私聊或其他地方交易后果自负 原万邦海外待租公群:第一页 3027 2190 2717 2916 2510 2442 2447 1223 190 3098 2832 368 2431 3108 3107 1822 2578 9866 695 122 1812 1789 1901 1558 1955 487 112 2385 3176 3071 3131 171 527 645 497 982 5689 513 1330 469 565 893 2999 7915 675 471 550 722 881 1300 811 802 895 762 908 496 772 251 629 444 1608
❤2
皇冠海外退押招商 注意:不在此导航里面的群都是假公群,我们只担保属于公群中的业务,不担保群老板的其他业务与群老板的个人信誉,必须在公群内先报备再交易,我们只担保公群内已报备过的交易,不在公群内发生的纠纷一律不受理,私聊或其他地方交易后果自负 原万邦海外待租公群:第三页 7612 2708 3106 2745 2611 526 6555 755 1740 362 2205 1829 2714
❤1
1
海外数据 注意:不在此导航里面的群都是假公群,我们只担保属于公群中的业务,不担保群老板的其他业务与群老板的个人信誉,必须在公群内先报备再交易,我们只担保公群内已报备过的交易,不在公群内发生的纠纷一律不受理,私聊或其他地方交易后果自负。 海外数据第1页 G:1188 供押168888U--蓝雨国内外-猫池卡发-机房
Showing the 12 most recent of 24 posts we hold for @hgww. 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
@hgww edited 10 posts 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
- 9 August 2026
- Most recent edit
- 3 September 2026
Mentions
Named by 7 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.
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 10 September 2026 — this entry's latest reading, not the date you are reading this.
“皇冠海外频道(备用)” (@hgww), 24,084 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/hgww.
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.