可正常更新
👍1
Signed 迂回

Channel
@yhhook7
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
283subscribers
+0 since we began measuring on 29 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003822087511 |
|---|---|
| Type | Channel |
| Username | @yhhook7 |
| Created | 10 February 2026 — measured — dated from the channel’s first post |
| First recorded | 29 August 2026 |
| Last confirmed live | 8 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 8 September 2026 |
| On Telegram | t.me/yhhook7 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Sept 2026, 14:02 | 283 | -2 |
| 29 Aug 2026, 13:25 | 285 | +2 |
| 29 Aug 2026, 05:00 | 283 | no change |
| 29 Aug 2026, 04:45 | 283 | first reading |
9 posts held, back to 10 February 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 9 posts for this entry, the most recent from 1 August 2026. An engagement rate over an empty window would be a number about nothing.
3 reactions across 3 posts, in 3 distinct kinds. The most used accounts for 33.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 33.3% | |
| 👍 | 1 | 33.3% | |
| 😁 | 1 | 33.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 4 of the 9 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 3 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 10 February 2026 to 1 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.
可正常更新
👍1
Signed 迂回
当前时间:2026-08-01 18:17:55 PUBG体验服Android新版本发布!(版本号:4.6.1.21395) Android 32 位: https://web.gpubgm.com/m/AOS_Beta4.6.0-b.1_No10_4.6.1.21390_Shipping_Google_CE.shell.signed.apk Android 64 位: https://web.gpubgm.com/m/AOS_Beta4.6.0-b.1_No9_4.6.1.21395_Shipping_Google_CE.shell.signed.apk 正常版本国体昨天那个听说是泄露的所以点开好友列表卡成ppt
❤1
Signed 迂回
加速已适配4.6.1
Signed 迂回
在蓝圈的时候 趴下来如果觉得卡顿就跳一下 反复如此出蓝圈的时候就不会卡顿了
Signed 迂回
游戏中记得打满饮料使用加速 并且全程趴下 可以使用高跳 但不能一次跳多次 64位加速自改 --- 改的越大越快 120帧 自改 0.0015 - 0.0017 90帧 自改 0.0020 - 0.0025 60帧 自改 0.0030 - 0.0035 120帧 自改慢动作 0.85 - 1.2 90帧 自改慢动作 1.2 - 1.5 60帧 自改慢动作 1.5 - 1.8 拉回可能是你 速度 改的太大了 可以通过以上配置 适当修改 普通 高跳 配置 自改 推荐 高跳高度 + 防摔大小 以下为推荐自改 6000 9 4500 6 可以适当修改 注 : 不要超过 8000 不然不容易跳起来 注 : 请开启陀螺仪 加 自改慢动作 超级 高跳 配置 自改 推荐 七图 / 五图 加速 并开启搭配的 超级高跳 高跳高度 防摔大小 以下为推荐自改 13000 …
Signed 迂回
加速等赛季更新
Signed 迂回
适配4.6.1 64bit 使用说明点我
Signed 沈泽
😎迂回国体加速😎 😏拉回请根据自己帧率更改速度 🤔点我查看如何自改加速和高跳 🤤点我查看如何解决加速卡脚问题 😷局内必须要开防标记否则标记 🤤当前版本4.6.1 公益状态 ---------------------------------------------- 🥵发视频打标签 #迂回国体加速 😝点击我下载加速安装包 🤪点击我下载范围安装包 🥰加速问题 点我 😚反馈问题 点我 😍点我加入官方频道 😍点我加入交流频道
😁1
Channel created
Showing the 9 most recent of 9 posts we hold for @yhhook7. 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 8 September 2026 — this entry's latest reading, not the date you are reading this.
“迂回加速主频道” (@yhhook7), 283 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/yhhook7.
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.