Channel
@hgtt
On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
6,732subscribers
-261 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1003635511680 |
|---|---|
| Type | Channel |
| Usernames | @hgjfal @hgtt |
| Description | 皇冠客服 @hgkf 供需频道 @hggx 官方大群 @hgdb 皇冠公群 @hggq 皇冠曝光 @hguu 皇冠海外 @hgww 专群A组 @hgaa 专群B组 @hgbb 公群H组 @hghh 海外G组 @hggg 投诉建议 @huidu 认准ID谨防上当受骗！ |
| Created | 20 April 2026 — measured — dated from the channel’s first post |
| First recorded | 8 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 11 August 2026 |
| On Telegram | t.me/hgtt |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 00:15 | 6,732 | -252 |
| 8 Aug 2026, 08:12 | 6,984 | -9 |
| 8 Aug 2026, 04:30 | 6,993 | first reading |
17 posts held, back to 20 April 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 7 pagesof Telegram’s post history, 20 posts per page.
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 2 of 6 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 29 July 2026 |
|---|---|
| Posts held | 17 (20 April 2026 – 29 July 2026) |
| Views total | 1,866 |
| Reactions total | 2 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 02:52 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.
24 reactions across 9 posts, in 3 distinct kinds. The most used accounts for 54.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 13 | 54.2% | |
| 👍 | 10 | 41.7% | |
| 🔥 | 1 | 4.17% |
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 11 of the 17 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 24reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 20 April 2026 to 29 July 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.
日期： 2026年7月29日 纠纷群：A组2183群 纠纷双方： @ddf**** 供方 @pp*** 需方 纠纷事由：送现业务，反馈取手被摁 处理结果：正常下发 处理思路： 1，无视频，拿货后近一小时反馈被摁。 2，鱼正常，后续也交易2笔，纠纷前一笔也是该车熟悉的人接的。 3，要求查询取手案件，期间车队反馈是取手动了心思。 4，正常该类情况真钓鱼单基本后续不会继续开刀。 经验总结：人心隔肚皮，自觉再好的掌控也难免在利益面前猪油蒙心。
Signed 皇冠仲裁aa
日期： 2026年7月26日 纠纷群：A组2321群 纠纷双方：骗子供方 @wanwan1de 骗子需方： @BXS3368 纠纷事由：担保办理业务时发现作业可疑，提交仲裁审核。 处理结果：骗子拉黑，押金待原地址主人办理退押 处理思路： 1，看作业码接回U。让提供切客，无法提供。 2，说是搬砖，无法提供搬砖记录。 3，收款码给所谓鱼付款，对方还能成给收款到账图？ 4，明显做图，骗子供方还一起要求立马下发。 由此可见，双方一起，骗第三方给担保地址上押，从而骗取押金 经验总结： 目前已经发现多起冒充所谓盘口，然后或者拉假群给担保真地址让对方转u，之后骗子拿着该上押图做假交易骗取押金。 特别是上押 要先行核对担保官方号，官方地址等等。确认无误之后再上押并立马发图@担保查账。 关注公告频道： @hggonggao 核实真假。 最简单的核实方法：手动输入担保号，看所在共同群并且可以发送消息验证。
❤2
Signed 皇冠仲裁aa
日期： 2026年7月22日 纠纷群：H组6666群 纠纷双方： @du**** 供方 需方： @Uc9***** 纠纷事由：会员放货后经车队核实离开，提供离开图后，要求车队去拿包裹，车队反馈取手被按，前台反馈会员还正常 处理结果：按钓鱼单处理。 处理思路： 监控视频清晰，放货离开后5分钟又返回现场，又过2分钟直接条子摁取手到现场，典型的钓鱼单。 经验总结：已经清晰明确的东西，就没有必要再浪费时间。
Signed 皇冠仲裁aa
日期： 2026年7月22日 纠纷群：A组2204群 纠纷双方： @oo**** 供方 骗子： @ldbb @ruanxiongg 纠纷事由：反馈被拉假群但上押真地址。7点既转u上押查账并中途还2次上押直至接近12点才发现上当。 经查实，此前已虚假作业并且双方确认办理多次下发。 处理结果：骗子拉黑，剩余押金原地址退押 经验总结：一定要吃一堑长一智，涉及资金方面一定要慎重。 特别是上押 要先行核对担保官方号，官方地址等等。确认无误之后再上押并立马发图@担保查账。 关注公告频道： @hggonggao 核实真假。 最简单的核实方法：手动输入担保号，看所在共同群并且可以发送消息验证。
Signed 皇冠仲裁aa
日期： 2026年7月20日 纠纷群：A组21117群 纠纷双方： @shu**** 供方 @JH*** 需方 纠纷事由：会员放包裹后 车队引导离开后 说有异常无法提供监控视频 安排去拿货 然后说没拿到 后面喊会员回现场包裹不在了 车队提供不了完整视频 处理结果：正常下发 处理思路： 1，无全程视频，从放，鱼离开，再到鱼回来，中间有不少时间。 2，在鱼回来中间也有车队让取手过去，视频中也没有体现也没有反馈东西是否在与不在。 3，异常说有车一起，就只看到一个过路车也无其他举证，取手也是在马路对面拍摄。 4，鱼后续且也继续入金。 经验总结：作为该业务中，最不可或缺的就是视频也是一个最基本的操作。要不然真损失了闷棍也得自己扛了，当然内部人员还需加强。
Signed 皇冠仲裁zz
日期： 2026年7月18日 纠纷群：H组8889群 纠纷双方： @ss**** 供方 @Tia*** 需方 纠纷事由：滴滴现金，会员开车送，正常引导放，取手拿货后，车队反馈包裹内为假币，未提供完整验货视频。 处理结果：正常下发 处理思路： 1、无法提供开箱等视频 。。 2，诈鱼反馈与切客经过相符并陈述为真币。 3，在没有开箱视频证据的情况下，以核实鱼情况为准。 经验总结：作为该业务中，最不可或缺的就是视频也是一个最基本的操作。要不然真损失了闷棍也得自己扛了，当然内部人员还需加强。
Signed 皇冠仲裁zz
日期： 2026年7月9日 纠纷群：A组23192群 纠纷双方： @白**** 供方 @wlx*** 需方 纠纷事由：一道进算保24，进款5000触发二次认证。 处理结果：正常下发 处理思路： 1、这里双方交易进款前对于二次做了说明：需方不负责二次，由供方承担。 2，保时内未反馈司法无提供司法说明。 3，核实料性为规则内，所以正常下发。 经验总结：如对作业中类如二次，24保护等等不明白的地方可以咨询仲裁，能接受与否后再选择做或者协商好规则。
❤1
Signed 皇冠仲裁zz
日期： 2026年6月27日 纠纷群：公群H6667 纠纷双方： @pa*** 供方 @h*** 需方 纠纷事由：19号打款一笔49990保三天司法，21号司法了，卡余50449为冻结后入金 处理结果：回款两层需方 处理思路： 1，市场上冻结后入金不赔付应该这么去理解，是车队没测卡验卡直接用卡前面的已经司法后面再去入那前面的钱已经拖出去了那不应该赔，核实车队21号当天开工记录有测卡验卡记录不是恶意入金来索要赔付。 2，冻结12：15，发卡12：11，入款12：18，时间上也不存在冻结后恶意入金找前一笔料方赔付。 3，当天测卡时间为10：22流程上间隔这么久也属于一定的业务疏忽，但不是主责，归根结底还是没保住。 经验总结：建议排卡时同步一份验卡态的视频，规避不必要的亏损。
❤1
Signed 皇冠仲裁aa
日期： 2026年6月25日 纠纷群：A组23140关联H8888群 纠纷双方： @Xxia**** 供方 @Bcz*** 需方 纠纷事由：送现6.7w反馈包裹里是练功券。 处理结果：无需下发 处理思路： 1、全程鱼放，取手拿，拆包视频有，明显一眼假。 2，明显的东西没有硬扯提前调包的道理。况且外包并不是常见的东西。 3，正常该种作业模式，以拆包为准。 经验总结：事实清晰，认对于该类型作业监控的重要性。
Signed 皇冠仲裁zz
日期： 2026年6月25日 纠纷群：A组23086 纠纷双方： @kaik**** 供方 @ab** 需方 纠纷事由：送现9w反馈取手被摁。 处理结果：无需下发 处理思路： 1、作业订单21日，送现9万，到达位置后刚开始反馈有异常并包裹被其他人拿走，后反馈失联。 2，提供证据取手被摁，经天眼查询该鱼10日已经报警并且同案10日已摁，。 3，该单为典型的钓鱼单。 经验总结：事有因并有果。
Signed 皇冠仲裁zz
日期： 2026年6月25日 纠纷群：A组23057 纠纷双方： @Sd1**** 供方 @duu** 需方 纠纷事由：送现4w拿完撤离1小时反馈取手回复暗号怀疑被摁。 处理结果：正常下发需方 处理思路： 1、从作业群记录反馈，该笔订单拿到1小时说收到暗号且还多次消息。真摁，能消息的一般条子也不会让。 2，经双方提供证实对比，该笔款项之后当天与隔天该鱼都有交易且正常作业下分。 3，对于类似事情，排除鱼问题的情况下，要么取手有心要么因为其他事情。 经验总结：对于取手的使用，还需好好斟酌。
❤1
Signed 皇冠仲裁zz
日期： 2026年6月17日 纠纷群：A组23002 纠纷双方： @n**** 供方 @a**** 需方 纠纷事由：送现3.3w 引导会员离开后被第三方抢包。 处理结果：正常下发需方 处理思路： 1，现场车队引导鱼离开后包裹被第三方抢走归属供方责任 2，需方鱼经核实本单取款记录，下一刀作业记录，三方对接记录，作业群加分情况核实为真鱼 3，现场视频第三方抢包行为专业，遮脸拿包就撤，不是同行就是内部泄密。 经验总结：地址最好是用过两次换一下 保证安全的前提下也避免同行，还有抢的那就要怀疑自己人了。
❤3👍2
Signed 皇冠仲裁aa
Showing the 12 most recent of 17 posts we hold for @hgtt. 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 — 240,732 of 1,336,469entries 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.
Named by 9 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.
@hgtt 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.
References a handle that is not a live channel — we have no record it ever was one.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“皇冠担保纠纷案例” (@hgtt), 6,732 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/hgtt.
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.