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

Channel
@citadel8888
On this record: Topic · Growth · Engagement · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
19,388subscribers
+4,682 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1003864589860 |
|---|---|
| Type | Channel |
| Username | @citadel8888 |
| Created | 12 February 2026 — measured — dated from the channel’s first post |
| First recorded | 8 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 32 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/citadel8888 |
Other / unclassifiable — 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 62% 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 Sept 2026, 05:37 | 19,388 | +165 |
| 16 Sept 2026, 02:39 | 19,223 | +120 |
| 14 Sept 2026, 06:15 | 19,103 | +110 |
| 12 Sept 2026, 15:00 | 18,993 | +138 |
| 10 Sept 2026, 15:21 | 18,855 | +207 |
| 7 Sept 2026, 09:56 | 18,648 | +223 |
| 4 Sept 2026, 11:20 | 18,425 | +57 |
| 2 Sept 2026, 22:35 | 18,368 | +48 |
| 1 Sept 2026, 23:45 | 18,320 | +52 |
| 1 Sept 2026, 00:37 | 18,268 | +72 |
| 31 Aug 2026, 02:04 | 18,196 | +121 |
| 29 Aug 2026, 22:28 | 18,075 | +58 |
| 29 Aug 2026, 00:43 | 18,017 | +88 |
| 28 Aug 2026, 01:56 | 17,929 | +102 |
| 27 Aug 2026, 03:32 | 17,827 | +137 |
| 26 Aug 2026, 03:23 | 17,690 | +133 |
| 25 Aug 2026, 04:33 | 17,557 | +135 |
| 24 Aug 2026, 01:06 | 17,422 | +267 |
| 22 Aug 2026, 09:29 | 17,155 | +244 |
| 20 Aug 2026, 20:52 | 16,911 | first reading |
93 posts held, back to 12 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 50 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 3 September 2026 |
|---|---|
| Posts held | 93 (12 February 2026 – 3 September 2026) |
| Views total | 20,919 |
| Reactions total | 360 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 08:53 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.
1,602 reactions across 91 posts, in 17 distinct kinds. The most used accounts for 64.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 1,033 | 64.5% | |
| ❤ | 421 | 26.3% | |
| 👏 | 30 | 1.87% | |
| 😁 | 20 | 1.25% | |
| 🤣 | 18 | 1.12% | |
| 🤬 | 14 | 0.874% | |
| 👎 | 13 | 0.811% | |
| 💩 | 11 | 0.687% | |
| 🥰 | 11 | 0.687% | |
| 🍌 | 8 | 0.499% | |
| 🔥 | 7 | 0.437% | |
| 😘 | 5 | 0.312% | |
| 🖕 | 4 | 0.25% | |
| 🤪 | 4 | 0.25% | |
| 🏆 | 1 | 0.062% | |
| 💔 | 1 | 0.062% | |
| 🕊 | 1 | 0.062% |
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 91 of the 93 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 1,602 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 93 most recent posts we hold, published 12 February 2026 to 3 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 欢迎对接,利润拉满
👍6
葫芦娃公益内核9.4更新日志 🎮和平内核更新日志 🌭修复密钥加密失效 🌭修复人机判断问题 🌭观战巡查暂时没有数据,删除 🎮无畏契约更新日志 🌭新增算法闪框解密2 全图解密敌人闪框,不漏人,不延迟,不卡顿 ❤️三角洲内核更新日志 🌭取消APP启动,采用sh启动 mt启动文件时,三角洲绝对不能在后台,否则会被三角洲检测Mt终端封号,启动完之后,必须把Mt后台给划掉 三角洲驱动文件放在网盘了 目前葫芦娃已适配PUBG4.5🎮最新四服,和平精英🎮,无畏契约🎮,❤️三角洲四游戏,网页雷达共享,软件雷达共享都已公益免费使用,卡密随便输入 网盘更新下载: https://drive.uc.cn/s/bcbdf247fb584?public=1 葫芦娃频道 @HLWNHNB 聊天群 @hulwjlq
👍11
王者🎮内部算法解密内核 适配王者最新UN加密算法 新增方框头像大小调节 新增小地图头像大小调节 优化解密闪框bug 通知频道: https://t.me/jinqyunb 卡网下单:https://luoye.yjsfk.cn/shop/V8ACPC1H/c49b09 【超便宜天一杯,奶茶钱】 五星级售后客服:https://t.me/jinwznb 【找客服售后解决问题,请先提供你的付款截图和订单,否则不回复消息】 👍代理注册链接 对接码: 6flmo95s 欢迎对接,利润拉满
👍8
❤️三角洲算法解密UDP解包内核 可以无视三角洲加密坐标更新 通过解析网络数据包提取玩家数据坐标 ,无需配置任何参数 可过全部查桂机构,隐私与安全性里面的开发者数据包也无法读取到任何获取痕迹全程0写入 不动任何游戏数据! 更新日志 1.优化性能占用 2.适配安卓17,修复低版本安卓系统启动失败 卡网下单: https://luoye.yjsfk.cn/shop/V8ACPC1H 客服售后: https://t.me/jjbnkl ✅ 内核陀螺仪+漏打自瞄随意裸奔 ✅ 内核模型/掩体变色+自研驱动 ✅ 内置云更新,游戏更新最快跟进 超低内存占用,稳定运行,欢迎体验 ❤️➡️频道: @dujnh 免root解包3d模型网页雷达下载点我
👍5👎1
适配🎮和平精英1.38.12新版本公益内核 基本绘制,自瞄这些功能没问题,有些小细节新版本可能会有点bug,评论区反馈我即可 取消APP版本启动,后续所有项目都会改为sh启动,原因很多人应该都知道,我就不解释了 开发者不会主动联系你 本项目也没有任何收费及内部 葫芦娃不会诋毁任何人及项目 网络上任何流言也要注意甄别 本项目仅供逆向学习研究 体验者的任何行为与作者无关 若有侵权违法行为,请联系我删除内容 请在24小时内删除本应用[下载代表同意本协议] 欢迎使用葫芦娃和平精英公益辅助 葫芦娃频道 @HLWNHNB 聊天群 @hulwjlq
👍8❤1🖕1
❤️三角洲算法解密UDP解包内核 可以无视三角洲加密坐标更新 通过解析网络数据包提取玩家数据坐标 ,无需配置任何参数 可过全部查桂机构,隐私与安全性里面的开发者数据包也无法读取到任何获取痕迹全程0写入 不动任何游戏数据! 更新日志 1.优化性能占用 2.适配安卓17,修复低版本安卓系统启动失败 卡网下单: https://luoye.yjsfk.cn/shop/V8ACPC1H 客服售后: https://t.me/jjbnkl ✅ 内核陀螺仪+漏打自瞄随意裸奔 ✅ 内核模型/掩体变色+自研驱动 ✅ 内置云更新,游戏更新最快跟进 超低内存占用,稳定运行,欢迎体验 ❤️➡️频道: @dujnh 免root解包3d模型网页雷达下载点我
👍13❤2👎1
❤️三角洲算法解密UDP解包内核 可以无视三角洲加密坐标更新 通过解析网络数据包提取玩家数据坐标 ,无需配置任何参数 可过全部查桂机构,隐私与安全性里面的开发者数据包也无法读取到任何获取痕迹全程0写入 不动任何游戏数据! 更新日志 1.优化性能占用 2.适配安卓17,修复低版本安卓系统启动失败 卡网下单: https://luoye.yjsfk.cn/shop/V8ACPC1H 客服售后: https://t.me/jjbnkl ✅ 内核陀螺仪+漏打自瞄随意裸奔 ✅ 内核模型/掩体变色+自研驱动 ✅ 内置云更新,游戏更新最快跟进 超低内存占用,稳定运行,欢迎体验 ❤️➡️频道: @dujnh 免root解包3d模型网页雷达下载点我
👍9
王者🎮内部算法解密内核 适配王者最新UN加密算法 新增方框头像大小调节 新增小地图头像大小调节 优化解密闪框bug 通知频道: https://t.me/jinqyunb 网盘: http://wpan.cdndns.site/down/3cab21b8a9db1ca590ffe7103bdafa3b 卡网下单:https://luoye.yjsfk.cn/shop/V8ACPC1H/c49b09 【超便宜天一杯,奶茶钱】 五星级售后客服:https://t.me/jinwznb 【找客服售后解决问题,请先提供你的付款截图和订单,否则不回复消息】
👍10
王者🎮公益算法解密内核 适配王者最新UN加密算法 新增方框头像大小调节 新增小地图头像大小调节 优化解密闪框bug 通知频道: https://t.me/jinqyunb 不禁言交流群: https://t.me/jinqiangyunb 网盘: http://wpan.cdndns.site/down/3cab21b8a9db1ca590ffe7103bdafa3b
👍5
王者公益解密内核 原金枪鱼内部算法解密,现在公益免费 不闪框,不卡框,不漏人 永不封号拉闸,解密和谐24小时内可以更新 通知频道: https://t.me/jinqyunb 不禁言交流群: https://t.me/jinqiangyunb
👍18❤1
葫芦娃三角洲🎮公益解密内核9.4更新日志 🌭新增三角洲网页雷达共享 适配零号大坝,长弓溪谷,航天基地,巴克什,潮汐监狱,AZ3五款地图 🌭网页雷达支持队友视角切换,可实现一人开挂,全队共享 🌭高级物资列表单独显示,根据物资等级分类开关显示,全部以高清蓝图显示 🌭网页雷达支持绘制玩家,队友,人机,玩家盒子,方向线,自己标识,装备文字,距离,物资功能完善,绘图清晰 🌭优化程序启动速度,优化cpu占用率 目前葫芦娃已适配PUBG4.5🎮最新四服,和平精英🎮,无畏契约🎮,三角洲❤️四款游戏,网页雷达共享,软件雷达共享都已公益免费使用,卡密随便输入,以及免root模型AI吸附自瞄 网盘更新下载: https://drive.uc.cn/s/531ebaccc73f4?public=1 葫芦娃频道 @HLWNHNB 聊天群 @hulwjlq
👍10
这几天看看吧 更新一下hook方案 接 频道广告or软件广告 软件稳定日活1w+ @daidai987 我真服了开未知用户自动归档了。。。 需要广告商家重新联系谢谢
👍16❤2🍌1
Showing the 12 most recent of 93 posts we hold for @citadel8888. 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.
@citadel8888 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.
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.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“CitAdel丨多功能系统APP” (@citadel8888), 19,388 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/citadel8888.
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.