#频道互推 #相似推荐 ------------------------------ 📢 三角洲MAN官方群 📢 三角洲KG官方群 📢 安卓黄油 黄油联盟 📢 小月公益直装内核和平&PUBG&三角洲 📢 【黄油】PC电脑单机游戏 📢 安卓【黄油】手机游戏 📢 拼多多数据号 📢 小秋 三角洲 ChatGPT内部 官方 📢 iOS-T1/失控进化iOS/项目开发/卡密低价货源批发 📢 三国演义官方频道认准客服 @DQYYDSDQ ------------------------------ ☁️ 互推入口:@sooo

Channel
转转数据号『低价号源』
@HERONB88
On this record: Topic · Growth · Engagement · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
13,441subscribers
-9,840 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1003817118574 |
|---|---|
| Type | Channel |
| Username | @HERONB88 |
| Created | Between 1 February 2026 and 24 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 34 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/HERONB88 |
Topic
Gaming — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 81% 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 |
|---|---|---|
| 17 Sept 2026, 08:36 | 13,441 | -278 |
| 15 Sept 2026, 10:59 | 13,719 | -539 |
| 13 Sept 2026, 19:01 | 14,258 | -672 |
| 12 Sept 2026, 00:19 | 14,930 | -570 |
| 9 Sept 2026, 13:59 | 15,500 | -865 |
| 6 Sept 2026, 06:39 | 16,365 | -337 |
| 4 Sept 2026, 03:57 | 16,702 | -211 |
| 2 Sept 2026, 17:34 | 16,913 | -272 |
| 1 Sept 2026, 14:25 | 17,185 | -137 |
| 31 Aug 2026, 15:44 | 17,322 | -16 |
| 30 Aug 2026, 17:05 | 17,338 | -241 |
| 29 Aug 2026, 15:08 | 17,579 | -350 |
| 28 Aug 2026, 11:43 | 17,929 | -106 |
| 27 Aug 2026, 10:29 | 18,035 | -155 |
| 26 Aug 2026, 07:57 | 18,190 | -277 |
| 25 Aug 2026, 10:17 | 18,467 | -252 |
| 24 Aug 2026, 12:47 | 18,719 | -366 |
| 22 Aug 2026, 19:47 | 19,085 | -317 |
| 21 Aug 2026, 10:07 | 19,402 | -172 |
| 20 Aug 2026, 11:13 | 19,574 | first reading |
Engagement
34 posts held, back to 24 July 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 63 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 4.47%
- avg views ÷ 13,441 subscribers
- Avg views / post
- 600
- 16 posts measured
- Reaction rate
- 0.898%
- reactions ÷ views · ER floor
- Posts in window
- 16
- of 34 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. It is computed over the 15 of 16 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 2 September 2026 |
|---|---|
| Posts held | 34 (24 July 2026 – 2 September 2026) |
| Views total | 9,604 |
| Reactions total | 86 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 09:35 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.
Reaction mix
144 reactions across 30 posts, in 14 distinct kinds. The most used accounts for 48.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 70 | 48.6% | |
| ❤ | 20 | 13.9% | |
| 🤮 | 18 | 12.5% | |
| 🥰 | 7 | 4.86% | |
| 💔 | 6 | 4.17% | |
| 🤣 | 5 | 3.47% | |
| 👏 | 3 | 2.08% | |
| 😁 | 3 | 2.08% | |
| 😍 | 3 | 2.08% | |
| 😭 | 3 | 2.08% | |
| 😢 | 2 | 1.39% | |
| 🤷♀ | 2 | 1.39% | |
| 😨 | 1 | 0.694% | |
| 🤓 | 1 | 0.694% |
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 32 of the 34 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 144 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 34 most recent posts we hold, published 24 July 2026 to 2 September 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
#频道互推 #相似推荐 ------------------------------ 📢 失约PUBGm美化频道(有用消息在上面) 📢 菠菜三角洲低价货源站 📢 失控进化QAQ(安卓/pc/dma/ios) 📢 小米科技-失控进化直装 root pc 📢 冰雪泛滥文件主频道🇨🇳 📢 丽江吃鸡 📢 COCO(XBOX已跑路) 📢 📊 体育情报局|足球⚽ NBA🏀 MLB⚾ 📢 (南宫集团)爆奖投稿 📢 三角洲/CS2/无畏契约/穿越火线CF ------------------------------ ☁️ 互推入口:@soso
👍1
全网唯一一家以质量和口碑好评的数据号『认准转转』😒
💔2👍1
卡网已上架『无畏契约』数据号 可放心购买低价靠谱 ❤️铂金🎚钻石🎚超凡👍神话
🤷♀2
全网唯一一家以质量和口碑好评的数据号『认准转转』😒
👍3❤1💔1
⚠️卡网已全面升级维护, 可以放心下单客服24小时都在 弥补大家所有账号买二送一 👋下单卡网 https://luoye.yjsfk.cn/shop/LQ2XVETA
👍5💔1
手枪号依旧极品,库存少,先到先得
👍5🤓1
📱卡网已上架纸飞机✈️账号『高质量』 ‼️卡密使用方法,前面的为账号 后面的为接码,复制浏览器收验证码就可以,2级密码为123123 🥰下单链接 https://luoye.yjsfk.cn/shop/LQ2XVETA
👍2❤1💔1
😙卡网已上架手枪/传世武器装备号 『每号保底一把』数量有限先到先得
👍6
全网唯一一家以质量和口碑好评的数据号『认准转转』🥰
👍4
卡网已最新补货,可以放心下单 ☑️数据号☑️直登号☑️退游号☑️授权号 客服一直都在线回复售后 @NIMEIPY 🥰购买链接 https://luoye.yjsfk.cn/shop/LQ2XVETA
👍5😨1
全网唯一一家以质量和口碑好评的数据号『认准转转』🎈
👍4🥰3😁2😢2
Showing the 12 most recent of 34 posts we hold for @HERONB88. 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
@HERONB88 edited 1 post 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
- 26 August 2026
- Most recent edit
- 26 August 2026
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
@LMGWJWD · 36,84180 postsBing(有问题先看0714置顶)
@nullnb62 · 20,09834 postsakk的小窝
@XIANHE_CHEAT · 6,70222 posts冷淡魔术快斗官方
@LDGWJ · 10,38820 postsGR频道
@GRPLYYDS · 13,46413 postsSEVEN公益改文件💤
@sevennb1 · 8,33711 posts辞约改文件主频道
@byCY6 · 8,97610 postsLEO内核【APK频道】
@QZMODN · 417 posts幻觉官方频道
@xueluoqingyan · 8,5897 posts北冥和平精英&PUBG《改文件》
@bmgwjnb · 9,5316 postsJS文件主频道
@JSAI866 · 26,0065 postsAS Game 官方频道 🇨🇳
@DSCHEAT8 · 14,1223 posts小九号商频道
@HMXMPD · 2,5363 posts残念泛滥文件
@Longshen666 · 6,4292 posts昔陌官方频道
@XMNB68 · 27,7281 post
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
Named by 20 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.
Named by
Channels on the register whose posts name this channel's handle.
@LMGWJWD · 36,84193 posts北冥和平精英&PUBG《改文件》
@bmgwjnb · 9,53174 posts北冥公益游戏外挂资源破解分享
@bmnb78 · 28,29667 postsBing(有问题先看0714置顶)
@nullnb62 · 20,09837 postsakk的小窝
@XIANHE_CHEAT · 6,70223 postsGR频道
@GRPLYYDS · 13,46422 posts冷淡魔术快斗官方
@LDGWJ · 10,38822 postsSEVEN公益改文件💤
@sevennb1 · 8,33711 posts辞约改文件主频道
@byCY6 · 8,97610 postsJS文件主频道
@JSAI866 · 26,0068 postsLEO内核【APK频道】
@QZMODN · 417 posts幻觉官方频道
@xueluoqingyan · 8,5897 postsAS Game 官方频道 🇨🇳
@DSCHEAT8 · 14,1224 posts残念泛滥文件
@Longshen666 · 6,4294 posts北冥《拦截/注入》主频道
@BMMOK · 6313 posts小九号商频道
@HMXMPD · 2,5363 posts昔陌官方频道
@XMNB68 · 27,7282 posts北冥专业互推集团
@bmhutui · 6391 post辅助内核破解(全游戏PC端游无畏契约和平精英三角洲直装)
@sotsyy · 241,4161 post零龙资源分享(三角形PUBG和平无畏契约王者荣耀)
@xubaiwj · 7,5501 post
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“转转数据号『低价号源』” (@HERONB88), 13,441 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/HERONB88.
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.