Channel
@xiaoxquanneng
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
4,024subscribers
-3,873 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1003584153926 |
|---|---|
| Type | Channel |
| Username | @xiaoxquanneng |
| Created | Between 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/xiaoxquanneng |
Hacking & security — 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 13 September 2026 and assigned it the closest of 31 fixed categories, at 85% 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 |
|---|---|---|
| 19 Sept 2026, 11:41 | 4,024 | -14 |
| 14 Sept 2026, 17:40 | 4,038 | -108 |
| 11 Sept 2026, 00:39 | 4,146 | -260 |
| 6 Sept 2026, 06:17 | 4,406 | -197 |
| 2 Sept 2026, 08:47 | 4,603 | -29 |
| 30 Aug 2026, 14:35 | 4,632 | -28 |
| 27 Aug 2026, 19:28 | 4,660 | -64 |
| 24 Aug 2026, 09:18 | 4,724 | -339 |
| 20 Aug 2026, 09:18 | 5,063 | -1,807 |
| 17 Aug 2026, 12:04 | 6,870 | -990 |
| 14 Aug 2026, 08:37 | 7,860 | -37 |
| 13 Aug 2026, 01:47 | 7,897 | first reading |
24 posts held, back to 2 August 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 3 pages 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 24 posts for this entry, the most recent from 19 August 2026. An engagement rate over an empty window would be a number about nothing.
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.
4 reactions across 2 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 4 | 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 2 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 4 reactions 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 2 August 2026 to 19 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.
出售国内外各种平台账号📱📱📱📱📱📱📱📱📱📱📱📱📱📱📱 🔴买号找小晓⚡️⚡️⚡️ 📱国内微信（可解封，保永久找回） 📱国外微信（可解封，保永久找回） 📱私人QQ （可解封，保永久找回） 📱抖音年号0违规，上号丝滑，核对跟聊天验证人脸都可解决 🈶钉钉.微博.陌陌.抖音.快手.等等... 🈶FB.火种.IG.领英等各种app 🈶全球独享静态IP，可用于快杀 精聊 养号 ✅承接微信/QQ解封 为你保驾护航，保障资源不流失！ IG FB各个国家自选带翠以及海外各类app成品与定制 👍推荐给身边有需要朋友或公司红包28U-—-3888U茶水🧧 👍信誉频道有更多详细介绍：https://t.me/xiaoxquanneng 👍联系方式： @xiaox52013141 （截图此条广告首次交易可优惠❗️） 已上压2000U🔴
📱📱📱最新技术现货秒发年号 🉑接粉爆粉爆群 客户跟本人都已亲测 🉑马上使用🉑当天加20-50个 🉑马上使用🉑当天加20-50个 🉑马上使用🉑当天加20-50个 云机直接转移 海外版 vmos.com （转移成功包十分钟不包操作死）
📱火种男号嘎嘎耐操！ ADS上号！ 售后：别人包首登，我包24小时 欢迎咨询 @xiaox52013141
陌陌满年老号实名可挑男女送svip 探探满年老号实名送可挑男女svip （后期可解封）
📱📱📱私人抖音年号全实名0违规自热非常好留卡25天后期可续费不是0违规包退！！！ @xiaox52013141
📱📱📱WS实卡可选各个地区各个州确保不连号可续费超群很稳随时可接码24小时在线解封 @xiaox52013141
❤2
纯香港🇭🇰6-12月手持护照 可加人 进群 视频号 进企业 额度10万 包收付 纯香港非换绑，封号可解
❤2
@zhuzhihao6666 这个人才之前上了我一个鱼号把我号里好友全删了还用死了不给钱，现在又还在p假图想上QQ白嫖避雷一下
📱📱📱 快手账号密码直登激活成品少量到货 包七天激活 三天找回 比备份包好登录 不掉线 ‼️‼️‼️30+到货 怕备份包掉线的来盘这个 精聊盘口最爱
📱📱📱 国外微信包7天死号免费补上去可加人7天内死了算我这边免费补目前最好用的微信，需要滴滴价格便宜 @xiaox52013141
联系方式 @xiaox52013141 一手对接认准晓 微信 抖音 QQ 快手国内所有软件出货频道 IG FB自选已经海外各类app成品与定制 我会长成一棵大树为那些给我浇过水的人遮风挡雨⚡️⚡️⚡️
交友软件定制： CMB(Coffee Meets Bagel) 派爱（Pairs） Ping! Omiai JD JustDating 火种 大黄蜂 MM 交友软件谁来优先吃肉！需要联系 @xiaox52013141
Showing the 12 most recent of 24 posts we hold for @xiaoxquanneng. 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.
@xiaoxquanneng 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.
Named by 2 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.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“晓晓全能号商” (@xiaoxquanneng), 4,024 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/xiaoxquanneng.
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.