反馈建议机器人 @TPkernel_FKbot 有时间会看的
👍95🖕2
Signed 五月飞雪

Channel
@TPKernel
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Citations · Cite this entry
106,440subscribers
+32,580 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
| Telegram ID | -1003831295700 |
|---|---|
| Type | Channel |
| Username | @TPKernel |
| Created | Between 1 February 2026 and 8 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 October 2026 |
| Measurements held | 38 |
| Confirmed unchanged | 1 time, most recently 14 October 2026 |
| On Telegram | t.me/TPKernel |
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 10 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Oct 2026, 15:06 | 106,440 | +484 |
| 13 Oct 2026, 02:28 | 105,956 | +1,268 |
| 8 Oct 2026, 20:18 | 104,688 | +2,342 |
| 4 Oct 2026, 07:56 | 102,346 | +4,794 |
| 25 Sept 2026, 14:55 | 97,552 | +7,616 |
| 19 Sept 2026, 00:00 | 89,936 | +533 |
| 16 Sept 2026, 13:55 | 89,403 | +309 |
| 14 Sept 2026, 16:17 | 89,094 | +560 |
| 13 Sept 2026, 03:21 | 88,534 | +1,188 |
| 11 Sept 2026, 03:58 | 87,346 | +729 |
| 8 Sept 2026, 06:39 | 86,617 | +1,543 |
| 5 Sept 2026, 02:41 | 85,074 | +546 |
| 3 Sept 2026, 09:55 | 84,528 | +436 |
| 2 Sept 2026, 04:26 | 84,092 | +254 |
| 1 Sept 2026, 03:04 | 83,838 | +332 |
| 30 Aug 2026, 22:57 | 83,506 | +475 |
| 29 Aug 2026, 20:24 | 83,031 | +603 |
| 28 Aug 2026, 21:56 | 82,428 | +435 |
| 27 Aug 2026, 19:23 | 81,993 | +457 |
| 26 Aug 2026, 17:08 | 81,536 | first reading |
250 posts held, back to 8 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 147 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 15 October 2026 |
|---|---|
| Posts held | 250 (8 July 2026 – 15 October 2026) |
| Views total | 2,212,334 |
| Reactions total | 18,007 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 15 Oct 2026, 07:42 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 15 October 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.
Measured directly from 30 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.
31,256 reactions across 250 posts, in 13 distinct kinds. The most used accounts for 77.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 24,118 | 77.2% | |
| 🤣 | 1,321 | 4.23% | |
| 🫡 | 1,126 | 3.60% | |
| 🤬 | 1,018 | 3.26% | |
| 💩 | 854 | 2.73% | |
| 👎 | 524 | 1.68% | |
| 🤮 | 508 | 1.63% | |
| 🤓 | 362 | 1.16% | |
| 🤡 | 361 | 1.15% | |
| 😍 | 355 | 1.14% | |
| 🤩 | 325 | 1.04% | |
| 🖕 | 289 | 0.925% | |
| 👌 | 95 | 0.304% |
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 250 of the 250 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 31,256 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 250 most recent posts we hold, published 8 July 2026 to 15 October 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @TPKernel. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 250 most recent posts we hold for this entry, published 8 July 2026 to 15 October 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
反馈建议机器人 @TPkernel_FKbot 有时间会看的
👍95🖕2
Signed 五月飞雪
🔷 三角洲公益解密辅助 - 命运 支持ROOT/免ROOT 首发免ROOT绘制 算法解密无视加密 支持三服 功能全面 顶级绘图媲美收费项目 免费网页雷达 无需自购服务器 独家自适应自瞄算法 枪枪到肉 ✅独家驱动 ✅漏打自瞄 ✅算法解密 ROOT模式就是正常的内核辅助 免ROOT支持绘制和雷达两种模式 通过解析网络数据包提取数据 不读取/修改任何内存 支持2D/3D雷达 全彩模型 只要你的设备能联网即可使用 ❤️ 公益频道:@fatedfm ❤️ 交流群组:@fatedfmchat
👍92🤩1
Signed 五月飞雪
暗区10142204 修复自瞄部位选择不够空间 驱动频道 @ZeroPd
👍137😍3🤩1
Signed 五月飞雪
🔷 三角洲公益解密辅助 - 命运 支持ROOT/免ROOT 首发免ROOT绘制 算法解密无视加密 支持三服 功能全面 顶级绘图媲美收费项目 免费网页雷达 无需自购服务器 独家自适应自瞄算法 枪枪到肉 ✅独家驱动 ✅漏打自瞄 ✅算法解密 ROOT模式就是正常的内核辅助 免ROOT支持绘制和雷达两种模式 通过解析网络数据包提取数据 不读取/修改任何内存 支持2D/3D雷达 全彩模型 只要你的设备能联网即可使用 ❤️ 公益频道:@fatedfm ❤️ 交流群组:@fatedfmchat
👍120
Signed 五月飞雪
6.3.1不强制更新修复平板卡片异常大
👍133🖕2
Signed 五月飞雪
apk6.3 大幅更新apk动画体验感受 瓦10141904 更新自动对齐小地图雷达,首次进入地图需要等待一会儿 暗区10141602 更新倒地不瞄,更新夜视仪绘制 驱动频道 @ZeroPd
👍113🤩6
Signed 五月飞雪
现在新机子不能秒解锁了吗,那不白买了
👍119💩5👎1
Signed 五月飞雪
@ZERO_Driver @ZeroPd 驱动频道都进进
👍91🤩2
Signed 五月飞雪
🎮 662首发王者免ROOT雷达 ✅不需要ROOT ✅不需要刷入任何东西 ✅只要你的设备可以联网 ✅支持安卓 鸿蒙 IOS 全程0读取/写入内存 稳定性和你不开一模一样 支持人物 野怪 兵线 防御塔等绘制 无视加密 无视加密 无视加密! 原工作室某项目 因单价过低工作室倒闭 现免费公益给大家使用 ❤️ 公益频道认准:@radar662
👍49
Signed 五月飞雪
租车是一嗨好还是神州好 哈啰坑了我600块
👍131🤣3👎2😍1
Signed 五月飞雪
你累你*
👍92🤬3🤓2
Signed 二月 飞雪
我很累了,以后应该不更新瓦解密了 然后哪天有空再更新维护这个项目吧
👍216🤣51👎21🫡17🖕15🤡15💩14
Signed 五月飞雪
Showing the 12 most recent of 250 posts we hold for @TPKernel. 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.
@TPKernel edited 9 posts 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.
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 14 October 2026 — this entry's latest reading, not the date you are reading this.
“TP通知频道<有问题置顶找解决>” (@TPKernel), 106,440 subscribers as measured 14 October 2026. Telegram Register, tgregister.com/channel/TPKernel.
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.