The owner of this channel has been inactive for the last 11 months. If they remain inactive for the next 17 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.

Channel
汇旺公群 @hwgqln
@hwgqln
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
690subscribers
+0 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001854166724 |
|---|---|
| Type | Channel |
| Username | @hwgqln |
| Description | 客服频道 @huinoe 公群频道 @hwgqln 供求频道 @gongqlu 核心大群 @dalqun 官方网站 https://www.yu444.com 公司介绍 @hwdbgss 公群机器人 @QunGrambot 专群机器人 @hejy444bot |
| Created | Between 1 October 2022 and 14 May 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/hwgqln |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 02:15 | 690 | no change |
| 9 Aug 2026, 02:03 | 690 | first reading |
Engagement
20 posts held, back to 14 May 2023 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 13 June 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Links
- 78
Lifetime counters from Telegram’s own channel header, read 9 August 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
The owner of this channel has been inactive for the last 11 months. If they remain inactive for the next 30 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
1️⃣代收类: 1.卡接一道回u 2.码接回u 3.卡接二道回u 4.海外直通车 2️⃣承兑类: 1.支付宝微信 2.现存承兑 3.多种资金 4.抖音快手等核销 5. 实物回u 3️⃣收u代付类: 1.白资公群 2.二道保时 3.二道混料 4.一道放料 5.其他资金 4️⃣合作类: 1.卡商公群 2.固话手机口 3.app跑分 4.招车队 5.贴卡片 6.快递代发 7.租号 5️⃣服务类: 1.查档公群 2.开飞机会员 3.票务酒店 4.设计类 5.搭建类 6.接码代实名 6️⃣买卖类: 1.卖各种号 2.买卖手机卡 3.卖数据 4.卖能量trx 5.收粉引流 6.烟酒奢侈品 7️⃣其他类: 外围 AI换脸 渗透等等 (新群) 8️⃣vip小公群: 1.代收类 2.承兑类 3.收u代付类 9️⃣游戏公群: 1.pc28游戏 2.百家乐 3.骰子游戏 4.红包牛牛 5.其他游戏
重要通知和说明: 1、一定要走公群里交易,认准带头衔的管理人员,私聊交易或其他地方交易,无保障,所有后果自负,如果群老板或者业务员让你去其他地方交易,或者直接私聊交易,请联系我们举报。 2、专群频道: @huinoe 可以在此学习专群的相关知识。 公群频道:@gongqunBZ 可以在此了解公群交易的注意事项。 订阅供求信息 @gongqlu 可以看各种商机。 3、请勿相信私聊发群链接的,都是骗子,请直接拉黑。另外,凡是在公群群发广告的,一律加入汇旺黑名单。 4、担保工作人员都很忙,不会主动私聊你,主动私聊你的100%都是骗子,请直接拉黑。 5、公群消失需要恢复群的群老板请将群号和群老板用户名提交 @hwjy074 。 6、汇旺担保旗下综合盘正式上线,招代理,点击进入,汇旺娱乐,官方直营综合盘 7、满一年的公群,导航加一年的标识1️⃣ ,公群logo正中间有1。 8、汇旺担保启用4个永久、好记、防失联用户名:…
5、其他游戏(注意:不在此导航里面的群都是假公群,我们只担保在我们公群内游戏能正常上下分,不担保群老板个人信誉,不担保代理、拉手等和群老板的其他交易或合作。): 🔥8 汇旺娱乐,11月送奥迪A6L🔥 1⃣ 16 旺博体育:综合盘 326 腾博会电子:老虎机/捕鱼 76 旺博鱼虾蟹游戏 66 九博综合群(体育/视讯/棋牌) 201 腾博会哈希28 90 新宝电子:PG/FG/JDB/CQ9 22 天豪九点红包
4、牛牛游戏(注意:不在此导航里面的群都是假公群,我们只担保在我们公群内游戏能正常上下分,不担保群老板个人信誉,不担保代理、拉手等和群老板的其他交易或合作。): 23 旺博红包牛牛 163 武氏红包牛牛 1⃣ 55 旺博13倍牛牛 91 九博红包牛牛 707 萬利會红包牛牛 萬利會极速红包牛牛 983 昌盛娱乐红包牛牛 222 武氏集团pc20倍牛牛 1088 福布斯(极速)红包牛牛 151 新澳门西湖真人牛牛 129 京东红包牛牛
3、骰子游戏(注意:不在此导航里面的群都是假公群,我们只担保在我们公群内游戏能正常上下分,不担保群老板个人信誉,不担保代理、拉手等和群老板的其他交易或合作。): 1⃣ 97 旺博骰子游戏(极速游戏) 旺博私聊极速骰子机器人 108 武氏集团骰子/极速私聊骰子 1⃣ 727 萬利會骰子,一秒开奖 萬利會5.8倍极速私聊骰子 186 昌盛娱乐骰子游戏 285 天胜集团骰子游戏 80 九博(极速骰子)游戏 1️⃣ 85 腾博会骰子/极速骰子 15 福布斯骰子(极速游戏) 27 开云骰子(豹子正常赔)
2、百家乐游戏(注意:不在此导航里面的群都是假公群,我们只担保在我们公群内游戏能正常上下分,不担保群老板个人信誉,不担保代理、拉手等和群老板的其他交易或合作。): 1⃣ 35 旺博视讯百家乐(卡卡湾1台) 1⃣ 36 旺博哈希百家乐 1⃣ 336 兄弟&亚星电投百家乐 338 旺博视讯百家乐2台 1⃣ 73 西湖洲际百家乐 68 新澳门西湖百家乐 79 新澳门南海百家乐 456 铂莱百家乐 1⃣ 83 东方汇视讯百家乐
1⃣ 11 旺博2.8倍pc28游戏 865 武氏2.8倍pc28 1⃣ 96 九博国际2.8pc28 89 萬利會2.8倍PC28 133 天胜集团2.8倍pc28 177 腾博会2.8倍加拿大pc28 902 天胜集团PC5.0 37 聚利国际2.8倍pc28 75 安彩2.82倍PC28 77 永發2.8倍加拿大pc28 3)、网盘pc28: 1⃣ 38 旺博PC28网盘(无13/14) 829 天胜集团pc28网盘 1⃣ 172 美高美PC28网盘赔率(无13/14) 78 萬利會pc28网盘(无视13/14) 92 九博国际网盘PC 1️⃣ 225 凯越pc28网盘(无13/14) 39 东方集团网盘PC28(无13/14)
十、游戏类公群(注意:不在此导航里面的群都是假公群,我们只担保在我们公群内游戏能正常上下分,不担保群老板个人信誉,不担保代理、拉手等和群老板的其他交易或合作。): 1、加拿大pc28游戏: 1)、2.0加拿大pc28: 1⃣ 28 旺博2.0加拿大PC28 1⃣ 95 武氏集团2.0pc28 1⃣ 99 九博国际2.0pc28 1⃣ 26 腾博会加拿大pc28 25 大发2.0加拿大pc28 570 萬利會pc28 819 天胜集团pc28 292 KK国际2.0pc28 75 飞扬国际2.0PC28 832 至尊贵宾会2.0pc28 50 万博国际PC2.0 2) 、高倍加拿大pc28:
VIP公群3198 华伦集团大区二道收U 群老板:@HLJT9 VIP公群3197 华伦集团资金盘二道保三天 群老板:@HLJT9 VIP公群3196 华伦集团精聊二道收U 群老板:@HLJT9 VIP公群3192 精聊大区二道保当天收U 群老板:@Wsndy111 VIP公群3183 混二道进算收U 群老板:@hh88688 VIP公群3182 晚风二道收u 群老板:@Wanf168 VIP公群3181 宝利大混二道收U 群老板:@edthb001 VIP公群3173 水之梦二道大混进算收u 群老板:@YTX667788 VIP公群3152 简朴寨二道卡收u公群 群老板:@LLQLLQ668 VIP公群3121 劳斯POS资金收U 群老板: @RoLLsroycea VIP公群3109 土土二道混料收U 群老板:@tutu1101 1️⃣ VIP公群3099 大押金保72小时收U 群老板:@HLJT9 VIP公群3098 小…
3)、收u代付类:(VIP小公群不公开,需要联系后面的群老板号进群,群老板如果更换用户名,需第一时间联系交易员修改联系用户名,用户名变更造成客户被拉假群的,群老板全责。) 进群后联系官方客服,走公群里交易,私聊交易或其他地方交易,无保障,所有后果自负 VIP公群3537 二道收u 群老板:@WM868 VIP公群3535 二道收U主营进算和保时 群老板:@xgp99599 VIP公群3533 猪刚鬣二道综合混料收u 群老板:@zhuzu55 VIP公群3456 诚久支付收u 群老板:@maikou158 VIP公群3380 二道进算收U 群老板 @pxkk68 VIP公群3376 摇钱树二道收u 群老板:@yqs21320 VIP公群3363 天盛长歌二道混料收u 群老板:@tiansheng12 VIP公群3335 发奋图强二道进算收u 群老板:@fftq223 VIP公群3333 海马支付一道保三收U 群老板:@HAMO_…
Showing the 12 most recent of 20 posts we hold for @hwgqln. 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.
Citation-graph rank
Citation-graph rank — 908,208 of 1,480,688entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Mentions
Named by 2 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.
@gongqunBZ · 221 post好涩
@haose666 · 11 posthta88
@hta88 · 21 post@huinoe 汇旺担保客服频道
@huinoe · 1261 post汇享国际供需频道
@HXJT9999 · 11 postmaikou158
@maikou158 · 11 post东南亚热点大事件
@pfpf118 · 11 postpxkk68
@pxkk68 · 21 post山姆精选-全国高端外围🉑约上门服务
@qwertyuipp1 · 11 postshunshun_000
@shunshun_000 · 51 postVIP公群3297 成都,重庆同台白资换U
@usdt225588 · 101 post山姆精选-全国高端外围🉑约上门服务
@w001818 · 41 postwangyi8878
@wangyi8878 · 51 post1
@Whui5566 · 51 post现存🎉银行卡🎉数字货币🎉保时
@xiancun · 51 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
- 74
- 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
- 74
- vacant every time we have ever looked
@hwgqln named 74 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 2 posts, 10 August 2026 – 10 August 2026
named in 2 posts, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
named in 1 post, 10 August 2026 – 10 August 2026
24 more handles are in this same list but not shown individually here — capped at 50.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“汇旺公群 @hwgqln” (@hwgqln), 690 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/hwgqln.
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.