Telegram RegisterThe public register of Telegram
Telegram profile photo for 皇冠担保-公告频道

Channel

皇冠担保-公告频道

@hgii

2 usernames

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Cite this entry

12,737subscribers

+2,145 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-1003434401639
TypeChannel
Usernames@hggonggao @hgii
Description皇冠客服 @hgkf 供需频道 @hggx 官方大群 @hgdb 皇冠公群 @hggq 皇冠曝光 @hguu 皇冠海外 @hghw 皇冠专群组 @hgaa @hgbb @hgcc @hgdd @hgee @hgll 皇冠公群组 @hghh @hgkk @hgjj @hgff 皇冠天行组 @hgpp 皇冠海外组 @hggg @hgjj 皇冠娱乐 6i.com 娱乐机器人 @hgiiiiii_bot 投诉建议 @huidu 欲戴皇冠 必承其重
Created19 April 2026 — measured — dated from the channel’s first post
First recorded8 August 2026
Last confirmed live16 November 2026
Measurements held64
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/hgii

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 11 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@hgii/17 · this entry27 Jun 2026, 03:34 UTC@hgvv/3227 Jun 2026, 03:48 UTC1.0013 minutes
@hgii/23 · this entry23 Jul 2026, 14:23 UTC@hgvv/3923 Jul 2026, 14:27 UTC1.004 minutes
@hgii/34 · this entry12 Aug 2026, 10:36 UTC@hgvv/4512 Aug 2026, 10:38 UTC1.0072 seconds
@hgii/36 · this entry21 Aug 2026, 11:55 UTC@hgvv/4721 Aug 2026, 11:57 UTC1.0072 seconds
@hgii/39 · this entry24 Sept 2026, 13:25 UTC@hgvv/5024 Sept 2026, 13:29 UTC1.004 minutes
@hgii/47 · this entry17 Oct 2026, 09:25 UTC@hgvv/5117 Oct 2026, 15:05 UTC1.005.7 hours
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@hgvv8 (8/8 hand-verifiable sample passed)0.984 minutesthis entry (6–2)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 1 of the 2 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 29 comparable posts for this entry, running 19 April 2026 to 11 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 2 channels, the one whose matching posts we hold earliest is @hgvv. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 12 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

10,42020,83815,62912,7378 August 202616 November 2026
64 measurements spanning 100 days, net +2,145. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 8,857–22,401 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 64
Measured (UTC)SubscribersChange
16 Nov 2026, 08:0612,737+256
12 Nov 2026, 23:1612,481+544
10 Nov 2026, 18:4511,937+54
9 Nov 2026, 07:4111,883+40
7 Nov 2026, 23:0711,843+89
6 Nov 2026, 21:0511,754+39
5 Nov 2026, 20:3411,715+26
4 Nov 2026, 23:4011,689+57
4 Nov 2026, 01:0811,632+58
2 Nov 2026, 22:2011,574+54
2 Nov 2026, 00:4611,520-7,469
1 Nov 2026, 04:1718,989-1,849
31 Oct 2026, 03:1920,838+151
30 Oct 2026, 01:1720,687+21
29 Oct 2026, 04:3120,666+47
28 Oct 2026, 01:2020,619+31
27 Oct 2026, 00:0020,588+26
26 Oct 2026, 02:4120,562+110
25 Oct 2026, 00:2720,452+52
23 Oct 2026, 23:1820,400first reading

Engagement

39 posts held, back to 19 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 69 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
33.2%
avg views ÷ 12,737 subscribers
Avg views / post
4,230
9 posts measured
Reaction rate
0.097%
reactions ÷ views · ER floor
Posts in window
10
of 39 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 11 November 2026
Posts held39 (19 April 2026 – 11 November 2026)
Views total38,080
Reactions total37
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 21:30 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
2
Videos
2
Links
6

Lifetime counters from Telegram’s own channel header, read 17 November 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.

Video runtime
3m 58s
Average length
1m 59s

Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

111 reactions across 21 posts, in 9 distinct kinds. The most used accounts for 62.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤6962.2%
👍109.01%
💩109.01%
👎98.11%
🖕76.31%
🎄21.80%
🥰21.80%
☃10.901%
🔥10.901%

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 25 of the 39 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 111 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 39 most recent posts we hold, published 19 April 2026 to 11 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: 2 of 10 posts held from the last 30 days (20.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).

11 Nov 2026, 16:01 UTC≈4,340 views1 reactionsread 17 November 2026

皇冠公告快速导航 1.皇冠永久联系方式 2.皇冠担保流程 3.皇冠唯一上押方式 4.皇冠重要公告 5.皇冠收费标准 6.皇冠各类资源群进入方式

🥰1

Signed 皇冠公群H组24小时在线

11 Nov 2026, 16:00 UTC≈3,240 views1 reactionsread 17 November 2026
Video

需方交易机器人使用步骤 ① 如何找到并核实公群交易机器人 通过公群管理员列表或者置顶信息找到本公群唯一交易机器人并发送信息即可对接业务(联系公群内担保客服核实交易机器人真假) ② 使用机器人确认金额与规则 通过交易机器人报单,询问汇率,以及附加规则,业务沟通全程使用机器人确认(全程隐私保护不会泄露信息) ③ 核实信息后开始交易 确认规则以及汇率金额无误后,供方贴卡,拿卡入金,入金成功后发水单,供方查账,核实到账无误后,供方在窗口内报备该笔交易金额的u数,金额无误点击【✅确认】有误点击【❌取消】 ④ 报备成功 确认后公群会同步提示报备成功,系统自动冻结该笔交易金额的u数 ⑤ 确认下发报备释放押金 过保时后或下发时提供地址供方下发,核实收到u后,供方报备下发,金额无误点击【✅确认】有误点击【❌取消】报备下发同步到公群,完成作业!

❤1

Signed 皇冠公群H组24小时在线

11 Nov 2026, 16:00 UTC≈4,330 views2 reactionsread 17 November 2026

皇冠担保 官方通告 交易机器人正式上线 感谢大家的支持! 皇冠担保交易机器人现已上线,专为代收付公群打造,主要解决交易隐私与报备效率问题。 核心功能 1.每个客户独立对接窗口,全程隐私保护,不泄露任何客户信息 2.供方报备简单:输入 报备:+金额u 开始作业,输入 报备:-金额u 完成订单 3.需方确认后,押金自动冻结/释放,流程清晰可追溯 主要好处 1.隐私更安全,避免信息泄露 2.报备加减账操作简单,减少沟通成本 3.双方确认后才生效,降低纠纷风险 4.公群保持禁言,所有作业统一走机器人,更规范 请供方每笔作业必须报备,需方核实后务必点击确认。 如有疑问,请联系对应客服。 所有上线交易机器人的公群负责人联系对应公群客服进入专属交易群,此群组仅公群供方人员进入。 皇冠担保 2026年11月12日

❤2

Signed 皇冠公群H组24小时在线

11 Nov 2026, 16:00 UTC≈2,640 views2 reactionsread 17 November 2026
Video

公群方交易机器人使用步骤 ① 如何找到并核实公群交易机器人 通知群内人员本公群内管理员列表或者置顶信息可找到本公群唯一交易机器人点击发送信息即可对接业务(联系公群内担保客服核实交易机器人真假) ② 使用机器人确认金额与规则 通过交易机器人沟通交流,看客户需要打卡多少,有无规则备注,全部通过交易机器人确认(全程隐私保护不会泄露信息) ③ 核实信息后开始交易 需方喊贴卡后,贴卡等待入款,核实到账后立刻报备加数(报备:+/- 作业u数量),等待需方核实确认后报备生效,系统冻结作业金额 ④核实地址下发 保时到或者下发时,让需方提供地址,核实确认后进行下发。 ⑤ 确认下发报备释放押金 下发附带转账图,需方确认收到后进行报备(报备:+/- 作业u数量),等待需方确认报备信息后自动释放押金,完成作业

❤2

Signed 皇冠公群H组24小时在线

31 Oct 2026, 16:41 UTCviews —

皇冠担保-公告频道 pinned «皇冠担保 官方公告 感谢新老用户一直以来的支持与信任! 由于近期业务量持续上涨,为进一步提高服务效率与响应速度,于今早 10:00 现正式新增皇冠专群E组、 专群L组、公群J组。 我们将以更高标准继续为大家提供更高效、专业的服务。 皇冠专群E组:@hgee 电话号码:+888 0279 3634 皇冠专群L组:@hgll 电话号码: +888 0343 7516 皇冠公群J组:@hgjj 电话号码:+888 0696 7314 皇冠担保客服:@HGKF …»

31 Oct 2026, 16:37 UTC≈5,020 views9 reactionsread 17 November 2026

皇冠公告快速导航 1.皇冠永久联系方式 2.皇冠担保流程 3.皇冠唯一上押方式 4.皇冠重要公告 5.皇冠收费标准 6.皇冠各类资源群进入方式

❤3👍2👎2💩1🖕1

Signed 皇冠担保qq

31 Oct 2026, 16:36 UTC≈4,740 views13 reactionsread 17 November 2026

皇冠担保 官方公告 感谢新老用户一直以来的支持与信任! 由于近期业务量持续上涨,为进一步提高服务效率与响应速度,于今早 10:00 现正式新增皇冠专群E组、 专群L组、公群J组。 我们将以更高标准继续为大家提供更高效、专业的服务。 皇冠专群E组:@hgee 电话号码:+888 0279 3634 皇冠专群L组:@hgll 电话号码: +888 0343 7516 皇冠公群J组:@hgjj 电话号码:+888 0696 7314 皇冠担保客服:@HGKF 皇冠担保 2026年11月1日

❤4🖕3🎄2☃1👎1💩1🔥1

Signed 皇冠担保qq

31 Oct 2026, 10:52 UTC≈3,930 views4 reactionsread 17 November 2026

恭喜皇冠索来尔百家乐开业!内部群送100个88u!

👍4

Signed 灰度

30 Oct 2026, 16:07 UTC≈4,280 views5 reactionsread 17 November 2026
Photo

👑 皇冠担保 × 🚀 天美索引 战略合作公告 皇冠担保是深耕行业的TOP1担保平台,凭借过硬的背景、口碑与专业的风控能力,稳居行业第一梯队。 而天美索引则是今年新启、势头强劲的头部索引与流量平台。 双方基于高度互信,经亲切友好的协商,现正式达成核心战略合作!具体合作内容如下: 🔹 1. 流量全网覆盖与精准推送 天美索引作为新锐流量引擎,将全面发挥自身强大的搜索矩阵优势,为皇冠担保及合作商户提供全方位的广告推送与精准引流支持,实现资源的最优配置与高效转化。 🔹 2. 强强联手与深度协作 老牌担保的实力风控与新锐索引的庞大流量完美融合。天美索引全面赋能广告推送,皇冠担保提供顶级安全背书,为广大新老用户保驾护航,提供专业、安全、高效的担保服务。 🔹 3. 共创共赢 共赴未来 本次合作纯属英雄相惜、相互成就。未来,双方将携手并进,共同为广大客户和合作伙伴提供更优质、更具保障的服务体验,在各自的赛道上再创辉煌! 📌 官方联系方…

❤5

Signed 皇冠担保yy

21 Oct 2026, 14:50 UTC≈5,560 views0 reactionsread 17 November 2026

皇冠公告快速导航 1.皇冠永久联系方式 2.皇冠担保流程 3.皇冠唯一上押方式 4.皇冠重要公告 5.皇冠收费标准

Signed 皇冠担保qq

19 Oct 2026, 04:12 UTC≈6,330 views10 reactionsread 17 November 2026

皇冠担保 官方公告 感谢新老用户一直以来的支持与信任! 由于近期业务量持续上涨,为进一步提高服务效率与响应速度,于 今天14:00 现正式新增皇冠公群F组。 我们将以更高标准继续为大家提供更高效、专业的服务。 皇冠公群F组:@hgff 电话号码:+888 0574 0971 皇冠担保客服:@HGKF

💩6👎2🖕2

Signed 皇冠担保qq

17 Oct 2026, 09:25 UTC≈6,730 views14 reactionsread 17 November 2026

皇冠担保 官方公告: 代收付公群交易机器人正式上线 为解决拉私群交易双删记录的问题,同时进一步提升跑分类型公群的交易效率与安全性,皇冠担保特推出公群专属 交易机器人。 核心优势 1. 全程隐私保护 单独给每个公群配置一个交易群,群内所有聊天均受隐私保护,不会透露任何客户信息,保障双方安全。 2. 报备流程简单高效 群内加减账操作与公群押金关联,供方报备、需方确认即可自动更新押金状态,减少沟通成本,超押风险。 使用方法 公群方:联系当组担保拉单独交易群,生成专属本群的交易机器人,群里仅拉入公群供方人员 客 户:私聊对应公群专属机器人报单,喊卡,公群贴卡,料方发进款发图,公群查账后,报备加帐,料方确认加帐,公群报备下发,料方确认下发 注意:每个客户设有单独对接窗口,通过群专属机器人可直接联系供方工作人员,全程隐私保护,交易必须进行机器人加减账单 加减账指令 开始作业:报备:+100u(直接填写作业金额,无需报汇率) …

❤7👎4💩2🖕1

Signed 皇冠担保yy

Showing the 12 most recent of 39 posts we hold for @hgii. 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

@hgii edited 4 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 November 2026

Posts recorded as deleted after publishing

We recorded 5 posts on @hgii 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
9 August 2026
Most recent seen missing
22 August 2026
Median time before seen missing
3 days
Seen missing in the last 30 days
0

Mentions

Named by 10 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.

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 16 November 2026 — this entry's latest reading, not the date you are reading this.

“皇冠担保-公告频道” (@hgii), 12,737 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/hgii.

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.