Channel
@superxiaomi1
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,798subscribers
+1,347 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001792066226 |
|---|---|
| Type | Channel |
| Username | @superxiaomi1 |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 6 October 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 6 October 2026 |
| On Telegram | t.me/superxiaomi1 |
Marketing & affiliate — 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 17 September 2026 and assigned it the closest of 31 fixed categories, at 37% 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 |
|---|---|---|
| 6 Oct 2026, 17:20 | 1,798 | -238 |
| 29 Sept 2026, 16:19 | 2,036 | +203 |
| 19 Sept 2026, 06:01 | 1,833 | +117 |
| 14 Sept 2026, 10:00 | 1,716 | +5 |
| 10 Sept 2026, 20:36 | 1,711 | +123 |
| 6 Sept 2026, 00:40 | 1,588 | +50 |
| 2 Sept 2026, 04:24 | 1,538 | +16 |
| 30 Aug 2026, 12:55 | 1,522 | +1,070 |
| 22 Aug 2026, 14:44 | 452 | +3 |
| 14 Aug 2026, 14:34 | 449 | -2 |
| 8 Aug 2026, 05:02 | 451 | no change |
| 7 Aug 2026, 19:45 | 451 | first reading |
20 posts held, back to 12 January 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 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 24 July 2026. An engagement rate over an empty window would be a number about nothing.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👏 | 1 | 100.0% |
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 1 of the 20 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 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 12 January 2026 to 24 July 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.
♾更新公告♾ 尊敬的用户： 平台于 今日（2026年7月24日） 进行协议版本更新，具体更新内容如下： 一、协议版本更新 各客户端协议版本号同步升级至最新版本： · 谷歌：12.9.0 (69662) · 官网：12.9.0 (69669) · 电脑客户端：7.0.2 · 苹果（iOS）：12.9.2 (34474) 注意事项 感谢您的理解与配合！ ➡️ 点击联系客服获取免费3天100个测试端口和免费测试数据
♾版本更新通知♾ 尊敬的用户： 平台已完成协议版本升级，各端最新版本号如下： 谷歌:12.8.3 (69222) 官网:12.8.3 (69229) 电脑:6.9.3 苹果:12.8.1 (33181) • 本次更新后有掉线的账号请重新登录后继续使用。如遇功能异常，请刷新页面。 感谢您的理解与配合！ ➡️ 点击联系客服获取免费3天100个测试端口和免费测试数据
♾更新公告♾ 尊敬的用户： 客服坐席新增「同步」功能 · 当前客服坐席默认仅显示近 1 个月且已开通权限的消息记录 · 新增「同步」按钮，点击后可加载该账号下的全部历史消息，便于您对比消息是否存在丢失 · 请谨慎使用：加载全量消息需一定时间，且对电脑配置及网络环境有一定要求 · 如需使用，建议逐个账号进行同步测试，避免同时操作多个账号影响性能 注意事项 · 本次更新不影响现有任务运行，无需重启任务 · 使用同步功能时请耐心等待加载完成，若数据较多可能出现短暂卡顿 感谢您的理解与配合！ ➡️ 点击联系客服获取免费3天100个测试端口和免费测试数据
♾更新公告♾ 尊敬的用户： 平台将于 2026 年 6 月 13 日 09:00-10:00（北京时间） 进行预约更新，具体更新内容如下： 一、数据清理优化 · 优化用户数据处理逻辑，用户名无效/未占用 的相关数据将不再被重复使用 更新耗时 1-5 分钟 注意事项 · 本次更新期间任务将自动停止，更新完成后需手动启动任务 · 更新后可能出现任务数据不一致的情况，请注意核对（建议提前停止任务） 感谢您的理解与配合！ ➡️ 点击联系客服获取免费3天100个测试端口和免费测试数据
♾临时更新通知 ♾ 尊敬的用户： 临时更新任务端，所有进行中的任务已停止，请手动重开。 感谢您的理解与配合！ ➡️ 点击联系客服获取免费3天100个测试端口和免费测试数据
♾小米知识分享♾ TG云控私信群发 + 客服系统注意事项 做TG云控私信群发，不要只看能发多少条，更要看账号稳不稳、话术自不自然、客服能不能及时接住回复。 1、影响账号稳定的因素比较多 TG账号能不能正常发消息，主要和几个因素有关：首发话术、对方回复后的第一条承接话术、账号国家、IP连通性、IP干净程度，还有账号本身质量。不是所有账号都能一样发送，也不是今天能发，明天就一定完全一样。 2、双向私信的流程要简单 一般流程就是：先简单打招呼，等对方回复后，再继续正常聊天。不要一上来就发太长、太硬、太像广告的内容，这样效果差，也容易让账号出问题。 3、账号国家尽量匹配目标国家 你发哪个国家的数据，最好优先测试对应国家或相近地区的TG账号。如果一个号可以正常发新招呼，并且当天或隔天没有冻结、封号、踢出设备，就说明这个号基本可以正常使用。 每个账号每天能发多少新招呼不固定，一般是1-5条，先小量测试，不要一开始就猛发。 …
♾版本更新通知♾ 尊敬的用户： 平台已完成协议版本升级，各端最新版本号如下： • Google Play 安卓：12.7.3 (67502) • 官方网页安卓：12.7.2 (67439) • PC 端：6.8.2 • iOS：12.7 (32933) • 本次更新后有掉线的账号请重新登录后继续使用。如遇功能异常，请刷新页面。 感谢您的理解与配合！ ➡️ 点击联系客服获取免费3天100个测试端口和免费测试数据
♾版本升级公告♾ 尊敬的用户： 平台已完成协议版本升级，各端最新版本号如下： • Google Play 安卓：12.6.4 (66662) • 官方网页安卓：12.6.4 (66669) • PC 端：6.7.8 • iOS：12.6.3 (32738) • 本次更新后有掉线的账号请重新登录后继续使用。如遇功能异常，请刷新页面。 感谢您的理解与配合！ ➡️ 点击联系客服获取免费3天100个测试端口和免费测试数据
♾功能升级♾ 尊敬的用户： 平台已完成功能升级，具体更新内容如下： 一、公司管理增强 • 新增账号信息修改功能：支持修改昵称、用户名及密码 二、客服坐席批量操作 • 支持批量创建客服坐席 • 支持批量修改客服坐席信息 • 支持批量修改客服坐席权限 • 支持批量删除客服坐席 本次升级为静默更新，无需重新登录。如遇功能异常，可联系客服为您解决！ 感谢您的理解与配合！ ➡️ 点击联系客服获取免费3天100个测试端口和免费测试数据
♾版本更新公告♾ 尊敬的用户： 平台已完成版本升级，具体更新内容如下： 一、协议版本更新 • Google Play 安卓：12.5.2 (65972) • 官方网页安卓：12.5.2 (65979) • PC 端：6.6.2 • iOS：12.5.2 (32493) 二、功能优化 • 优化 PC 协议搜索性能，提升查询响应速度 注意事项 • 本次更新后有掉线的账号请重新登录后继续使用 感谢您的理解与配合！ ➡️ 点击联系客服获取免费3天100个测试端口和免费测试数据
♾更新公告♾ 尊敬的用户： 平台于 2026 年 3 月 24 日 9点（北京时间） 进行更新，具体更新内容如下： 一、语音优化 • 优化语音波形 二、任务管理增强 • 新增「清理失败计次」功能：当账号失败次数达到上限时，可通过清理操作重置状态，继续完成任务 三、客服功能微调 • 优化客服模块交互细节，提升操作流畅度 注意事项 • 本次更新将强制所有账号退出登录，任务自动停止 • 请在更新完成后重新登录并手动重启任务 感谢您的理解与配合！ ➡️ 点击联系客服获取免费3天100个测试端口和免费测试数据
♾功能更新♾ 具体更新内容如下： 一、任务创建优化 • 取消创建任务时的文案与文件快捷输入功能，简化操作流程 二、上传体验升级 • 优化上传界面交互 • 新增失败文件展示区域，支持一键快捷重试 三、账号导出 • 导出账号新增 session 类型字段，满足精细化运营需求 四、新增功能模块 • 新增群发任务分享链接，支持任务配置快速共享与协作 本次升级为静默更新，无需重新登录。如遇功能异常，请及时与官方客服反馈 感谢您的理解与配合！ ➡️ 点击联系客服获取免费3天100个测试端口和免费测试数据
Showing the 12 most recent of 20 posts we hold for @superxiaomi1. 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.
Named by 1 registered channel — 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.
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 October 2026 — this entry's latest reading, not the date you are reading this.
“小米云控官方频道-Telegram云控Tg云控飞机群发打粉/拉群/客服坐席客服系统自动剧本” (@superxiaomi1), 1,798 subscribers as measured 6 October 2026. Telegram Register, tgregister.com/channel/superxiaomi1.
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.