Telegram RegisterThe public register of Telegram
Telegram profile photo for 小羽神无广频道

Channel

小羽神无广频道

@ChinesASDE

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

314subscribers

+21 since we began measuring on 3 November 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003997516771
TypeChannel
Username@ChinesASDE
Created27 September 2026 — measured — dated from the channel’s first post
First recorded3 November 2026
Last confirmed live12 November 2026
Measurements held3
Confirmed unchanged1 time, most recently 12 November 2026
On Telegramt.me/ChinesASDE

Growth

293314303.53 November 2026 — 293 subscribers3 November 2026 — 294 subscribers12 November 2026 — 314 subscribers3 November 202612 November 2026
3 measurements spanning 9 days, net +21. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 290–317 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Nov 2026, 13:07314+20
3 Nov 2026, 22:27294+1
3 Nov 2026, 06:22293first reading

Engagement

10 posts held, back to 27 September 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.

ERR · 30 days
20.4%
avg views ÷ 314 subscribers
Avg views / post
64.0
2 posts measured
Reaction rate
2.34%
reactions ÷ views · ER floor
Posts in window
2
of 10 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 30 October 2026
Posts held10 (27 September 2026 – 30 October 2026)
Views total128
Reactions total3
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Nov 2026, 06: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.

Reaction mix

16 reactions across 8 posts, in 2 distinct kinds. The most used accounts for 68.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1168.8%
❤531.3%

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 8 of the 10 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 16 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 10 most recent posts we hold, published 27 September 2026 to 30 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.

Recent posts

Telegram’s own ‘edited’ marker: 0 of 2 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

30 Oct 2026, 02:16 UTC63 views1 reactionsread 3 November 2026
Forwarded from @ChinesASDF

小羽神和平美化10.25更新日志 卡密: HP-XYS-2026-5-14 ------------------------------------- 1.修复逻辑问题 2.减少闪退概率 3.不强制更新喜欢玩哪个版本就玩哪个版本 😙注:手持配置可以写新版自适应也可以写旧版格式 ------------------------------------- 有你们在 我就在 美化下载链接:https://pan.baidu.com/s/1I6e2-hlx6D6VM5T0uGpD9g?pwd=6666 提取码6666 ------------------------------------- QQ群1059647786 官方频道:@ChinesASDF 交流群组:@ChinesASDB 无广频道:@ChinesASDE 美化使用教程点我 看完能给我点个赞吗 制作不易 爸爸们多多发快手支持一下吧 🙏 -------------------…

👍1

Signed RahøøL

30 Oct 2026, 02:16 UTC65 views2 reactionsread 3 November 2026
Forwarded from @ChinesASDF

小羽神1.25瓦手美化9.22 1.为用户服务 删除了卡密验证! 2.再次修复一些bug 3.6.12.58以下的都刷6.12.23,只有6.12.58刷6.12.58 4.解决大部分人数组获取不到的问题 5.驱动过验证在驱动压缩包 6.使用前你的标配手枪是不能带皮肤的 7.枪皮配置.h是绝对不能改的改了这个名字否则读取不到重复下载它后面会增加括号和必须删掉 8.驱动在频道和qq群文件 驱动是RT-QX 9.正常执行报错白色英文字母就是因为你的配置格式乱改导致读取失败 10.😙😙😙我之前就说过了瓦手美化封号一小时 自行测试封号了别来叫 如果你有皮肤不是贴图没的话可以拿那个皮肤改其他的皮肤是不会封号的❗️❗️❗️ 注意:配置和美化要放同一个路径否则读取不到配置 !!! 下载前一定要看下面的选项示例 不要没有看跟个脑*一样不会用就来问 少给我带一些麻烦事 就是对我最好的尊重 !!! 下载前不看前面的选项出问题了还来问你等的死全家 …

❤1👍1

Signed RahøøL

20 Oct 2026, 16:49 UTC212 viewsread 3 November 2026
Forwarded from @ChinesASDF

小羽神和平美化10.2更新日志 卡密: HP-XYS-2026-5-14 ------------------------------------- 1.修复一下旧版格式删除或注释了开火检视打击等还是能被自适应算法自动写入 2.不强制更新喜欢玩哪个版本就玩哪个版本 😙注:手持配置可以写新版自适应也可以写旧版格式 ------------------------------------- 也是将近一个月没更新了最近在厂里没时间 请大家谅解 有你们在 我就在 美化下载链接:https://pan.baidu.com/s/1I6e2-hlx6D6VM5T0uGpD9g?pwd=6666 提取码6666 ------------------------------------- QQ群1059647786 官方频道:@ChinesASDF 交流群组:@ChinesASDB 无广频道:@ChinesASDE 美化使用教程点我 看完能给我点…

Signed 小羽神(没回就是有事或者在睡觉)

17 Oct 2026, 11:43 UTC300 views3 reactionsread 3 November 2026
Forwarded from @ChinesASDF

小羽神和平美化10.17更新日志 卡密: HP-XYS-2026-5-14 ------------------------------------- 1.更新自适应手持配置一行美化所有配件更多介绍手持配置文件里 2.减少闪退概率 3.不强制更新喜欢玩哪个版本就玩哪个版本 😙注:手持配置可以写新版自适应也可以写旧版格式 ------------------------------------- 也是将近一个月没更新了最近在厂里没时间 请大家谅解 有你们在 我就在 美化下载链接:https://pan.baidu.com/s/1I6e2-hlx6D6VM5T0uGpD9g?pwd=6666 提取码6666 ------------------------------------- QQ群1059647786 官方频道:@ChinesASDF 交流群组:@ChinesASDB 无广频道:@ChinesASDE 美化使用教程点我 看完…

👍3

Signed RahøøL

27 Sept 2026, 16:20 UTC≈1,100 views3 reactionsread 3 November 2026

你们好

👍3

Signed 小羽神(没回就是有事或者在睡觉)

27 Sept 2026, 16:17 UTC538 views1 reactionsread 3 November 2026
Forwarded from @ChinesASDF

小羽神和平美化9.28更新日志 1.增加地铁头盔背包智能判断 2.增加QX驱动读写 自由选择系统读写或驱动读写 系统读写就是原来没有加驱动的读写 3.不强制更新 注:和平美化没检测其实选不选驱动读写都一样 只是我闲的没事干就想加而已 ---------------------------- 美化功能介绍 1.和平经典美化 2.和平地铁美化 3.局内美化 4.手持美化 5.载具美化 6.秒刷启用 7.动态广角 8.输出代码 1、2选项为全局遍历 可以拿来改载具,动作,衣服,背包,枪械等等 缺点是对方穿了你同样的皮肤、衣服、背包头盔,可能会透明人,其他的不会 3、4、5为局内自身美化 6是秒刷的开关开了局内自身美化想秒刷、不脱配件、不脱甲那就开秒刷 7广角 8是输出游戏的代码要改皮肤配置啥的可以在里面找 ---------------------------- 下载链接:https://pan.baidu.com/s/1I6e2-…

❤1

27 Sept 2026, 16:16 UTC266 views1 reactionsread 3 November 2026
Forwarded from @ChinesASDFPhoto

Photo, posted without a caption

❤1

27 Sept 2026, 16:15 UTC785 views2 reactionsread 3 November 2026
Forwarded from @ChinesASDF

和平小羽神and鸭梨公益云端 为什么选择云端? 云端通过云端服务器计算游戏下发数据包从而实现拦截替换返回正常无异常数据达到稳定连打不动任何内存纯云端统计返还数据 有效解决断点追踪特征拉闸问题 有效解决游戏对账号下发的闪框加密/无效果加密 无视任何加密可搭配全网公益项目游玩 你还在为经常小黑屋/隔离/禁网而烦恼吗 ? 不妨试试云端给你一个全新的体验 采用云端物理机母机高速响应不会漏包丢包 完美承受大量人员 现已开启大批量公益测试 0成本 游玩 耳听为虚 眼见为实 不吹牛逼不欺骗用户 有效拦截反作弊下发数据包 可搭配半火随便游玩 全网都在吃举报禁网 缩圈禁网 不妨试试云端 给你的账号多添一份保障 注:安装了和平和平端口要卸载否则包名冲突 账号:bzkj 密码:bzkj 官方电报: @ChinesASDF 反馈联系: @ChinesASDT 下载链接:https://pan.baidu.com/s/1Xk84VDoT07eXvn8G…

👍2

27 Sept 2026, 16:15 UTC127 views3 reactionsread 3 November 2026
Forwarded from @ChinesASDF

🐟小羽神下载导航and广告位🐧 ☺️--------------🤔 😱点击下载和平配置美化🤕 🥰点击下载王者荣耀美化🤣 🤐点击下载和平精英端口😉 😏点击下载瓦手公益端口😚 🤔点击进入QQ群🤓 😍和平通杀人脸😘 😡小羽神主频道👻 😇@ChinesASDF🥶 👁️无广频道 @ChinesASDE🤘 😏全都是公益项目收费直接被大卡车🤣 👾--------------👾 置顶频道广告位↓↓↓ 精品飞机号 佐菲租号铺

❤2👍1

Showing the 10 most recent of 10 posts we hold for @ChinesASDE. 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.

Forward network

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.

Mentions

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.

Cite this entry

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 November 2026 — this entry's latest reading, not the date you are reading this.

“小羽神无广频道” (@ChinesASDE), 314 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/ChinesASDE.

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.