Channel
@m416kernel
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
4,239subscribers
+153 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1004302158145 |
|---|---|
| Type | Channel |
| Username | @m416kernel |
| Created | Between 1 June 2026 and 19 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 11 August 2026 |
| On Telegram | t.me/m416kernel |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 07:23 | 4,239 | +142 |
| 8 Aug 2026, 07:52 | 4,097 | +11 |
| 7 Aug 2026, 14:46 | 4,086 | first reading |
19 posts held, back to 19 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 4 pagesof 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. It is computed over the 4 of 16 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 8 August 2026 |
|---|---|
| Posts held | 19 (19 July 2026 – 8 August 2026) |
| Views total | 42,383 |
| Reactions total | 121 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 12: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.
Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
121 reactions across 4 posts, in 9 distinct kinds. The most used accounts for 52.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 64 | 52.9% | |
| ❤ | 31 | 25.6% | |
| 🥰 | 10 | 8.26% | |
| 👏 | 5 | 4.13% | |
| ❤🔥 | 3 | 2.48% | |
| 🔥 | 3 | 2.48% | |
| 😱 | 2 | 1.65% | |
| 🤓 | 2 | 1.65% | |
| 😁 | 1 | 0.826% |
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 4 of the 19 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 121reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 19 July 2026 to 8 August 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.
新版本的快更新了 关于防举报我在作个解释 你在开始对局的时候 蓝洞会从主服务器给你当前的对局开一个战斗服务器 你被举报的流程是先走蓝洞主服务器 再回调到战斗服务器 因为举报受到的检测全部由战斗服务器启动ioctl检测线程 走蓝洞主服务器下发的安全期冻结什么的 是被动的 真正的系统检测是从战斗服务器启动的 防举报就是不让战斗服务器对你的账号进行检测 点点表情加快发布
❤28👍11👏2🤓2😱2🥰1
Signed 雪饼 （直奔主题）
卡密验证出现了一点小问题 正在修复中 偷偷给你们透露点东西 可能会直接推送1.3版本 点点表情 我们加快修复速度 顺便让我看看有多少玩家在等待
👍53🥰7❤3❤🔥3👏3
Signed 冷清
我在这里回复一下一些问题 ①他妈的加不加广角 加不加美化 我他妈不加 加了这些东西就是早晚拉闸 单绘制自瞄就是可以演戏稳定战神 场均杀7~12个上不了你来找我 m4的宗旨就是为了给那些没有root也想上战神的人的人用的 ②上下滑动ui的时候会偶现bug 那就是他妈的不小心开了一些功能或者关了一些功能 你重新点就是了 婴儿别玩m416 感谢 ③为什么一把打完就闪退？那是因为我连接了自动反馈功能 每一把打完实际你的截图就自动发到我这里来了 目前没有什么解决方案 也许我会在下个版本v1.3.0取消自动反馈就不会一把一闪了 其余没有什么逼事我也就不说了
🔥3🥰2
Signed 𝐾𝑖𝑛𝑔 IP 中国上海
🌟免费卡密已激活→ m416king 10000设备 永不到期卡密 适用于全球日韩越南台湾四服 反馈发送至 @fzdzking *各个m4将军尽情地疯狂踩踏pubg的检测吧
😁1
Signed 𝐾𝑖𝑛𝑔 IP 中国上海
退出m4了拜拜大家 希望日后的日子里你们还能记得我
Signed 雪饼 （直奔主题）
➡️M416-PUBGM通知 ➡️v1.3.0版本至臻版本更新同步发布免费卡密延长至3天 10000设备 🟢M416-和平精英通知 🟢将开放双版本 一个版本为稳定性优先 一个版本为全火暴力版本 内置不拉回加速一键拾取超体火箭超级飞等功能 PUBGM: @m416kernel 和平精英: @m416loader
Posted without readable text
Photo, posted without a caption
Photo, posted without a caption
🔴m4至臻v1.2.0版本新添一位战神 免费福利激励月卡已送出~ 🌟更多反馈查看 - @m416feedback
Photo, posted without a caption
你们天天领卡密 我们也需要生活赚钱的 我们的总负责人在上海留学所以说经济压力很大😂 没有义务一辈子为你们无偿付出 🙂领完卡密 24小时内禁止再次领取 ⚠️3 CNY几乎都是市场价你们不想买的可以不买
Showing the 12 most recent of 19 posts we hold for @m416kernel. 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 — 997,139 of 1,160,990entries 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.
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 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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“M416-PUBGM直装通知频道” (@m416kernel), 4,239 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/m416kernel.
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.