维护结束✔️

Channel
轰炸社区
@hongzha7788
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
113,216subscribers
+151 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
Register entry
| Telegram ID | -1002288208730 |
|---|---|
| Type | Channel |
| Username | @hongzha7788 |
| Created | Between 1 September 2024 and 10 October 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/hongzha7788 |
Topic
Hacking & security — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 9 August 2026 and assigned it the closest of 31 fixed categories, at 83% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 23:55 | 113,216 | +70 |
| 12 Aug 2026, 02:33 | 113,146 | +22 |
| 11 Aug 2026, 02:27 | 113,124 | -14 |
| 10 Aug 2026, 00:47 | 113,138 | +5 |
| 9 Aug 2026, 02:52 | 113,133 | +39 |
| 7 Aug 2026, 23:51 | 113,094 | +29 |
| 7 Aug 2026, 17:15 | 113,065 | no change |
| 7 Aug 2026, 17:06 | 113,065 | first reading |
Engagement
22 posts held, back to 10 October 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 15 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 8.45%
- avg views ÷ 113,216 subscribers
- Avg views / post
- 9,570
- 3 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 3
- of 22 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.
| Window | Rolling 30 days · latest post in window 10 August 2026 |
|---|---|
| Posts held | 22 (10 October 2024 – 10 August 2026) |
| Views total | 28,710 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 18:25 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
紧急维护,耐心等待⌛️
由于最近三天,服务器一直存在网络波动,导致比较多的轰炸没有实际生效,在此对大家说声抱歉。 并且我方将最近三天的所有轰炸,包括加强轰炸、定时短信轰炸、短信轰炸。都按照1.5倍积分返还。(最高轰炸6000积分,返还9000积分) 目前已经全部退回,您可以对机器人发送 /my查询您的当前积分。
人民币充值系统已经修复,感谢大家一直以来的支持🙏
充值系统已经修复,感谢大家一直以来的支持🙏
恢复
紧急修复中
轰炸社区 pinned «推荐使用🤖️点击下方蓝色字体使用 ⬇️⬇️⬇️⬇️ 暗精灵社工库 暗精灵社工库 暗精灵社工库»
推荐使用🤖️点击下方蓝色字体使用 ⬇️⬇️⬇️⬇️ 暗精灵社工库 暗精灵社工库 暗精灵社工库
停机维护中
微信支付宝充值支付通道已经恢复正常~ 再次感谢各位用户赞助支持我们❤️
恢复正常
Showing the 12 most recent of 22 posts we hold for @hongzha7788. 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.
Mentions
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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“轰炸社区” (@hongzha7788), 113,216 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/hongzha7788.
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.