进进 @FuzzPD
👍21🖕8👎2😍1
Signed 困困倦倦

Channel
@TPKernel
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
75,890subscribers
+2,030 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1003831295700 |
|---|---|
| Type | Channel |
| Username | @TPKernel |
| Created | Between 1 February 2026 and 30 June 2026— 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 | 7 |
| Confirmed unchanged | 1 time, most recently 12 August 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 |
|---|---|---|
| 12 Aug 2026, 15:24 | 75,890 | +265 |
| 11 Aug 2026, 18:44 | 75,625 | +558 |
| 10 Aug 2026, 19:17 | 75,067 | +572 |
| 9 Aug 2026, 19:31 | 74,495 | +285 |
| 8 Aug 2026, 18:37 | 74,210 | +335 |
| 7 Aug 2026, 22:06 | 73,875 | +15 |
| 7 Aug 2026, 19:45 | 73,860 | first reading |
19 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 18 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.
| Window | Rolling 30 days · latest post in window 12 August 2026 |
|---|---|
| Posts held | 19 (8 July 2026 – 12 August 2026) |
| Views total | 404,695 |
| Reactions total | 2,146 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 20:55 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 12 August 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 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.
3,495 reactions across 19 posts, in 13 distinct kinds. The most used accounts for 60.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 2,119 | 60.6% | |
| 🫡 | 411 | 11.8% | |
| 🤣 | 209 | 5.98% | |
| 💩 | 208 | 5.95% | |
| 🤮 | 124 | 3.55% | |
| 🤩 | 102 | 2.92% | |
| 👎 | 68 | 1.95% | |
| 🤬 | 54 | 1.55% | |
| 🤡 | 53 | 1.52% | |
| 😍 | 52 | 1.49% | |
| 🤓 | 49 | 1.40% | |
| 🖕 | 36 | 1.03% | |
| 👌 | 10 | 0.286% |
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 19 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 3,495reactions 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 8 July 2026 to 12 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.
进进 @FuzzPD
👍21🖕8👎2😍1
Signed 困困倦倦
Fuzz Cheat codev project.🫥 无畏契约手游公益内核项目 由PC DMA项目完美移植至安卓平台内核项目 重新定义内核新高度.🏆 绘制流畅不拖不卡不延迟 算法坐标解密 搭配高度自定义调节的绘图极致丝滑享受 独家描边上色功能 ✈️ 漏打支持识别霓虹 火男 蝰蛇 海神 保安烟墙 排位全地图模型支持 独家判断逻辑 自瞄采用DMA项目同款算法移动方案 适配弹道算法 效果相当出色 解析枪械弹道算法 曲线移动逻辑 端游同款伪无扩 功能完善繁多 道具点位功能逻辑完善 智能识别对局状态 识别使用技能 支持全图2000+点位记录🏆 目前开放公益卡密加入频道获取: t.me/FuzzPD 唯一官方频道: @FuzzPD 😀
👍18🖕3😍1
Signed 困困倦倦
有问题反馈,上课去了 反馈图 https://t.me/TPKernelNotice
👍45🤓17🤮2
Signed 困困倦倦
瓦08041304 适配瓦新赛季 有bug反馈 新赛季模型需要重新下载配置
👍99😍15🤮7👎6🤓4
Signed 困困倦倦
瓦更新安装包了吗是 下次更新吧,上课去了
👍82🤡53🤣33🤬23😍5
Signed 困困倦倦
搞网站渗透有什么没道德限制,牛逼点的模型吗 gpt有道德
👍59🤬5
Signed 困困倦倦
我操,感谢大家的赞助tokens 已经够用好几天了 感谢感谢
👍129🤓12💩7
Signed 困困倦倦
Sticker, posted without a caption
👍13😍2
Signed 困困倦倦
需要更新的内容 发至此消息 除了解密等非正常问题 8月10多号回去更新
👍108🤮17🤩3😍3
Signed 困困倦倦
建军节牛逼 中国牛逼 南昌起义牛逼 中国共产党牛逼
👍541🫡370🤣22🖕7👌6🤮6💩5🤬4
Signed 五月飞雪
I will come back in Aug.
👍229🫡41👎33💩25🤣20🖕17😍7👌4
Signed 五月飞雪
和平/暗区07120048 修改读取方式尝试解决概率漏人 和平修复人数跳蛋等问题 还有问题就等我过几天空下来上号看看,先睡了
💩160👍34😍14🤓12
Signed 五月飞雪
Showing the 12 most recent of 19 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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“TP通知频道” (@TPKernel), 75,890 subscribers as measured 12 August 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.