Telegram RegisterThe public register of Telegram

Channel

Ai官方拿包,解绑发布频道

@XB11033

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

9,564subscribers

+264 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1002489006038
TypeChannel
Username@XB11033
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/XB11033

Growth

9,3009,5649,4326 August 2026 — 9,300 subscribers6 August 2026 — 9,314 subscribers9 August 2026 — 9,457 subscribers13 August 2026 — 9,564 subscribers6 August 202613 August 2026
4 measurements spanning 7 days, net +264. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 9,260–9,604 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 00:149,564+107
9 Aug 2026, 21:549,457+143
6 Aug 2026, 11:209,314+14
6 Aug 2026, 04:029,300first reading

Engagement

24 posts held, back to 28 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 14 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
98.2%
avg views ÷ 9,564 subscribers
Avg views / post
9,390
23 posts measured
Reaction rate
0.106%
reactions ÷ views · ER floor
Posts in window
24
of 24 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 10 August 2026
Posts held24 (28 July 202610 August 2026)
Views total215,980
Reactions total230
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 15: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.

What this channel posts

Video runtime
3m 48s
Average length
1m 54s

Measured directly from 2 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.

Reaction mix

218 reactions across 21 posts, in 6 distinct kinds. The most used accounts for 36.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
8036.7%
👍6529.8%
👎3315.1%
💩2411.0%
🤮146.42%
🤔20.917%

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 23 of the 24 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 230reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 24 most recent posts we hold, published 28 July 2026 to 10 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.

Recent posts

10 Aug 2026, 02:54 UTC≈15,900 views12 reactionsread 12 August 2026
File

‼️‼️❗️❗️❗️❗️❗️❗️❗️❗️‼️‼️ AI典藏版.apk版本 8.10更新日志,公益卡密: @XB1103 本次为云更新 版本号:1.9 1️⃣:增加载具追踪概率调节(全网独家) 2️⃣:增加内鬼模式(物资页面) 3️⃣:增加轮胎追踪,同步腰射开镜概率(需要删除配置之后使用) 4️⃣:优化自瞄指哪打哪算法 5️⃣:修复密钥解密显示问题 6️⃣:修复启动悬浮窗出来立马闪退 7️⃣:修复地铁忽略人机开启之后人机人数归0 8️⃣:修读地铁甲显示问题 9️⃣:修复boss显示是人机 1️⃣0️⃣:修复盒子显示距离调节失效问题 👍Ai始终坚持以人民为中心,坚持全心全意为人民服务,只要是用户需要我们都会进行添加,新赛季成功助力超过5️⃣0️⃣0️⃣+用户封神,感谢Ai用户们的喜爱,还有更新反馈建议联系: @Xiaoyannb666666 ❗️❗️😃点击进入官方频道 ❗️❗️😃点击进入内部交流群

12

9 Aug 2026, 14:02 UTC≈1,210 views5 reactionsread 12 August 2026
File

Ai定制SK和平半火解密端8.9(优化预防高风险数据).zip

👍5

9 Aug 2026, 08:24 UTC≈1,270 views9 reactionsread 12 August 2026

‼️‼️❗️❗️❗️❗️❗️❗️❗️❗️‼️ 目前所有置换活动全部处理,所有代理后台已经授权完毕,所有已置换用户全部已拉内部交流群,置换服务明天截止,所有卡密解绑无限,解密也不扣时,坚持做为人民服务的项目 和平Ai典藏3h卡 天卡 Aiultra3h卡 天卡 瓦手nl 巡猎端口天卡已全部大量补卡 售后联系: @Xiaoyannb666666

👍7🤔2

9 Aug 2026, 05:59 UTC≈1,370 views5 reactionsread 12 August 2026
Photo

😃😀😃 Ai典藏apk版本已经恢复云更新,服务器流量已经正常充值,自瞄算法已经同步Ai黑金+Aipro白金,大幅度降低高危概率,置换仅有最后一天,售后联系: @Xiaoyannb666666

👍41

8 Aug 2026, 15:44 UTC≈7,650 views19 reactionsread 12 August 2026
File

‼️‼️❗️❗️❗️❗️❗️❗️❗️❗️ Ai定制SK和平半火解密端8.8(增加预防高风险数据)更新日志 1:增加预防高风险数据,用户自行测试效果 2:优化解密速度,适配世面所有内核数据 3:增加半火防封数据,可防市面上一切内核随机拉闸问题 4:扩容服务器数据,提升带宽,目前容量健康 5:修复部分用户大厅跑小人问题 6:使用Ai定制sk端口务必先执行sh文件,否则解密无法生效 👍Ai定制sk解密端口依旧采用周卡以上全部免费使用,所有费用Ai团队承担,风雨同舟,玩家至上,不断优化,只为更好 还有更新反馈建议联系: @Xiaoyannb666666 ❗️❗️😃点击进入官方频道 ❗️❗️😃点击进入内部交流群 点我免费获取卡密

👍107👎2

8 Aug 2026, 15:42 UTC≈1,610 views15 reactionsread 12 August 2026
File

Aiultra8.8(修复闪退卡顿,掉后台等).sh

👍93👎3

8 Aug 2026, 15:31 UTC≈17,400 views11 reactionsread 12 August 2026
File

‼️‼️❗️❗️❗️❗️❗️❗️❗️❗️ AI典藏版.apk 8.8更新日志,公益卡密: @XB1103 本次为云更新 版本号:1.8 1️⃣:同步白金自瞄算法,增加平滑速度,降低高危概率 2️⃣:修复人机射线掩体变色问题 3️⃣:修复密钥解密失效问题 4️⃣:修复头甲绘制等级bug 5️⃣:修复盒子绘制距离调节bug 6️⃣:修复开启类骨骼打boss失效问题 7️⃣:修复内鬼模式人物失效问题 👍Ai始终坚持以人民为中心,坚持全心全意为人民服务,只要是用户需要我们都会进行添加,新赛季成功助力超过5️⃣0️⃣0️⃣+用户封神,感谢Ai用户们的喜爱,还有更新反馈建议联系: @Xiaoyannb666666 ❗️❗️😃点击进入官方频道 ❗️❗️😃点击进入内部交流群 点我免费获取卡密

4👍4👎3

8 Aug 2026, 07:22 UTC≈1,450 views22 reactionsread 12 August 2026

‼️‼️❗️❗️❗️❗️❗️❗️❗️❗️‼️‼️ 近期注意到一些关于"AI跑路"的讨论,在此向大家说明:AI项目若非遇到特殊状况,不会无故停止维护。此前AI黑金与AI Pro白金的停更,并非出于我个人意愿,而是由于技术现实因身体原因及个⼈规划调整,无法继续更新。经协商,我无奈接手了该项目的后续开发与维护工作。天下没有不散的筵席,原开发者因故离场,但项目仍会继续服务大家,也感谢各位一直以来的理解与支持。 ❗❗下方为置换规则 置换规则:由于技术替代以及维护成本上升,为了保证用户高品质的使用体验,开启置换服务 黑金+100白金+50,置换完毕发送免费sk解密端口永久卡+内部交流群 置换售后客服: @Xiaoyannb666666

💩19👎3

7 Aug 2026, 06:20 UTC≈16,500 views8 reactionsread 12 August 2026
File

‼️‼️❗️❗️❗️❗️❗️❗️❗️❗️‼️‼️ AI典藏版.apk 8.7更新日志,公益卡密: @XB1103 本次为云更新 版本号:1.7 1️⃣:增加用户强烈反馈的密钥解密显示 2️⃣:真人射线同步血量颜色,方便区分真人 3️⃣:增加用户反馈物资自定义距离调节 4️⃣:优化雷达显示,同步Aipro白金雷达显示 5️⃣:解决游戏最新坐标加密,无视游戏更新 6️⃣:优化渲染流畅度,全网最流畅模型漏打 7️⃣:更新多种坐标解密 8️⃣:优化部分已知问题 👍Ai始终坚持以人民为中心,坚持全心全意为人民服务,只要是用户需要我们都会进行添加,新赛季成功助力超过5️⃣0️⃣0️⃣+用户封神,感谢Ai用户们的喜爱,还有更新反馈建议联系: @Xiaoyannb666666 ❗️❗️😃点击进入官方频道 ❗️❗️😃点击进入内部交流群 点我免费获取卡密

💩5👍2👎1

5 Aug 2026, 08:41 UTC≈9,140 views11 reactionsread 12 August 2026
File

‼️‼️❗️❗️❗️❗️❗️❗️❗️❗️‼️‼️ AIultra8.5(更新解密,解决掩体失效问题)更新日志 1:解决游戏最新下发的加密,更新坐标解密 2:修复用户反馈漏打失效问题,采用手动开启 3:尝试优化用户反馈掉帧卡顿,卡死等问题 4:增加辅助稳定性,隐藏程度提升 👍Ai始终坚持以人民为中心,坚持全心全意为人民服务,只要是用户需要我们都会进行添加,新赛季成功助力超过5️⃣0️⃣0️⃣+用户封神,感谢Ai用户们的喜爱,还有更新反馈建议联系: @Xiaoyannb666666 ❗️❗️😃点击进入官方频道 ❗️❗️😃点击进入内部交流群 点我免费获取卡密

👍4👎43

4 Aug 2026, 12:28 UTC≈64,700 views14 reactionsread 12 August 2026
File

‼️‼️❗️❗️❗️❗️❗️❗️❗️❗️‼️‼️ AI典藏版.apk更新日志,公益卡密: @XB1103 本次为云更新 版本号:1.5 1️⃣:增加地铁boss追踪(使用用类骨骼)即可 2️⃣:修复露手模式开启追踪自瞄等控件无法隐藏问题 4️⃣:增加数组解密 5️⃣:增加手雷追踪(内存功能页面)(如想稳定自己配防) 6️⃣:添加模型渲染开关(可随时卸载模型) 7️⃣:优化模型(解决部分用户漏掩体) 8️⃣:更新辅助解密,同步游戏最新加密,也可以使用sk解密端口 👍Ai始终坚持以人民为中心,坚持全心全意为人民服务,只要是用户需要我们都会进行添加,新赛季成功助力超过5️⃣0️⃣0️⃣+用户封神,感谢Ai用户们的喜爱,还有更新反馈建议联系: @Xiaoyannb666666 ❗️❗️😃点击进入官方频道 ❗️❗️😃点击进入内部交流群 点我免费获取卡密

9👍5

1 Aug 2026, 06:10 UTC≈3,450 views9 reactionsread 12 August 2026
Photo

😃😀😃 Ai典藏apk版本最新自定义教程,已经解决密钥加密问题,任何物资都可以自定义

5👍4

Showing the 12 most recent of 24 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.

Citation-graph rank

Citation-graph rank — 189,829 of 1,160,990entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

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.

Mentions

Named by 6 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.

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.

Cite this entry

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 13 August 2026 — this entry's latest reading, not the date you are reading this.

“Ai官方拿包,解绑发布频道” (@XB11033), 9,564 subscribers as measured 13 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.