Channel
@hanggui
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
2,127subscribers
-2,350 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002164882867 |
|---|---|
| Type | Channel |
| Usernames | @hanggui @huichanguize |
| Created | 20 August 2024 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 18 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/hanggui |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 07:14 | 2,127 | -11 |
| 30 Aug 2026, 03:34 | 2,138 | -315 |
| 27 Aug 2026, 13:24 | 2,453 | no change |
| 27 Aug 2026, 11:45 | 2,453 | -192 |
| 24 Aug 2026, 18:47 | 2,645 | -32 |
| 24 Aug 2026, 10:47 | 2,677 | -377 |
| 20 Aug 2026, 16:43 | 3,054 | -11 |
| 20 Aug 2026, 08:12 | 3,065 | -270 |
| 17 Aug 2026, 19:56 | 3,335 | -14 |
| 17 Aug 2026, 15:55 | 3,349 | -283 |
| 14 Aug 2026, 18:24 | 3,632 | -33 |
| 14 Aug 2026, 12:18 | 3,665 | -272 |
| 11 Aug 2026, 10:59 | 3,937 | -41 |
| 11 Aug 2026, 04:52 | 3,978 | -290 |
| 8 Aug 2026, 17:33 | 4,268 | -161 |
| 8 Aug 2026, 03:54 | 4,429 | -48 |
| 7 Aug 2026, 17:02 | 4,477 | no change |
| 7 Aug 2026, 16:48 | 4,477 | first reading |
4 posts held, back to 20 August 2024 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 5 pagesof 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 4 posts for this entry, the most recent from 12 February 2025. An engagement rate over an empty window would be a number about nothing.
2 reactions across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 100.0% |
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 1 of the 4 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 2reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 4 most recent posts we hold, published 20 August 2024 to 12 February 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
在公群作业中，人头送卡已经报备的，证据已经证实己送人，如果此时公群出现追溯纠纷时！视为人头己送无法中止交易，结算优先于其他追溯本群业务的纠纷！此时就算没打，强行作业！群内明显洗押也是可以高于其他纠纷的！但是必须提供完整证据链！报备必须是真实的，或者操作记录全部能对接上！证据证明确实是真的已经作业！缺一不可！不能靠猜测！注意！证据不足或者报备错误造成的后果是无法结算的！涉嫌套押金无法结算！所以中介上人一定不要嫌麻烦！按照要求如实报备，对自己利益也会有保障！
❤2
在公群专群作业中，卡号下面备注禁止地区等，涉及到一些关键字！比如说地区后面带关键词的！如“新疆户头”在支付行业里就是银行卡帐户，不能用于人头户籍地
1️⃣🟢无论黑产还是灰产或者是其他类型的产业都是要有一个统一的标准及规矩！ 2️⃣🟢在发生纠纷时以一个公平公正⚖️公开的条则来判定！而不是根据某些人自己的心情和不专业的知识来进行到判断！“抱着反正不是他的钱”的态度来处理问题！这样就有失公允！ 3️⃣🟢“行业内规则”以下简称为“行规” @hanggui 是根据以往判定经验和各担保平台及相关实际操作情况，结合历史结果来进行研究和总结的！并对一些不足做出相应修改！也请大家多多指点一二。 4️⃣🟢 “行规” @hanggui 独立于任何组织及担保势力之外！只站在公正立场上看待问题！所有观点不会偏向任何个人及组织！也绝不会向任何势力及组织屈服！ 5️⃣🟢“行规” @hanggui 己启用永久用户名N F T，为防止失联请大家记住“行规” @hanggui 拼音既可！
Channel created
Showing the 4 most recent of 4 posts we hold for @hanggui. 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 — 543,257 of 1,627,068entries 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 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.
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.
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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“灰产|跑分| 【行业|规则】” (@hanggui), 2,127 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/hanggui.
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.