王者🎮内部算法解密内核 适配王者最新UN加密算法 新增方框头像大小调节 新增小地图头像大小调节 优化解密闪框bug 通知频道: https://t.me/jinqyunb 卡网下单:https://luoye.yjsfk.cn/shop/V8ACPC1H/c49b09 【超便宜天一杯,奶茶钱】 五星级售后客服:https://t.me/jinwznb 【找客服售后解决问题,请先提供你的付款截图和订单,否则不回复消息】 👍代理注册链接 对接码: 6flmo95s 欢迎对接,利润拉满
👍14❤2

Channel
@enennba
On this record: Topic · Observations · Growth · Engagement · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
22,891subscribers
+22,768 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1004388344155 |
|---|---|
| Type | Channel |
| Username | @enennba |
| Created | 7 August 2026 — measured — dated from the channel’s first post |
| First recorded | 9 August 2026 |
| Last confirmed live | 6 September 2026 |
| Measurements held | 22 |
| Confirmed unchanged | 1 time, most recently 6 September 2026 |
| On Telegram | t.me/enennba |
Software piracy — 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 17 August 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.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
17,900 average views per post against 22,891 subscribers — an engagement rate of 78.2%. Across the 2,691 registered channels in the same cohort — 10,000–31,610 subscribers, posting mainly in Chinese — the middle half sit between 1.65% and 9.91%, with a median of 4.04%.
| Window | 30 days (8 August 2026 – 7 September 2026) |
|---|---|
| Posts measured | 54 of 55 published in the window (1 exact, 53 rounded by Telegram) |
| Views totalled | 967,178 |
| Mature posts only | 79.9% over 52 posts read at least 24h after publication |
| Subscribers | 22,891 measured 6 September 2026 |
| Cohort | b10000:zho · 2,691 channels · p10 0.508% · p25 1.65% · p50 4.04% · p75 9.91% · p90 20.6% |
| Position in cohort | 99.294th percentile · 19.4× the cohort median |
| Uncertainty | ±0.128% of the figure, from Telegram’s rounding |
| Post language | Chinese · 100.0% of the window’s posts |
When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.
This is not a verdict, and the direction is not a quality signal. A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.
Recorded under the key err_high, last confirmed 7 September 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Sept 2026, 20:36 | 22,891 | +646 |
| 4 Sept 2026, 04:16 | 22,245 | +252 |
| 2 Sept 2026, 17:56 | 21,993 | +252 |
| 1 Sept 2026, 16:23 | 21,741 | +208 |
| 31 Aug 2026, 19:36 | 21,533 | +324 |
| 30 Aug 2026, 20:46 | 21,209 | +250 |
| 29 Aug 2026, 23:33 | 20,959 | +219 |
| 29 Aug 2026, 00:38 | 20,740 | +219 |
| 28 Aug 2026, 02:23 | 20,521 | +121 |
| 27 Aug 2026, 02:56 | 20,400 | +145 |
| 26 Aug 2026, 05:12 | 20,255 | +82 |
| 25 Aug 2026, 04:39 | 20,173 | +138 |
| 23 Aug 2026, 23:37 | 20,035 | +428 |
| 22 Aug 2026, 09:07 | 19,607 | +418 |
| 20 Aug 2026, 23:03 | 19,189 | +466 |
| 19 Aug 2026, 22:11 | 18,723 | +622 |
| 19 Aug 2026, 00:03 | 18,101 | +279 |
| 17 Aug 2026, 20:58 | 17,822 | +480 |
| 16 Aug 2026, 22:23 | 17,342 | +16,771 |
| 9 Aug 2026, 03:00 | 571 | first reading |
57 posts held, back to 7 August 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 37 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 2 September 2026 |
|---|---|
| Posts held | 57 (7 August 2026 – 2 September 2026) |
| Views total | 967,178 |
| Reactions total | 9,583 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 13:09 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.
9,583 reactions across 54 posts, in 31 distinct kinds. The most used accounts for 39.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 3,775 | 39.4% | |
| 😭 | 1,889 | 19.7% | |
| 🖕 | 835 | 8.71% | |
| ❤ | 710 | 7.41% | |
| 🤣 | 518 | 5.41% | |
| 💩 | 441 | 4.60% | |
| 👎 | 404 | 4.22% | |
| 🍌 | 201 | 2.10% | |
| 🕊 | 173 | 1.81% | |
| 🤮 | 108 | 1.13% | |
| 🌭 | 104 | 1.09% | |
| 🤬 | 81 | 0.845% | |
| 🤔 | 52 | 0.543% | |
| 🤩 | 49 | 0.511% | |
| 🤓 | 43 | 0.449% | |
| 👌 | 42 | 0.438% | |
| 🤡 | 27 | 0.282% | |
| 🔥 | 26 | 0.271% | |
| 😁 | 20 | 0.209% | |
| 🤗 | 18 | 0.188% | |
| 11 further kinds | 67 | 0.699% |
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 54 of the 57 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 9,583 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 57 most recent posts we hold, published 7 August 2026 to 2 September 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.
王者🎮内部算法解密内核 适配王者最新UN加密算法 新增方框头像大小调节 新增小地图头像大小调节 优化解密闪框bug 通知频道: https://t.me/jinqyunb 卡网下单:https://luoye.yjsfk.cn/shop/V8ACPC1H/c49b09 【超便宜天一杯,奶茶钱】 五星级售后客服:https://t.me/jinwznb 【找客服售后解决问题,请先提供你的付款截图和订单,否则不回复消息】 👍代理注册链接 对接码: 6flmo95s 欢迎对接,利润拉满
👍14❤2
❤️三角洲算法解密UDP解包内核 可以无视三角洲加密坐标更新 通过解析网络数据包提取玩家数据坐标 ,无需配置任何参数 可过全部查桂机构,隐私与安全性里面的开发者数据包也无法读取到任何获取痕迹全程0写入 不动任何游戏数据! 更新日志 1.优化性能占用 2.适配安卓17,修复低版本安卓系统启动失败 卡网下单: https://luoye.yjsfk.cn/shop/V8ACPC1H 客服售后: https://t.me/jjbnkl ✅ 内核陀螺仪+漏打自瞄随意裸奔 ✅ 内核模型/掩体变色+自研驱动 ✅ 内置云更新,游戏更新最快跟进 超低内存占用,稳定运行,欢迎体验 ❤️➡️频道: @dujnh 免root解包3d模型网页雷达下载点我
👍6❤4
王者🎮内部算法解密内核 适配王者最新UN加密算法 新增方框头像大小调节 新增小地图头像大小调节 优化解密闪框bug 通知频道: https://t.me/jinqyunb 网盘: http://wpan.cdndns.site/down/3cab21b8a9db1ca590ffe7103bdafa3b 卡网下单:https://luoye.yjsfk.cn/shop/V8ACPC1H/c49b09 【超便宜天一杯,奶茶钱】 五星级售后客服:https://t.me/jinwznb 【找客服售后解决问题,请先提供你的付款截图和订单,否则不回复消息】
👍11❤4🕊1
❤️三角洲算法解密UDP解包内核 可以无视三角洲加密坐标更新 通过解析网络数据包提取玩家数据坐标 ,无需配置任何参数 可过全部查桂机构,隐私与安全性里面的开发者数据包也无法读取到任何获取痕迹全程0写入 不动任何游戏数据! 更新日志 1.优化性能占用 2.适配安卓17,修复低版本安卓系统启动失败 卡网下单: https://luoye.yjsfk.cn/shop/V8ACPC1H 客服售后: https://t.me/jjbnkl ✅ 内核陀螺仪+漏打自瞄随意裸奔 ✅ 内核模型/掩体变色+自研驱动 ✅ 内置云更新,游戏更新最快跟进 超低内存占用,稳定运行,欢迎体验 ❤️➡️频道: @dujnh 免root解包3d模型网页雷达下载点我
❤21👍16
已上架支持3d模型显示的天卡 【可以看清楚人物具体在哪个楼层,以及各种物资容器显示】 比普通2d雷达天卡贵10元,因为3d模型要占用大量的服务器资源 https://t.me/dujnh/119
👍9❤4
新版本网页雷达, ip跟安装包全部都变了 不要覆盖安装,把旧版本先删掉再安装,覆盖安装是会出问题的
👍24❤3🔥1
❤️三角洲网页雷达(免root) 不限制机型,华为,IQ,vivo,只要你的设备可以正常联网即可,不需root权限,不需要电脑,不需要解bl,手机联网即可绘制 通过解析网络数据包提取玩家数据坐标 ,无需配置任何参数 可过全部查桂机构,隐私与安全性里面的开发者数据包也无法读取到任何获取痕迹全程0写入 不动任何游戏数据!支持设备型号不限安卓鸿蒙都可以,不限制系统版本,手游都通用 支持3d模型显示人物位置,把游戏整个地图的模型都会加载在雷达上,可以看清楚别人具体在哪个楼层具体位置 卡网下单: https://luoye.yjsfk.cn/shop/V8ACPC1H 客服售后: https://t.me/jjbnkl 通知频道: https://t.me/dujnh 可以完全做到百分之百不封号,前提是环境干净,有root的手机建议直接恢复出厂设置,不需要root权限,能联网就可以玩 有代理想对接或者售卖的可以联系我
👍22❤8
❤️三角洲算法解密UDP解包内核 可以无视三角洲加密坐标更新 通过解析网络数据包提取玩家数据坐标 ,无需配置任何参数 可过全部查桂机构,隐私与安全性里面的开发者数据包也无法读取到任何获取痕迹全程0写入 不动任何游戏数据! 更新日志 1.优化性能占用 2.适配安卓17,修复低版本安卓系统启动失败 卡网下单: https://luoye.yjsfk.cn/shop/V8ACPC1H 客服售后: https://t.me/jjbnkl ✅ 内核陀螺仪+漏打自瞄随意裸奔 ✅ 内核模型/掩体变色+自研驱动 ✅ 内置云更新,游戏更新最快跟进 超低内存占用,稳定运行,欢迎体验 ❤️➡️频道: @dujnh 免root解包3d模型网页雷达下载点我
👍32❤7🍌6🤓2😍2
3d雷达目前就是这种效果,可以显示物资跟容器,可以看清楚敌人在具体哪个楼层,比2d位置更精确 后续我们还会上掩体判断,然后优化一下3d的绘图 https://t.me/dujnh
👍30❤7
三角洲内核解密后真人不显示,换网络,然后重启辅助游戏即可 因为我们的解密是通过网络层面走的udp进行的,有时候解密失败就是网络有问题,重启一下换网络就好
👍30❤2
❤️三角洲UDP解包内核 可以无视三角洲加密坐标更新 通过解析网络数据包提取玩家数据坐标 ,无需配置任何参数 可过全部查桂机构,隐私与安全性里面的开发者数据包也无法读取到任何获取痕迹全程0写入 不动任何游戏数据! 卡网下单: https://luoye.chyidc.cn/shop/V8ACPC1H 客服售后: https://t.me/jjbnkl ✅ 内核陀螺仪+漏打自瞄随意裸奔 ✅ 内核模型/掩体变色+自研驱动 ✅ 内置云更新,游戏更新最快跟进 超低内存占用,稳定运行,欢迎体验 ❤️➡️频道: @dujnh
👍12❤4🍌1🤗1
❤️三角洲3d模型udp解包免root网络雷达 从原来的2 d平面直接升级成3 d,可以看见楼层,可以精确敌人的具体位置,现在😋 3d模型已加入物资,容器绘制 目前仅月卡支持3d模型(包含2d) 下单卡网: https://luoye.chyidc.cn/shop/V8ACPC1H 客服售后: https://t.me/jjbnkl 通知频道: https://t.me/dujnh
👍16❤9🍌1😍1
Showing the 12 most recent of 57 posts we hold for @enennba. 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.
@enennba edited 1 post 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 64 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. The 23 listed below are the most frequent namers; the rest are counted above but not each listed.
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 6 September 2026 — this entry's latest reading, not the date you are reading this.
“不嘿嘿频道” (@enennba), 22,891 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/enennba.
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.