以后统一有问题发问题视频+私聊调试,否则不受理
👍16

Channel
@BY_kernel
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Cite this entry
24,992subscribers
+4,167 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1003864369392 |
|---|---|
| Type | Channel |
| Username | @BY_kernel |
| Description | 通知频道:@BY520a 交流群组:@BY520y BY-Kernel-Bot:@BY_Kernel_Bot |
| Created | 4 February 2026 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 October 2026 |
| Measurements held | 39 |
| Confirmed unchanged | 1 time, most recently 14 October 2026 |
| On Telegram | t.me/BY_kernel |
Software piracy — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 46% 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, 17:51 | 24,992 | +25 |
| 13 Oct 2026, 06:10 | 24,967 | +110 |
| 9 Oct 2026, 03:19 | 24,857 | +99 |
| 4 Oct 2026, 17:18 | 24,758 | +621 |
| 26 Sept 2026, 19:00 | 24,137 | +273 |
| 19 Sept 2026, 16:21 | 23,864 | +278 |
| 17 Sept 2026, 07:41 | 23,586 | +99 |
| 15 Sept 2026, 07:59 | 23,487 | +45 |
| 13 Sept 2026, 16:36 | 23,442 | +235 |
| 11 Sept 2026, 20:58 | 23,207 | +143 |
| 9 Sept 2026, 11:39 | 23,064 | +374 |
| 6 Sept 2026, 01:39 | 22,690 | +627 |
| 3 Sept 2026, 22:36 | 22,063 | +456 |
| 2 Sept 2026, 11:46 | 21,607 | +335 |
| 1 Sept 2026, 13:12 | 21,272 | +6 |
| 31 Aug 2026, 13:02 | 21,266 | +9 |
| 30 Aug 2026, 13:55 | 21,257 | +6 |
| 29 Aug 2026, 12:57 | 21,251 | -10 |
| 28 Aug 2026, 11:44 | 21,261 | +2 |
| 27 Aug 2026, 12:29 | 21,259 | first reading |
103 posts held, back to 4 February 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 94 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 12 October 2026 |
|---|---|
| Posts held | 103 (4 February 2026 – 12 October 2026) |
| Views total | 504,055 |
| Reactions total | 2,688 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 15 Oct 2026, 02:23 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 3 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,994 reactions across 102 posts, in 26 distinct kinds. The most used accounts for 70.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 2,808 | 70.3% | |
| ❤ | 440 | 11.0% | |
| 🖕 | 149 | 3.73% | |
| 🤣 | 114 | 2.85% | |
| 😭 | 79 | 1.98% | |
| 💩 | 75 | 1.88% | |
| 🤡 | 68 | 1.70% | |
| 😨 | 61 | 1.53% | |
| 🤓 | 30 | 0.751% | |
| 👎 | 28 | 0.701% | |
| 🤬 | 24 | 0.601% | |
| 🍌 | 15 | 0.376% | |
| 👏 | 15 | 0.376% | |
| 🕊 | 15 | 0.376% | |
| 😁 | 15 | 0.376% | |
| 😍 | 13 | 0.325% | |
| 🥰 | 13 | 0.325% | |
| 🔥 | 7 | 0.175% | |
| 🌭 | 6 | 0.15% | |
| 🌚 | 4 | 0.1% | |
| 6 further kinds | 15 | 0.376% |
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 102 of the 103 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,994 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 103 most recent posts we hold, published 4 February 2026 to 12 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.
以后统一有问题发问题视频+私聊调试,否则不受理
👍16
至今没有一人联系我,默认全体适配,已清理上传
👍36🕊3
解密失效录制视频,发到@ohno_1007,每个上传都能本地重放解密出来,有的还用老版本给我上传
👍29
王者解密自行检查是否开启等,所有上传下发已测试可正常解密,已进行清理
👍28❤1🔥1
GameFrame 云更新已上线 版本:1.1.2 Build:2026101104 渠道:普通版 / BY 版 更新日志: 修复诊断上传将已是明文的坐标表再次变换,导致 output_parsed=false 的误报。 诊断流程现在与实时采样使用相同的明文判断,保留输入原始字节,并明确标注输出来源。 增加部分/完整明文、变换失败与旧诊断包判读回归;本次不修改实时解密算法。 已有云更新功能的客户端重新启动后检查更新。
👍36❤1🔥1
测试
👍29🔥1
🌟 BY Kernel Pro v4.0 更新内容如下 -更新云更新 -适配全部云端上传的下发 进入网盘下载最新版本 https://pan.quark.cn/s/e639b6845c9a
👍43🤩3
驱动更新v9.98 已上传 网盘/BY/BY驱动
👍38❤1
请使用最新版上传无效果分析,老版本一律无视
👍39❤1
🌟 BY Kernel Pro v3.9 更新内容如下 -修复王者解密概率性闪框 -解决项目闪退问题 -解决卡屏2 -补全上传数据完整性 进入网盘下载最新版本 https://pan.quark.cn/s/e639b6845c9a
👍43❤1
🌟 BY Kernel Pro v3.8 更新内容如下 -更新驱动为bydrive v9.97 -修复驱动断点安装失败 -适配亡者5v5小游戏新版本 -适配亡者5v5小游戏加密 -更新亡者5v5血量解密 -修复亡者5v5野怪绘制已知问题 -修复项目卡屏问题 -解决已知所有bug 进入网盘下载最新版本 https://pan.quark.cn/s/e639b6845c9a
👍48❤5
vm样板,有没有token多的
👍20
Showing the 12 most recent of 103 posts we hold for @BY_kernel. 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
瓦要什么形式的辅助瞄准
The shares total 115%, 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.
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 103 most recent posts we hold, published 4 February 2026 to 12 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 14 October 2026 — this entry's latest reading, not the date you are reading this.
“BY Kernel” (@BY_kernel), 24,992 subscribers as measured 14 October 2026. Telegram Register, tgregister.com/channel/BY_kernel.
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.