小骨不打算做解密,莫要反馈了 解密早晚被修,所以不做是最好的结果,也是为粉丝们负责🟩
👍24❤1
Signed 喻安

Channel
@Xiaogu_zcr521
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
24,419subscribers
+4,633 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002778695216 |
|---|---|
| Type | Channel |
| Username | @Xiaogu_zcr521 |
| Created | Between 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 32 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/Xiaogu_zcr521 |
Other / unclassifiable — 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 86% 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 |
|---|---|---|
| 17 Sept 2026, 21:19 | 24,419 | +237 |
| 15 Sept 2026, 15:58 | 24,182 | +143 |
| 14 Sept 2026, 02:41 | 24,039 | +31 |
| 12 Sept 2026, 11:22 | 24,008 | +146 |
| 10 Sept 2026, 05:58 | 23,862 | +340 |
| 6 Sept 2026, 21:17 | 23,522 | +372 |
| 4 Sept 2026, 08:36 | 23,150 | +160 |
| 2 Sept 2026, 23:13 | 22,990 | +143 |
| 1 Sept 2026, 17:34 | 22,847 | +104 |
| 31 Aug 2026, 20:57 | 22,743 | +304 |
| 30 Aug 2026, 17:43 | 22,439 | +133 |
| 29 Aug 2026, 15:16 | 22,306 | +220 |
| 28 Aug 2026, 16:33 | 22,086 | +242 |
| 27 Aug 2026, 19:44 | 21,844 | +233 |
| 26 Aug 2026, 22:59 | 21,611 | +136 |
| 25 Aug 2026, 21:39 | 21,475 | +176 |
| 24 Aug 2026, 22:13 | 21,299 | +198 |
| 23 Aug 2026, 08:47 | 21,101 | +137 |
| 21 Aug 2026, 19:34 | 20,964 | +141 |
| 20 Aug 2026, 14:52 | 20,823 | first reading |
64 posts held, back to 30 July 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 56 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 2 September 2026 |
|---|---|
| Posts held | 64 (30 July 2026 – 2 September 2026) |
| Views total | 87,910 |
| Reactions total | 371 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 11:56 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.
Measured directly from 4 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.
1,421 reactions across 64 posts, in 19 distinct kinds. The most used accounts for 69.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 989 | 69.6% | |
| ❤ | 358 | 25.2% | |
| 😭 | 16 | 1.13% | |
| 🤔 | 14 | 0.985% | |
| 😍 | 8 | 0.563% | |
| 👏 | 7 | 0.493% | |
| 🌭 | 6 | 0.422% | |
| 😁 | 4 | 0.281% | |
| 🙊 | 3 | 0.211% | |
| 🥰 | 3 | 0.211% | |
| 🍾 | 2 | 0.141% | |
| 🏆 | 2 | 0.141% | |
| 😇 | 2 | 0.141% | |
| 🤩 | 2 | 0.141% | |
| ☃ | 1 | 0.07% | |
| ❤🔥 | 1 | 0.07% | |
| 😴 | 1 | 0.07% | |
| 🤯 | 1 | 0.07% | |
| 🦄 | 1 | 0.07% |
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 64 of the 64 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,421 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 64 most recent posts we hold, published 30 July 2026 to 2 September 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.
小骨不打算做解密,莫要反馈了 解密早晚被修,所以不做是最好的结果,也是为粉丝们负责🟩
👍24❤1
Signed 喻安
如果哪天大家在网上看到我的果照,请不要嘲笑我,那是我曾经以为被爱了.💜
👍33😭10😍5🍾2🤩2
Signed 喻安
准的一批兄弟们,不仅支持守约,还支持各种英雄🌟
👍18❤7
Signed 喻安
🌟小骨公益王者内核(无解密) 1.0.1 🟢 更新内容 ⬇️: 1🟢用户卡密输入错误自动把卡密配置里面的卡密清零,避免后续都无法使用 2🟢修复地图方框不显示 3🟢把上帝改成自动修改,每局自动修改 4🟢优化自瞄算法,更准、更牛逼 5🟢修复自瞄有的时候打不到人 6🟢更新终端UI显示 7🟢修复自瞄有的时候不触发自瞄 8🟢将自瞄算法尽力改成可以瞬发的 配置文件➡️: /data/adb/小骨 卡密➡️: @Xiaogu_zcr521 有任何Bug评论反馈,看见我会尽力修复,感谢各位支持,可裸奔,包稳定🦖
👍14❤12😁1
Signed 喻安
🎮小骨公益王者内核(无解密) 拥有以下📥特点 0.01 1.极强的稳定性,只行为不外挂 2.功耗极低,手机不会卡,不发烫 3.内置无敌上帝,贴合真实感觉 4.内置无敌自瞄,自动适配二技能 5. UI比较经典,无花里胡哨 🫥 6.支持自动斩杀/自动惩戒/换装等 ⭐ 卡密: @Xiaogu_zcr521 部分驱动读取无法读取到,还在适配中 我建议大家都可以尝试一下,有任何可以问题反馈,谢谢!🌟
👍20❤10
Signed 喻安
小骨王者内核即将出道🫥
👍42🤔6👏3
Signed 喻安
新版换密钥教程,根据视频操作就行🫥
👍23❤6
Signed 喻安
送你们一个TG号😡 +918955629190----https://jiema.didiapi.uk/getcode?id=24483d91-a8e0-4c13-9d2a-8b2db51fb334 8.30 11.08还能用, 还能登录
👍27❤4
Signed 喻安
我辟谣一下,我看见网上都在说Zcode配DeepSeek最强 实则不然,经过测试Zcode Bug一大堆,模型都不知道自己要改什么 同一个任务,同一个模型,同一个提示词,Zcode跑了一个小时半,跑不出来任何东西,Codex20分钟给你解决完 一天一个直追,一天一个碾压,跑分超过了这个超过了那个,实际体验下来呢,拉中之王 目前我用这么多的编程框架,Codex用起来最舒服最聪明 不要再去网上听他们瞎说,乖乖用Codex吧
👍28❤12☃1
Signed 喻安
Sy王者11.4.1.36正式服美化8.29_0510.zip ✅更新内容 🟢修复夏侯惇霜北刀12技能动作 🟢修复马超神骥逐星野持枪强化特效 🟢修复元歌诡秘之主24技能特效和3技能动作 🟢修复暃朽木白哉1技能特效延迟和3技能特效补全 🟢修复百里守约暗夜巡卫123技能立正 🟢修复百里玄策2技能蓄力特效和钩子特效补全 🟢修复达摩黄金狮子座1技能特效丢失和2技能特效延迟 🟢修复廉颇撼地雄心123技能抽搐 🟢修复凯冥王哈迪斯大招翅膀和2技能指示圈 🟢修复长时间游玩后皮肤美化可能失效的问题 🟢修复偶尔掉帧的问题 🟢修复mt执行版本偶尔killed的问题 🟢修复强制刷新率无效的问题 🟢修复概率玩几小时后掉皮肤效果的问题 🟢增加检测游戏版本号校验 🟢移除皮肤配置1234 ✔️美化or自瞄订阅链接 https://shop.bromk.cn/shop/RGVJ30K7 📱点我加入QQ群聊【Syyyyy】
❤10👍1
Signed Sy王者主频道
这是一个最基础的UI模板🌟 可以让AI在这上面进行改,添加功能,实现功能等 开源: @Xiaogu_zcr521 个人感觉这套UI非常不错,底子还好,很适合作为底层模板 #源码 #小骨 #开源
👍24❤7🦄1
Signed 喻安
游戏裸奔反馈 8.28 官方卡网 🔗 zcr521.top 支持🎮🎮🎮🎮🎮❤️等所有腾讯游戏 祝你早日圆梦大红大国梦 售后 @zcr9178 来点反馈图 😀
👍11❤6
Signed 喻安
Showing the 12 most recent of 64 posts we hold for @Xiaogu_zcr521. 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.
@Xiaogu_zcr521 edited 6 posts 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 5 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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“zcr521环境” (@Xiaogu_zcr521), 24,419 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/Xiaogu_zcr521.
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.