#频道互推 #群组推荐 优质-破解软件-分享基地 来一点医学科学前沿 精选音乐收藏馆 无损音乐分享频道 机场订阅节点VPN分享社 🅥 资源分享 - 软件|网站|工具|破解 机器人收藏夹中文圈玩转bot 异次元&里番动漫 小小溪Channel
👍1

Channel
@xiaoxinv
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
21,942subscribers
-284 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001837247909 |
|---|---|
| Type | Channel |
| Username | @xiaoxinv |
| 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 | 49 |
| Confirmed unchanged | 1 time, most recently 28 October 2026 |
| On Telegram | t.me/xiaoxinv |
Software piracy — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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, 01:48 | 21,942 | +20 |
| 26 Oct 2026, 22:55 | 21,922 | -8 |
| 25 Oct 2026, 22:26 | 21,930 | +3 |
| 24 Oct 2026, 23:39 | 21,927 | -2 |
| 24 Oct 2026, 02:39 | 21,929 | +9 |
| 23 Oct 2026, 00:16 | 21,920 | -2 |
| 21 Oct 2026, 21:57 | 21,922 | +14 |
| 19 Oct 2026, 12:50 | 21,908 | +6 |
| 18 Oct 2026, 12:05 | 21,902 | +2 |
| 17 Oct 2026, 14:00 | 21,900 | -3 |
| 16 Oct 2026, 13:47 | 21,903 | -10 |
| 15 Oct 2026, 15:16 | 21,913 | -4 |
| 14 Oct 2026, 11:46 | 21,917 | -8 |
| 13 Oct 2026, 01:41 | 21,925 | -14 |
| 8 Oct 2026, 15:17 | 21,939 | -1 |
| 4 Oct 2026, 01:21 | 21,940 | -26 |
| 25 Sept 2026, 06:55 | 21,966 | -34 |
| 18 Sept 2026, 20:00 | 22,000 | -13 |
| 16 Sept 2026, 09:39 | 22,013 | +5 |
| 14 Sept 2026, 16:19 | 22,008 | first reading |
26 posts held, back to 5 December 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 69 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.
| Window | Rolling 30 days · latest post in window 11 October 2026 |
|---|---|
| Posts held | 26 (5 December 2024 – 11 October 2026) |
| Views total | 1,962 |
| Reactions total | 2 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Oct 2026, 08:31 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.
472 reactions across 23 posts, in 10 distinct kinds. The most used accounts for 39.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 185 | 39.2% | |
| ❤ | 172 | 36.4% | |
| 🥰 | 37 | 7.84% | |
| 👎 | 26 | 5.51% | |
| 🔥 | 24 | 5.08% | |
| 🤡 | 15 | 3.18% | |
| 🌚 | 8 | 1.69% | |
| 👏 | 3 | 0.636% | |
| 🤔 | 1 | 0.212% | |
| 🤬 | 1 | 0.212% |
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 24 of the 26 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 472 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 26 most recent posts we hold, published 5 December 2024 to 11 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.
#频道互推 #群组推荐 优质-破解软件-分享基地 来一点医学科学前沿 精选音乐收藏馆 无损音乐分享频道 机场订阅节点VPN分享社 🅥 资源分享 - 软件|网站|工具|破解 机器人收藏夹中文圈玩转bot 异次元&里番动漫 小小溪Channel
👍1
#频道互推 #群组推荐 Fang的资源分享群 App Store 限免应用 小众机场测评 折腾IOS内测|限免频道 DLsite Steam黄油下载 【离港一二线机场收录&测评】 金十数据 闪电资讯 APPDO的互联网记忆 动画&插画分享(NSFW)
❤1
#频道互推 #群组推荐 折腾搞机频道New 蜻蜓资源分享-科技‖软件 折腾实验室频道 金十数据 闪电资讯 严选君综合福利社 枫叶の破解软件分享 利器软件工具与开源项目 趣味播报 老司机之家 弈泽 - 审计级财报分析系统
❤1
#频道互推 #群组推荐 朱颜别镜 | 妹子图 | 美女图 严选君综合福利社 推个鸡场|优质小而美机场推荐 白嫖分享社 | 综合类白嫖资源 机器人收藏夹中文圈玩转bot 趣味播报 分享社_破解软件/公益机场VPN 电子书图书馆 白嫖小仓库 丨 抽奖福利之家 弈泽 - 审计级财报分析系统
#频道互推 #群组推荐 汉堡TG公益代理|订阅节点分享 QQ资源岛软件 利器软件工具与开源项目 资源分享客栈-分享各种东西 深度 好文 (付费文章共享) 机场订阅节点VPN分享社 🅥 折腾IOS内测|限免频道 精选壁纸美图|风景美人acg 折腾实验室频道 电报频道&群组索引
#频道互推 #群组推荐 B站充电视频分享 机器人收藏夹中文圈玩转bot 墨理破解软件免费翻墙节点分享社 𝕎𝔼电报频道精选推荐 折腾IOS内测|限免频道 某咕咕机场测评站(真实机场测评) DLsite Steam黄油下载 资源分享 - 软件|网站|工具|破解 国产电视剧频道(每日更新) 电报频道&群组索引
#频道互推 #群组推荐 资源分享客栈-分享各种东西 机场订阅节点VPN分享社 🅥 频道藏馆 熊猫资源分享—破解软件/影视分享 多网盘影视资源分享 利器软件工具与开源项目 夸克网盘短剧资源自取 机器人收藏夹中文圈玩转bot 枫叶の破解软件分享 电报频道&群组索引
❤1
#频道互推 #群组推荐 图书杂志资源免费分享 墨理破解软件免费翻墙节点分享社 (NSFW)mmd分享 某咕咕机场测评站(真实机场测评) txt爽文小说 APPDO的互联网记忆 安卓软件游戏破解资源分享 今日有羊毛 纵享丝滑(丝袜精选) 电报频道&群组索引
❤1
自由笔记限免 ipad上很好用的一款笔记软件,适合学生党,再次迎来了限时领取永久会员活动,今天11:30结束,还有一个小时,不同设备端同一个邮箱登陆会员会同步,详细领取步骤:用邮箱注册登录>打开软件个人账号中心即可领取永久会员 #ios #限免 #笔记 项目地址: ios下载
❤29👍8🥰3🤬1
Hailsey Bot 一款永久免费小火箭账号共享共享机器人,24h自动更新,实时检测账号可用性,点击账号密码可自动复制,仅限登陆到苹果手机App Store,请勿登录iCloud,否则锁机概不负责 #ios #小火箭 #共享账号 项目地址: 点此启用
👍23❤18🥰5🌚2
MYTV player 一款安卓端m3u播放器,目前正在限免阶段,有安卓手机的感兴趣的可以下载内购一下,挺好使,限免机会不多 #m3u8 #播放器 #限免 #Android 项目地址: 点此下载
❤12👍8🔥4🥰2🤔1
好记性密码管理 一款ios商店伪装商家的影视app橘子影视,实测无广告,有观影历史,可看最新电视剧、综艺、动漫、短剧、电视直播等 使用方法:打开APP,添加新密码,第一排输入22222,点击Save Password出现提示重启APP即可 #影视 #app #ios 项目地址: 点此下载
❤14🤡7👍6👎3🔥2🥰1
Showing the 12 most recent of 26 posts we hold for @xiaoxinv. 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.
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 28 October 2026 — this entry's latest reading, not the date you are reading this.
“小新の资源库|免费vpn|破解软件” (@xiaoxinv), 21,942 subscribers as measured 28 October 2026. Telegram Register, tgregister.com/channel/xiaoxinv.
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.