😃😀😀 目前和平Ai定制sk解密端使用名额趋于饱和,购买过Ai任意系列永久卡的用户和没有进内部交流群的用户可以抓紧联系售后了,联系: @Xiaoyannb666666
👍4🔥1

Channel
@XB11033
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
9,751subscribers
+451 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002489006038 |
|---|---|
| Type | Channel |
| Username | @XB11033 |
| Description | 安装包获取地址 |
| Created | Between 1 October 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 4 September 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 3 times, most recently 4 September 2026 |
| On Telegram | t.me/XB11033 |
Gaming — 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 15 August 2026 and assigned it the closest of 31 fixed categories, at 45% 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 |
|---|---|---|
| 29 Aug 2026, 01:36 | 9,751 | +24 |
| 26 Aug 2026, 11:47 | 9,727 | +15 |
| 23 Aug 2026, 20:08 | 9,712 | +45 |
| 19 Aug 2026, 18:26 | 9,667 | +21 |
| 16 Aug 2026, 19:38 | 9,646 | +82 |
| 13 Aug 2026, 00:14 | 9,564 | +107 |
| 9 Aug 2026, 21:54 | 9,457 | +143 |
| 6 Aug 2026, 11:20 | 9,314 | +14 |
| 6 Aug 2026, 04:02 | 9,300 | first reading |
37 posts held, back to 28 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 34 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 28 August 2026 |
|---|---|
| Posts held | 37 (28 July 2026 – 28 August 2026) |
| Views total | 116,672 |
| Reactions total | 224 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 29 Aug 2026, 05:15 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 29 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 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.
346 reactions across 34 posts, in 7 distinct kinds. The most used accounts for 45.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 158 | 45.7% | |
| ❤ | 108 | 31.2% | |
| 👎 | 34 | 9.83% | |
| 💩 | 24 | 6.94% | |
| 🤮 | 14 | 4.05% | |
| 🤔 | 5 | 1.45% | |
| 🔥 | 3 | 0.867% |
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 36 of the 37 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 358 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 37 most recent posts we hold, published 28 July 2026 to 28 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.
😃😀😀 目前和平Ai定制sk解密端使用名额趋于饱和,购买过Ai任意系列永久卡的用户和没有进内部交流群的用户可以抓紧联系售后了,联系: @Xiaoyannb666666
👍4🔥1
‼️‼️❗️❗️❗️❗️❗️❗️❗️❗️‼️‼️ AI典藏版.apk版本 8.24更新日志,公益卡密: @XB1103 本次为云更新 版本号:2.3 1.优化安全区预测 2.增加自瞄漏哪打哪 3.重构模型渲染 4.重构底层逻辑优化CPU占用 5.选择新的自瞄模式后强制开启算法无后且自适应 6.增加古墓类名 7.修复投掷物预警失效 👍Ai始终坚持以人民为中心,坚持全心全意为人民服务,只要是用户需要我们都会进行添加,新赛季成功助力超过5️⃣0️⃣0️⃣+用户封神,感谢Ai用户们的喜爱,还有更新反馈建议联系: @Xiaoyannb666666 ❗️❗️😃点击进入官方频道 ❗️❗️😃点击进入内部交流群 点我免费获取卡密
👍10❤2🔥1
‼️‼️❗️❗️❗️❗️❗️❗️❗️❗️‼️‼️ 全网大部分追踪项目集体拉闸,Ai典藏和Aiultra经过内部排查无视这次检测,稳定性这块可以相信Ai
👍9🤔3
三角洲奔驰启动视频教程
👍7🔥1
Aiultra俱乐部特供8.24(彻底修复物资镜像).zip
👍7❤2
AIultra8.22(修复物资镜像,增加头甲绘制).zip
👍7❤2
‼️‼️❗️❗️❗️❗️❗️❗️❗️❗️‼️‼️ AI典藏版.apk版本 8.20更新日志,公益卡密: @XB1103 本次为云更新 版本号:2.2 1️⃣:增加安全区预测(在雷达页面里面)百分百准确 2️⃣:增加同行识别(目前仅能看到世面部分项目 晚一点就可以看到其他辅助的了 只要是对接了云验的都可以看到 再次解释:你不打开这个开关 别人就看不到你 你也看不到别人。你打开了这个开关的话 你看得到别人 别人也看得到你) 3️⃣:修复迫击炮雷达显示不准问题 4️⃣:优化预测安全区 5️⃣:增加模型读取方式 6️⃣:修复部分设备无法投屏模式bug 7️⃣:修复了一些其他的小问题,优化用户体验 8️⃣:修复淘汰王绘制没效果 👍Ai始终坚持以人民为中心,坚持全心全意为人民服务,只要是用户需要我们都会进行添加,新赛季成功助力超过5️⃣0️⃣0️⃣+用户封神,感谢Ai用户们的喜爱,还有更新反馈建议联系: @Xiaoyan…
👍9❤2
Ai典藏卡密验证已经恢复 湖北dns劫持已申诉解封,湖北用户可以正常使用了
👍5
卡网上架瓦手wawa内部 😙修复登录网络异常 1️⃣更新Wawa驱动处理页面折叠和超大页面 2️⃣修复一些驱动被特征问题 3️⃣删除悬浮窗雷达距离 4️⃣更新共享雷达流畅 5️⃣更新玩家名单 6️⃣修复登录错误 7️⃣修复掩体判断(发搓包了) 自愿赞助地址 1:https://shop.368fk.cn/shop/ZNOU7RUE 2:https://ufo.fakalon.cn/links/80F1B96F 🔗瓦瓦网盘下载https://wwbju.lanzouq.com/b01884raid 密码666 反馈 @Xiaoyannb666666
👍7❤6
AIultra8.16(更新解密,修复物资).zip
👍6
‼️‼️❗️❗️❗️❗️❗️❗️❗️❗️‼️‼️ AI典藏版.apk版本 8.16更新日志,公益卡密: @XB1103 本次为云更新 版本号:2.1 1.优化掩体刷新速度设置 2.支持安卓17 3.修复迫击炮雷达bug 4.增加"自适应压枪"开关,不开的话,就是之前原汁原味的,自己调节的 开了的话就是自适应 5.增加淘汰王绘制 👍Ai始终坚持以人民为中心,坚持全心全意为人民服务,只要是用户需要我们都会进行添加,新赛季成功助力超过5️⃣0️⃣0️⃣+用户封神,感谢Ai用户们的喜爱,还有更新反馈建议联系: @Xiaoyannb666666 ❗️❗️😃点击进入官方频道 ❗️❗️😃点击进入内部交流群 点我免费获取卡密
👍6❤4
‼️‼️❗️❗️❗️❗️❗️❗️❗️❗️‼️‼️ AI典藏版.apk版本 8.13更新日志,公益卡密: @XB1103 本次为云更新 版本号:2.0 1:修复密钥解密 2:增加轮胎追踪快捷开关 3:移除空投无人机物资 4:修复无后台导致悬浮窗闪退问题 5:修复用户反馈绘制卡顿等问题,最大程度优化代码 6:新增掩体刷新速度调节(同步Aipro白金模型库) 7:增加"自适应压枪"开关,同步Aipro白金自适应数据(内测中) 👍Ai始终坚持以人民为中心,坚持全心全意为人民服务,只要是用户需要我们都会进行添加,新赛季成功助力超过5️⃣0️⃣0️⃣+用户封神,感谢Ai用户们的喜爱,还有更新反馈建议联系: @Xiaoyannb666666 ❗️❗️😃点击进入官方频道 ❗️❗️😃点击进入内部交流群 点我免费获取卡密
👍7❤3
Showing the 12 most recent of 37 posts we hold for @XB11033. 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.
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 11 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 29 August 2026 — this entry's latest reading, not the date you are reading this.
“Ai官方拿包,解绑发布频道” (@XB11033), 9,751 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/XB11033.
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.