Channel
@hengan88888888
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
1,114subscribers
+82 since we began measuring on 16 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002310920340 |
|---|---|
| Type | Channel |
| Username | @hengan88888888 |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 16 August 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 11 October 2026 |
| On Telegram | t.me/hengan88888888 |
Hacking & security — 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 18 September 2026 and assigned it the closest of 31 fixed categories, at 60% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Oct 2026, 17:57 | 1,114 | +8 |
| 4 Oct 2026, 20:55 | 1,106 | +6 |
| 25 Sept 2026, 14:56 | 1,100 | +7 |
| 17 Sept 2026, 06:57 | 1,093 | +6 |
| 12 Sept 2026, 20:36 | 1,087 | +2 |
| 8 Sept 2026, 17:38 | 1,085 | +4 |
| 3 Sept 2026, 10:58 | 1,081 | +20 |
| 30 Aug 2026, 23:38 | 1,061 | +9 |
| 28 Aug 2026, 01:34 | 1,052 | +12 |
| 24 Aug 2026, 17:36 | 1,040 | +1 |
| 20 Aug 2026, 22:02 | 1,039 | +4 |
| 17 Aug 2026, 18:37 | 1,035 | +3 |
| 16 Aug 2026, 19:30 | 1,032 | no change |
| 16 Aug 2026, 19:15 | 1,032 | first reading |
20 posts held, back to 16 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 1 page of 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 16 August 2026. An engagement rate over an empty window would be a number about nothing.
【通道名称】：抖音固额 【通道编码】：664 【固定金额】：10 费率2️⃣0️⃣🔤8️⃣ 【通道名称】：支付宝纯原生 【通道编码】：999 【固定金额】：100 200 费率1️⃣6️⃣🔤3️⃣🔽🔽 【通道名称】：支付宝纯固额原生 【通道编码】：822 【固定金额】： 50 费率1️⃣6️⃣🔤3️⃣🔽🔽 【通道名称】：支付宝纯原生 【通道编码】：890 【固定金额】：30-90 费率1️⃣6️⃣🔤3️⃣🔽🔽 【通道名称】：994 【通道编码】：支付宝超小额全层原生 【固定金额】： 1-9 先切❌❌
【通道名称】：支付宝纯原生 【通道编码】：999 【固定金额】：100 200 费率1️⃣7️⃣🔤5️⃣🔽🔽 【通道名称】：支付宝纯固额原生 【通道编码】：822 【固定金额】： 50 费率1️⃣7️⃣🔤5️⃣🔽🔽 【通道名称】：支付宝纯原生 【通道编码】：890 【固定金额】：30-90 费率1️⃣7️⃣🔤5️⃣🔽🔽
【通道名称】： 微信京东游戏 【通道编码】：783 【通道金额】：50-1000（整百） 费率2️⃣🔤5️⃣🔽🔽🔽 【通道名称】：支付宝AA原生 【通道编码】：804 【通道限额】：300|400 费率1️⃣3️⃣🔤3️⃣🔽🔽🔽 【通道名称】：支付宝小芒 【通道编码】：819 【固定金额】： 100 200 费率1️⃣7️⃣🔤1️⃣🔼🔼🔼
【通道名称】：支付宝固额40 【通道编码】：823 【固定金额】：40 固额 费率1️⃣7️⃣ 肯德基 🚌🚌
【810】支付宝个码原生 100-500 先切 先切要等白天来码子了❌❌❌❌
【通道名称】：永辉 整数 【通道编码】：992 【固定金额】：20-100 费率1️⃣7️⃣🔤8️⃣
【通道名称】：微信小额原生双端 （高成率） 【通道编码】： 785 【通道金额】： 1- 9 费率2️⃣3️⃣🔤3️⃣🔽🔽🔽🔽 【通道名称】：支付宝纯原生 【通道编码】：999 【固定金额】：100 200 费率1️⃣7️⃣🔤9️⃣🔼🔼🔼 【通道名称】：支付宝纯固额原生 【通道编码】：822 【固定金额】： 50 费率1️⃣7️⃣🔤9️⃣🔼🔼🔼 【通道名称】：支付宝纯原生 【通道编码】：890 【固定金额】：30-90 费率1️⃣7️⃣🔤9️⃣🔼🔼🔼 原生涨回来了 神经码商搞事情
【通道名称】：微信小额原生双端 （高成率） 【通道编码】： 785 【通道金额】： 1- 9 费率2️⃣3️⃣🔤3️⃣🔼🔼🔼 这条为主哈 上条发错了
【通道名称】：微信小额原生双端 （高成率） 【通道编码】： 785 【通道金额】： 1- 9 费率2️⃣3️⃣🔽🔽🔽🔽 【通道名称】：支付宝纯原生 【通道编码】：999 【固定金额】：100 200 费率8️⃣🔽🔽 【通道名称】：支付宝纯固额原生 【通道编码】：822 【固定金额】： 50 费率8️⃣🔽🔽 【通道名称】：支付宝纯原生 【通道编码】：890 【固定金额】：30-90 费率8️⃣🔽🔽
【通道名称】：支付宝纯原生 【通道编码】：999 【固定金额】：100 200 费率1️⃣6️⃣🔤3️⃣🔽🔽 【通道名称】：支付宝纯固额原生 【通道编码】：822 【固定金额】： 50 费率1️⃣2️⃣🔽🔽 【通道名称】：支付宝纯原生 【通道编码】：890 【固定金额】：30-90 费率1️⃣2️⃣🔽🔽
【通道名称】：支付宝纯原生 【通道编码】：999 【固定金额】：100 200 费率1️⃣7️⃣🔽🔽 【通道名称】：支付宝纯固额原生 【通道编码】：822 【固定金额】： 50 费率1️⃣7️⃣🔤5️⃣🔽🔽 【通道名称】：支付宝纯原生 【通道编码】：890 【固定金额】：30-90 费率1️⃣7️⃣🔤5️⃣🔽🔽 【通道名称】：支付宝代付 【通道编码】： 922 【固定金额】：50 费率1️⃣7️⃣🔽🔽
【通道名称】：支付宝GMM 【通道编码】：841 【通道金额】：300-450 费率1️⃣5️⃣🔤5️⃣🔼🔼🔼 【通道名称】：支付宝纯原 【通道编码】：662 【固定金额】： 100 200 费率1️⃣7️⃣🔤3️⃣🔽🔽🔽 原生 【通道名称】：支付宝纯原生 【通道编码】：999 【固定金额】：100 200 费率1️⃣7️⃣🔤3️⃣🔽🔽🔽
Showing the 12 most recent of 20 posts we hold for @hengan88888888. 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.
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.
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 11 October 2026 — this entry's latest reading, not the date you are reading this.
“恒安支付通知频道群” (@hengan88888888), 1,114 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/hengan88888888.
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.