⚙️ Bot 功能更新公告 🤖机器人:AIBoxBot ✨ 中文生图 文生图6 新增两个NSFW Lora 点击获取最新机器人地址 高速服务区,防失联 如在使用过程中遇到问题,可通过 [客服 / 群组] 反馈。 #BotUpdate #功能更新
👍2❤1

Channel
@aiboxbot_public
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Cite this entry
54,102subscribers
-2,231 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001840335424 |
|---|---|
| Type | Channel |
| Username | @aiboxbot_public |
| Description | AI工具箱AIBox版本发布,相关通知,防失联。机器人链接 @aibox_forward2048_bot 有具体问题请咨询客服 @aibxkefu_bot |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 28 October 2026 |
| Measurements held | 53 |
| Confirmed unchanged | 1 time, most recently 28 October 2026 |
| On Telegram | t.me/aiboxbot_public |
Technology — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 93% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Oct 2026, 00:55 | 54,102 | -37 |
| 27 Oct 2026, 03:39 | 54,139 | -20 |
| 26 Oct 2026, 04:06 | 54,159 | -16 |
| 25 Oct 2026, 01:56 | 54,175 | -32 |
| 24 Oct 2026, 01:08 | 54,207 | -28 |
| 22 Oct 2026, 22:19 | 54,235 | -31 |
| 21 Oct 2026, 17:36 | 54,266 | -21 |
| 20 Oct 2026, 13:21 | 54,287 | -22 |
| 19 Oct 2026, 15:48 | 54,309 | -19 |
| 18 Oct 2026, 18:57 | 54,328 | -18 |
| 17 Oct 2026, 18:01 | 54,346 | -33 |
| 16 Oct 2026, 14:56 | 54,379 | -22 |
| 15 Oct 2026, 15:46 | 54,401 | -30 |
| 14 Oct 2026, 13:28 | 54,431 | -33 |
| 13 Oct 2026, 04:26 | 54,464 | -120 |
| 8 Oct 2026, 19:40 | 54,584 | -151 |
| 4 Oct 2026, 09:19 | 54,735 | -223 |
| 25 Sept 2026, 21:58 | 54,958 | -181 |
| 19 Sept 2026, 03:39 | 55,139 | -45 |
| 16 Sept 2026, 18:22 | 55,184 | first reading |
60 posts held, back to 4 May 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 169 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. It is computed over the 14 of 17 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 27 October 2026 |
|---|---|
| Posts held | 60 (4 May 2026 – 27 October 2026) |
| Views total | 25,693 |
| Reactions total | 31 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 28 Oct 2026, 13:22 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 28 October 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
70 reactions across 38 posts, in 2 distinct kinds. The most used accounts for 68.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 48 | 68.6% | |
| 👍 | 22 | 31.4% |
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 42 of the 60 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 70 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 60 most recent posts we hold, published 4 May 2026 to 27 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.
⚙️ Bot 功能更新公告 🤖机器人:AIBoxBot ✨ 中文生图 文生图6 新增两个NSFW Lora 点击获取最新机器人地址 高速服务区,防失联 如在使用过程中遇到问题,可通过 [客服 / 群组] 反馈。 #BotUpdate #功能更新
👍2❤1
⚙️ Bot 功能更新公告 🤖机器人:AIBoxBot ✨ 新增 文生图6 功能,支持NSFW 点击获取最新机器人地址 高速服务区,防失联 如在使用过程中遇到问题,可通过 [客服 / 群组] 反馈。 #BotUpdate #功能更新
🚀 AIBox 小程序版本正式上线! 🤖机器人:AIBox小程序 🎉 AIBox 全新推出小程序版本,带来更便捷、更流畅的使用体验! ✨ 本次升级亮点: 🧩 功能更集中:常用功能统一整合,一站式使用 ⚡️ 操作更便捷:简化操作流程,使用更加轻松 🚀 体验再升级:功能布局更清晰,操作更顺手 点击获取最新机器人地址 高速服务区,防失联 如在使用过程中遇到问题,可通过 [客服 / 群组] 反馈。 #BotUpdate #功能更新
❤1
📢 【Telegram 私人群组创建教程】 按照自己使用的设备创建 Telegram 私人群组。 ✅ 创建完成后,请确认群组类型为 「私人(Private)」。 📌 请按照图片中的步骤操作即可!
🌿 SFW 频道推荐 AI美咲写真集
👍1
⚙️ Bot 功能更新公告 🤖机器人:AIBoxBot ✨ 新增 图片编辑2 功能 点击获取最新机器人地址 高速服务区,防失联 如在使用过程中遇到问题,可通过 [客服 / 群组] 反馈。 #BotUpdate #功能更新
AI工具箱AIBox版本发布防失联频道 pinned Deleted message
⚙️ Bot 功能更新公告 🤖机器人:AIBoxBot ✨ 视频换脸功能已经恢复,并将时长放宽到了 2 分钟 点击获取最新机器人地址 高速服务区,防失联 如在使用过程中遇到问题,可通过 [客服 / 群组] 反馈。 #BotUpdate #功能更新
❤2
⚙️ Bot 备选克隆教程 操作步骤: 1、点击打开 @BotFather。 2、发送 /newbot,按照提示设置机器人名称和用户名。 3、创建成功后,复制 @BotFather 提供的 Token。 4、将机器人用户名(不带 @)和 Token 按以下格式发送给克隆机器人,即可完成绑定。 ✅ 提交示例: 机器人用户名 Token 机器人用户名和 Token 之间用空格或换行分隔均可。 点击获取最新机器人地址 高速服务区,防失联 如在使用过程中遇到问题,可通过 [客服 / 群组] 反馈。 #BotUpdate #功能更新
❤1👍1
⚙️ Bot 功能更新公告 🤖机器人:AIBoxBot ✨ Klein图像编辑 新增 文生图2、单图编辑2 功能 ✨ 图像编辑 新增 换头 功能 点击获取最新机器人地址 高速服务区,防失联 如在使用过程中遇到问题,可通过 [客服 / 群组] 反馈。 #BotUpdate #功能更新
❤1👍1
⚙️ Bot 功能更新公告 🤖机器人:AIBoxBot ✨ 图像编辑2 新增 双图编辑 功能 点击获取最新机器人地址 高速服务区,防失联 如在使用过程中遇到问题,可通过 [客服 / 群组] 反馈。 #BotUpdate #功能更新
❤3👍1
⚙️ Bot 功能更新公告 为保障您的长期使用权益,所有用户必须克隆一个属于自己的私人机器人,实现独立使用、专属管理。 ⚠️ 主机器人可能随时出现异常或被封禁! 提前拥有私人机器人,可有效降低使用中断的风险。即使主机器人无法使用,只要您的私人机器人未受到限制,仍可正常运行,保障业务持续使用! 打开 AIBox机器人 按引导提示创建自己的专属机器人 点击获取最新机器人地址 高速服务区,防失联 如在使用过程中遇到问题,可通过 [客服 / 群组] 反馈。 #BotUpdate #功能更新
👍1
Showing the 12 most recent of 60 posts we hold for @aiboxbot_public. 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.
@aiboxbot_public edited 5 posts 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.
@aiboxbot_public named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 28 October 2026 — this entry's latest reading, not the date you are reading this.
“AI工具箱AIBox版本发布防失联频道” (@aiboxbot_public), 54,102 subscribers as measured 28 October 2026. Telegram Register, tgregister.com/channel/aiboxbot_public.
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.