🌟芒果官方消息 PUBG MOBILE 4.7 重磅来袭 👍全新赛季迎接全新的你 💎芒果官方频道 @MGBJH6
👍14

Channel
@MGBJH6
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
4,249subscribers
+552 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002656303912 |
|---|---|
| Type | Channel |
| Usernames | @BLZHNB @MGBJH6 |
| Description | “莫叹少年资历浅,他日凌霄震九天” |
| Created | 2 May 2025 — measured — dated from the channel’s first post |
| First recorded | 8 August 2026 |
| Last confirmed live | 11 November 2026 |
| Measurements held | 20 |
| On Telegram | t.me/MGBJH6 |
Giveaways & airdrops — 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 13 September 2026 and assigned it the closest of 31 fixed categories, at 73% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Nov 2026, 18:22 | 4,249 | no change |
| 11 Nov 2026, 17:47 | 4,249 | +4,248 |
| 2 Nov 2026, 06:58 | 1 | -3,907 |
| 30 Oct 2026, 09:28 | 3,908 | -20 |
| 27 Oct 2026, 02:54 | 3,928 | -27 |
| 23 Oct 2026, 21:38 | 3,955 | -16 |
| 21 Oct 2026, 01:40 | 3,971 | -18 |
| 17 Oct 2026, 17:06 | 3,989 | -19 |
| 14 Oct 2026, 09:16 | 4,008 | -424 |
| 8 Sept 2026, 13:20 | 4,432 | -51 |
| 3 Sept 2026, 02:03 | 4,483 | -4 |
| 31 Aug 2026, 01:57 | 4,487 | -9 |
| 28 Aug 2026, 11:04 | 4,496 | -20 |
| 25 Aug 2026, 04:14 | 4,516 | +89 |
| 21 Aug 2026, 19:09 | 4,427 | +121 |
| 18 Aug 2026, 10:05 | 4,306 | +175 |
| 15 Aug 2026, 17:27 | 4,131 | +227 |
| 12 Aug 2026, 07:42 | 3,904 | +188 |
| 8 Aug 2026, 22:11 | 3,716 | +19 |
| 8 Aug 2026, 07:47 | 3,697 | first reading |
32 posts held, back to 2 May 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages of Telegram’s post history, 20 posts per page.
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 11 November 2026 |
|---|---|
| Posts held | 32 (2 May 2025 – 11 November 2026) |
| Views total | 9,753 |
| Reactions total | 198 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Nov 2026, 18:22 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.
Lifetime counters from Telegram’s own channel header, read 11 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
990 reactions across 30 posts, in 16 distinct kinds. The most used accounts for 35.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 347 | 35.1% | |
| ❤ | 198 | 20.0% | |
| 🤩 | 97 | 9.80% | |
| 🔥 | 82 | 8.28% | |
| 🎉 | 74 | 7.47% | |
| 👏 | 71 | 7.17% | |
| 🥰 | 68 | 6.87% | |
| 💋 | 10 | 1.01% | |
| 🤣 | 9 | 0.909% | |
| 🖕 | 7 | 0.707% | |
| 🤮 | 7 | 0.707% | |
| 😁 | 6 | 0.606% | |
| 💩 | 4 | 0.404% | |
| 😨 | 4 | 0.404% | |
| 🤓 | 3 | 0.303% | |
| 🤔 | 3 | 0.303% |
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 30 of the 32 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 990 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 32 most recent posts we hold, published 2 May 2025 to 11 November 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.
Telegram’s own ‘edited’ marker: 4 of 12 posts held from the last 30 days (33.3%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
🌟芒果官方消息 PUBG MOBILE 4.7 重磅来袭 👍全新赛季迎接全新的你 💎芒果官方频道 @MGBJH6
👍14
上古真神葫芦侠Pro【速刷】 葫芦侠独家功能: 刷流量 刷话费 刷各种平台会员 全面更新 可刷一切 📱快手区:播放量 点赞 关注 评论 📱抖音区:播放量 点赞 关注 评论 📱QQ区:名片赞 说说赞 ⚠️游戏区:和平 蛋仔 无畏契约王者 三角洲 火影 均可刷点券 有更多功能自己下载体验 🔥其他黑科技:伪装机型 刷qq会员 跳卡网支付 ai脱衣 刷话费等等✅ 网盘下载链接点击下载 密码123456 一次性费用购买后真无限使用 软件已对接36000个不同ip账号 欢迎各位老板前来使用 请勿用与非法途径!!! 点击加入官方频道
👍8
Signed 普通(全网收管理)
库存大量补了
👍15
目前库存充足各位老板抓紧拿下✅
👍29
@MGBJH1 副频道,加入备用
👍8❤1
广告位联系我 @laodi811 普通广告位25一周 黑灰广告位35一周 置顶广告位45一周 直装/全防/半火/文件/内核都可以 💎频道链接 https://t.me/MGBJH6 🥰所有广告与本频道无关‼️
👍17❤2🤣2💩1
@MGBJH1 副频道,加入备用
👍16
📱快手发布关于芒果8级号的作品,并带此频道可获取8级号 点我联系客服审核领取8级号
👍21
卡网目前有高等级的苹果ID账号,也有普通的扫码8级号,大家可以自行选择
👍14
大量招收代理入驻,享受最低价拿号,进入我们的卡网一键入驻即可✅
👍16😁1
卡网价格现在为一块
👍16❤1
芒果八级号,质量有保障
👍13💩3
Showing the 12 most recent of 32 posts we hold for @MGBJH6. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 2 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.
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.
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 November 2026 — this entry's latest reading, not the date you are reading this.
“芒果八级号” (@MGBJH6), 4,249 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/MGBJH6.
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.