Telegram RegisterThe public register of Telegram
Telegram profile photo for 黑网联盟@Heiwang

Channel

黑网联盟@Heiwang

@heiwang

On this record: Growth · Engagement · Posts · Citations · Cite this entry

4,088subscribers

+3,491 since we began measuring on 13 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001170741558
TypeChannel
Username@heiwang
CreatedBetween 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live26 August 2026
Measurements held6
Confirmed unchanged1 time, most recently 26 August 2026
On Telegramt.me/heiwang

Growth

5974,0882,342.513 August 2026 — 597 subscribers14 August 2026 — 4,073 subscribers17 August 2026 — 4,077 subscribers20 August 2026 — 4,079 subscribers23 August 2026 — 4,086 subscribers26 August 2026 — 4,088 subscribers13 August 202626 August 2026
6 measurements spanning 13 days, net +3,491. 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 73–4,612 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
26 Aug 2026, 23:234,088+2
23 Aug 2026, 20:334,086+7
20 Aug 2026, 09:424,079+2
17 Aug 2026, 18:394,077+4
14 Aug 2026, 20:164,073+3,476
13 Aug 2026, 15:17597first reading

Engagement

4 posts held, back to 13 August 2026the 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.

ERR · 30 days
92.4%
avg views ÷ 4,088 subscribers
Avg views / post
3,780
4 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
4
of 4 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 13 August 2026
Posts held4 (13 August 202613 August 2026)
Views total15,111
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 15:17 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.

Recent posts

13 Aug 2026, 15:07 UTC7 viewsread 13 August 2026
Photo

#黑盘曝光 #黑网联盟 #金宝娱乐城赢钱就卡审核 只让充值不让提! 已在赌博网址举报渠道、国家反诈中心、12377递交全部证据,绝不撤案,绝不和解! 八年累计亏损2000万,新账号再亏200万,从未提现。申请30万本金出款,平台直接吞没余额、锁死账号,所有关联账号一并封禁,纯粹黑吃黑杀猪盘。核心管理人龙大圣,老牌黑产资金盘分子,反诈漏网之鱼。出事之后客服推诿甩锅,管理层直接装死失联。警告所有为该盘供血的USDT、支付资金通道:若继续为该杀猪盘提供服务,我会把你们全部扒出,全套证据移交执法机关,连带曝光追责! 不计一切代价死磕到底!紧盯盘口老板、管理人员、整条资金链路,持续举报曝光,不铲除这颗毒瘤绝不罢休! 免费收录/黑盘曝光.@sbsb 关注黑盘联盟.@heipan 关注黑网联盟.@heiwang 黑网联盟口号一次不忠.终身不用 欢迎踊跃投稿曝光黑网,只要真实,一经采纳稿费到位18-188U不等

13 Aug 2026, 14:45 UTC≈13,900 viewsread 13 August 2026
Photo

#黑盘曝光 #黑网联盟 #6600彩娱乐 赢钱就卡审核 只让充值不让提! 老玩家长期正常存取,近期赢钱申请提现,却遭连日拖延、审核没完没了!平台反复劝说 “多玩再提”,始终拒绝出款 —— 摆明平时小额放饵、赢钱立刻黑款,只进不出! 免费收录/黑盘曝光.@sbsb 关注黑盘联盟.@heipan 关注黑网联盟.@heiwang 欢迎踊跃投稿曝光黑网,只要真实,一经采纳稿费到位18-188U不等

13 Aug 2026, 14:44 UTC602 viewsread 13 August 2026
Photo

#黑盘曝光 #黑网联盟 #6600彩娱乐 赢钱就卡审核 只让充值不让提! 老玩家长期正常存取,近期赢钱申请提现,却遭连日拖延、审核没完没了!平台反复劝说 “多玩再提”,始终拒绝出款 —— 摆明平时小额放饵、赢钱立刻黑款,只进不出! 免费收录/黑台曝光.@sbsb 关注黑盘联盟.@heipan 关注黑网联盟.@heiwang 欢迎踊跃投稿曝光黑网,只要真实,一经采纳稿费到位18-188U不等

13 Aug 2026, 14:43 UTC602 viewsread 13 August 2026
Photo

#黑盘曝光 #黑网联盟 #6600彩娱乐 赢钱就卡审核 只让充值不让提! 老玩家长期正常存取,近期赢钱申请提现,却遭连日拖延、审核没完没了!平台反复劝说 “多玩再提”,始终拒绝出款 —— 摆明平时小额放饵、赢钱立刻黑款,只进不出! 免费收录/黑台曝光.@sbsb 关注黑网联盟.@heiwang 欢迎踊跃投稿曝光黑网,只要真实,一经采纳稿费到位18-188U不等

Showing the 4 most recent of 4 posts we hold for @heiwang. 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 — 68,879 of 1,621,120entries 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 13 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 26 August 2026 — this entry's latest reading, not the date you are reading this.

“黑网联盟@Heiwang” (@heiwang), 4,088 subscribers as measured 26 August 2026. Telegram Register, tgregister.com/channel/heiwang.

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.