已经完成三角洲模拟udp解密,和基础那些检测绕过,稍后更新v1.2版本,王者晚些
👍50❤1

Channel
@ss_00
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Polls · Citations · Cite this entry
133,089subscribers
-6,157 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
| Telegram ID | -1002140646101 |
|---|---|
| Type | Channel |
| Usernames | @by520a @ss_00 |
| Description | 交流群 @BY520y 发布频道@BY_Kernel BY全版本公告声明 开发者不会主动联系你 本系列作品仅供学习研究,使用者的任何行为与应用作者无关,请在24小时内删除本应用 [下载代表同意本协议] 若有侵权违法行为,请联系我删除内容 |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 October 2026 |
| Measurements held | 81 |
| Confirmed unchanged | 1 time, most recently 18 October 2026 |
| On Telegram | t.me/ss_00 |
Other / unclassifiable — 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 9 August 2026 and assigned it the closest of 31 fixed categories, at 39% 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 |
|---|---|---|
| 18 Oct 2026, 00:59 | 133,089 | -44 |
| 17 Oct 2026, 18:50 | 133,133 | +23 |
| 17 Oct 2026, 00:46 | 133,110 | no change |
| 16 Oct 2026, 22:09 | 133,110 | -61 |
| 16 Oct 2026, 00:18 | 133,171 | no change |
| 15 Oct 2026, 21:55 | 133,171 | -106 |
| 15 Oct 2026, 03:40 | 133,277 | -13 |
| 14 Oct 2026, 18:51 | 133,290 | -123 |
| 13 Oct 2026, 20:56 | 133,413 | -27 |
| 13 Oct 2026, 06:47 | 133,440 | -287 |
| 10 Oct 2026, 10:58 | 133,727 | -103 |
| 9 Oct 2026, 03:18 | 133,830 | -346 |
| 6 Oct 2026, 05:38 | 134,176 | -127 |
| 4 Oct 2026, 19:17 | 134,303 | -183 |
| 1 Oct 2026, 04:38 | 134,486 | -257 |
| 27 Sept 2026, 00:21 | 134,743 | -700 |
| 19 Sept 2026, 17:39 | 135,443 | -95 |
| 18 Sept 2026, 10:59 | 135,538 | -94 |
| 17 Sept 2026, 04:57 | 135,632 | -89 |
| 16 Sept 2026, 03:17 | 135,721 | first reading |
472 posts held, back to 11 March 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 156 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 17 October 2026 |
|---|---|
| Posts held | 472 (11 March 2026 – 17 October 2026) |
| Views total | 709,679 |
| Reactions total | 11,962 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 18 Oct 2026, 07:02 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 18 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 48 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.
21,158 reactions across 468 posts, in 33 distinct kinds. The most used accounts for 86.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 18,295 | 86.5% | |
| ❤ | 1,037 | 4.90% | |
| 👏 | 639 | 3.02% | |
| 🎉 | 288 | 1.36% | |
| 🤓 | 136 | 0.643% | |
| ✍ | 105 | 0.496% | |
| 🔥 | 100 | 0.473% | |
| 🌭 | 96 | 0.454% | |
| 🤩 | 73 | 0.345% | |
| 😭 | 61 | 0.288% | |
| 🤨 | 51 | 0.241% | |
| 🕊 | 43 | 0.203% | |
| 🤔 | 36 | 0.17% | |
| 👌 | 34 | 0.161% | |
| 🦄 | 34 | 0.161% | |
| 😍 | 28 | 0.132% | |
| 🫡 | 26 | 0.123% | |
| 🥰 | 17 | 0.08% | |
| 😘 | 11 | 0.052% | |
| 🙏 | 9 | 0.043% | |
| 13 further kinds | 39 | 0.184% |
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 469 of the 472 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 21,158 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 472 most recent posts we hold, published 11 March 2026 to 17 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.
已经完成三角洲模拟udp解密,和基础那些检测绕过,稍后更新v1.2版本,王者晚些
👍50❤1
等一下云更,王者通杀,全体适配解密
👍95❤6
bug反馈,功能失效,驱动适配 @ohno1007
👍99❤1🔥1
🌟 BY Kernel Pro V1.1.6 更新内容如下 -适配王者新加密 点击链接下载最新版本 http://103.43.10.159:8879/downloads/2026101701/by/AImGui 唯一适配驱动 https://pan.quark.cn/s/e639b6845c9a
👍86❤3
https://pan.quark.cn/s/e639b6845c9a 里下载最新驱动,不支持rt,仅bydrive
👍110
🌟 BY Kernel Pro V1.1.5 更新内容如下 1.适配王者新版本+解密 2.和平占用优化,全开50 3.解决拖框问题 4.和平闪框解密更新 点击链接下载最新版本 http://103.43.10.159:8879/downloads/2026101602/by/AImGui
👍105❤1
bug反馈,功能失效,驱动适配 @ohno1007
👍105❤1
Signed ohno
『❤️三角洲/🎮暗区突围双游戏公益算法解密_Kernel_v1.2』 2026年10月16日 三角洲/暗区突围UDP解密,内核镜像抓包,不修改游戏任何内核,解决千人千面加密;不闪框不漏人不遁地;欢迎各位用户免费体验! ✨栖月三角洲/暗区突围公益UDP解密 🎮暗区突围更新内容 - 优化解密延迟 - 加入高价值物资列表显示 - 加入绘制帧率调节 - 加入自瞄范围显示按钮 🐱三角洲/暗区突围目前解密可正常使用。如果出现无效果的情况,请先检查驱动、解密方案及相关设置是否选择正确。 公益频道:@yuenhpdd The best cheat for Delta Force✅ ✨更新时间:2026年10月11日 ✨栖月 Kernel运营团队 🎮推荐一个朋友的三角洲免root网页雷达项目:👉 https://t.me/guitouwy/50
👍102❤5
🎮三角洲软路由网页3D雷达 纯网络路由读取坐标100%不封号无视行为1,3,7各种封号 手机端只需要安装一个加速器即可,不需要电脑,不需要开热点,不需要root权限,纯网络读取 支持安卓,鸿蒙全系统,只要你的设备可以正常联网即可(网络获取坐标),不需root权限,不需要电脑,不需要解bl,手机联网即可绘制 高级物资,3d人物骨骼,2d平面地图,人物职业,头甲包,名字信息,血量状态,全部可以显示,效果堪比内核,并且比内核更加稳定 本地内核绘制全部信息都要在本地游戏内存里面读取,非常容易封号封一天或者三天,甚至十年,而我们所有坐标都是在网络中获取 ⭐交流群:https://t.me/evachating ⚠️ 对接码:EVA520 📣 购买链接:https://luoye.42bb.cn/shop/EVA_Kernel 💬 反馈/代理/bug:@Kasaura
👍99❤2
🎮Apex公益算法解密🦾目前三角洲手游最稳定的公益算法解密 好评如潮 交流群开放.绝对颠覆传统 功能完善媲美端游DMA项目. 产品功能介绍:(算法解密 UDP解密 模拟解密 人物绘制 全物资/容器绘制 掩体漏打变色 内核陀螺仪自瞄 内核触摸自瞄 AI自动压枪 大小地图雷达 网页雷达等等功能) 新版本已更新三角洲最新算法解密,多套解密方案自由切换,不同设备都能找到适合自己的解密,适配市面99%机型,完美解决千人千面加密,不闪框不漏人不遁地 ,欢迎各位用户免费体验! 『点我验证Apex算法解密真实性』 💰打假解密成功奖励10万元人民币 ✨官方频道: https://t.me/ApexZPD https://t.me/ApexZPD https://t.me/ApexZPD
👍98❤1
🧧🧧🧧🧧🧧🧧🧧🧧🧧🧧 🤑电子易爆分 🤩加拿大28类 🃏棋牌游戏 ⚽️体育 🌈电子游戏 🔥彩票💕 麻将胡了 赏金女王 真人 全都有!主打信誉口碑✨ 大小额出款无忧!各种出入款方式 😀问鼎注册链接: w94eu.top 😀君临国际注册: j55ce.top ⚡️非凡注册链接: z31kf.top ⚡️巅峰注册链接: df18r.top ⚡️征途注册链接: zah71.top 💎西海岸注册链接: h70xm.top 😃真龙国际注册🔗: z7ll.top 新上线! 😀万象国际注册🔗: ww290.top 注册送28 🎁新人充值900返388 1100返500! ⚡️⚡️⚡️⚡️ ✨联系扶持客服 @yi1218 详细福利请关注https://t.me/yia1122 ✅邀请好友有福利 邀请充值奖励700人民币!最高奖励1500
👍97❤1
🔷 三角洲公益解密辅助 - 命运 支持ROOT/免ROOT 首发免ROOT绘制 算法解密无视加密 支持三服 功能全面 顶级绘图媲美收费项目 免费网页雷达 无需自购服务器 独家自适应自瞄算法 枪枪到肉 ✅独家驱动 ✅漏打自瞄 ✅算法解密 ROOT模式就是正常的内核辅助 免ROOT支持绘制和雷达两种模式 通过解析网络数据包提取数据 不读取/修改任何内存 支持2D/3D雷达 全彩模型 只要你的设备能联网即可使用 ❤️ 公益频道:@fatedfm ❤️ 交流群组:@fatedfmchat
👍98❤2
Showing the 12 most recent of 472 posts we hold for @ss_00. 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.
@ss_00 edited 8 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.
The 3 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
瓦要什么形式的辅助瞄准
The shares total 114%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
想要更新什么游戏
Shares as published, totalling 98%. No per-option vote count is published by Telegram, so none is shown.
复活qx10-11系列并且添加陀螺仪以及断点功能
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 472 most recent posts we hold, published 11 March 2026 to 17 October 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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 18 October 2026 — this entry's latest reading, not the date you are reading this.
“BY公益内核发布频道” (@ss_00), 133,089 subscribers as measured 18 October 2026. Telegram Register, tgregister.com/channel/ss_00.
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.