qihuan5.5.sh 优化骨骼 优化人机骨骼 修复自瞄圈和自由相机不能保存配置问题 优化帧率 执行后可看到注册账号网站需购买会员。 已经添加毒舌端口。 🩵➡️ @qihuaiSK
❤1👍1

Channel
@qihuaiSK
On this record: Topic · Previous handles · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
2,388subscribers
+454 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1004384954934 |
|---|---|
| Type | Channel |
| Username | @qihuaiSK |
| Created | Between 1 June 2026 and 2 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 12 September 2026 |
| On Telegram | t.me/qihuaiSK |
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 15 September 2026 and assigned it the closest of 31 fixed categories, at 35% 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.
@qihuaiSK was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Sept 2026, 00:21 | 2,388 | -2 |
| 7 Sept 2026, 06:41 | 2,390 | -1 |
| 2 Sept 2026, 10:45 | 2,391 | -4 |
| 30 Aug 2026, 10:24 | 2,395 | +4 |
| 27 Aug 2026, 13:43 | 2,391 | +34 |
| 24 Aug 2026, 10:07 | 2,357 | +45 |
| 20 Aug 2026, 09:53 | 2,312 | +8 |
| 17 Aug 2026, 20:14 | 2,304 | +60 |
| 15 Aug 2026, 01:27 | 2,244 | +110 |
| 11 Aug 2026, 12:22 | 2,134 | +166 |
| 8 Aug 2026, 11:33 | 1,968 | +34 |
| 7 Aug 2026, 15:17 | 1,934 | no change |
| 7 Aug 2026, 15:01 | 1,934 | first reading |
16 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 1 page 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 16 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
89 reactions across 10 posts, in 5 distinct kinds. The most used accounts for 46.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👎 | 41 | 46.1% | |
| ❤ | 27 | 30.3% | |
| 👍 | 12 | 13.5% | |
| 🖕 | 7 | 7.87% | |
| 💅 | 2 | 2.25% |
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 10 of the 16 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 89 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 2 August 2026 to 7 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.
qihuan5.5.sh 优化骨骼 优化人机骨骼 修复自瞄圈和自由相机不能保存配置问题 优化帧率 执行后可看到注册账号网站需购买会员。 已经添加毒舌端口。 🩵➡️ @qihuaiSK
❤1👍1
马上更换服务器,可能你们要等几分钟才能玩
Channel name was changed to «777»
Channel photo updated
大家在这里交流
qihuan4.8.sh 使用账号密码登陆,请开通会员 新增战斗模式只显示敌人血量手持骨骼距离 优化模型漏打 新增漏打部位多调节 优化自动打矿(目前不支持自动避开人机和动物)
👎10👍5❤1
防止破解版传播,我会关闭评论,请认准正常。 我在加急防破解。 晚点发布新版
👎20👍4💅2
Photo, posted without a caption
👎6❤5
📞爱老母牛
🖕7
新增建筑门建筑墙血量显示 优化领地显示范围优化成员显示 因为被敌人瞄准提示 新增敌人拆家提示 因为物资显示背景开关和大小调节 优化漏打 优化人机骨骼
新增追踪 新增绘制远距离变小按钮 新增智能追踪预瞄 新增智能瞄准 新增名单滑条 新增绘图2(队伍数字) 防举报配合追踪(登陆页面启动程序开启防举报) 优化自瞄 还有啥忘记了 追踪请用小号使用 最新包发布在qq群(进群请提供卡密) 追踪仅供周卡使用
❤12👎4
随便破,我一天更新5次
❤2
Showing the 12 most recent of 16 posts we hold for @qihuaiSK. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“777公益项目” (@qihuaiSK), 2,388 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/qihuaiSK.
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.