Channel
@xiaozhenag04
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
3,410subscribers
+4 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002010817638 |
|---|---|
| Type | Channel |
| Username | @xiaozhenag04 |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/xiaozhenag04 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 16:43 | 3,410 | +4 |
| 12 Aug 2026, 11:16 | 3,406 | first reading |
5 posts held, back to 6 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 1 pageof 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 11 August 2026 |
|---|---|
| Posts held | 5 (6 August 2026 – 11 August 2026) |
| Views total | 1,136 |
| Reactions total | 4 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 11:16 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.
4 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 75.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 3 | 75.0% | |
| 👍 | 1 | 25.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 4 of the 5 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 4reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 5 most recent posts we hold, published 6 August 2026 to 11 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.
#比特冲刺 #DASHBIT #Vless #非正式测试 #测速宽带 #深圳移动1000M #辽宁电信2000M ====================== ▎机场简介: 新用户注册即送 48H 免费试用；支持 AI / 流媒体解锁,线路涵 盖韩国、马来西亚、德国、香港、台湾、新加坡、日本、美国，提供电信优化，三网优化,CMI中转线路，AWS中转，以及多地区低倍率直连节点 开业时间：2026年5月3日 ▎机场优惠: 不限时 7 折优惠码：dashbit ▎机场关联: 官网：https://web.dashbit.top 频道：@dashbitTel 群组：@dashbitWWW 套餐详情: https://img.remit.ee/api/file/BQACAgUAAyEGAASHRs…
❤1
#念云 #Vless #Hy2 #ss #非正式测试 #测速宽带 #深圳电信2000M #佛山联通2000M #上海移动1000M ===================== ▎机场简介: 中规中矩，群主好说话 ▎机场关联: 官网： https://xnyun.wiki 频道: @NianyunY 群组： @xiaonyun ===================== ▎各项指标: 速度 ⭐️⭐️⭐️⭐️/5 解锁 ⭐️⭐️✨/5 拓扑 ⭐️⭐️⭐️✨/5 综合 ⭐️⭐️⭐️✨/5 ▎个人评价: 最近在自用的一个机场，性价比高，线路配置不错，目前有狗妈和阿里云，三网速度都不错，晚高也能流畅使用，解锁还需提升 ===================== #提醒 …
❤1👍1
#Fly云 #Tuic #Vless #非正式测试 #测速宽带 #深圳移动1000M #广州联通1000M ===================== ▎机场简介: 低价高速 轻松上车 ▎机场关联: 官网：http://520fly.com 频道: @fly521yun 群组： @fly520yun ===================== ▎各项指标: 速度 ⭐️⭐️⭐️/5 解锁 ⭐️⭐️/5 拓扑 ⭐️⭐️⭐️/5 综合 ⭐️⭐️⭐️/5 ▎个人评价: 定价适中 跨网还需再优化 延迟颇高 速度不大稳定 ===================== #提醒 以上测速仅代表后端网络环境速度，仅供参考，具体速度与本地网络环境有关，需要亲自评价。任何机场都有…
❤1
NBA测速联盟| NBA-Speed test pinned a photo
#鲤云 #Vless #非正式测试 #测速宽带 #深圳移动1000M ====================== ▎机场简介: 鲤云只有小流量套餐 机场为海外中转节点+协议vless 晚高峰保证4K流畅秒开 全节点解锁奈飞、迪士尼、TVer、Tiktok、 ChatGPT等众多流媒体服务 aff佣金：循环25% ▎机场关联: 官网：鲤云6.com 频道： @liyun168 ▎机场套餐: 7元50G 月付 10元100G 月付 17元200G 8折（linyun888） ====================== ▎各项指标: 速度 ⭐️⭐️⭐️✨ 解锁 ⭐️⭐️⭐️✨ 拓扑 ⭐️⭐️⭐️✨ 综合 ⭐️⭐️⭐️✨ ▎个…
Showing the 5 most recent of 5 posts we hold for @xiaozhenag04. 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 — 1,286,706 of 1,350,102entries 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.
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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“NBA测速联盟| NBA-Speed test” (@xiaozhenag04), 3,410 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/xiaozhenag04.
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.