范围配置列表 用户列表 南坤配置 6 5 6 6 刺客配置 7 5 5 6
Signed 一只鼠.

Channel
@YZSS3
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
167subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004366668896 |
|---|---|
| Type | Channel |
| Username | @YZSS3 |
| Created | Between 1 June 2026 and 21 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/YZSS3 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 15:47 | 167 | no change |
| 7 Aug 2026, 17:31 | 167 | first reading |
20 posts held, back to 21 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 1 pageof 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. It is computed over the 10 of 20 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 3 August 2026 |
|---|---|
| Posts held | 20 (21 July 2026 – 3 August 2026) |
| Views total | 6,633 |
| Reactions total | 46 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 15:47 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.
Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 1 video 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.
46 reactions across 10 posts, in 4 distinct kinds. The most used accounts for 34.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 16 | 34.8% | |
| 👍 | 16 | 34.8% | |
| 🌭 | 7 | 15.2% | |
| 😱 | 7 | 15.2% |
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 20 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 46reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 21 July 2026 to 3 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.
范围配置列表 用户列表 南坤配置 6 5 6 6 刺客配置 7 5 5 6
Signed 一只鼠.
范围已更换偏移 偏移显示200以上 基本上都是安全的 也可以在大厅开一遍 然后再去局内开一下 过移速 已添加完整的哈希校验
👍3
Signed 一只鼠.
目前没有任何问题 换了欧服直接无敌稳定还不追风
Signed 一只鼠.
加速过移速 有时间再更新一下 或者适配印度 哈希校验已经搞好了 尝试解决亚服封号问题
❤4
Signed 一只鼠.
封号的不选亚洲服务器就行亚洲有一个检测
Signed 一只鼠.
这个置顶标题 我会员掉了 改了 全部又要重新弄 我就不换了
Signed 一只鼠.
已更新没有任何异常的PUBGM4.5正式服加速
❤3
Signed 一只鼠.
现在加速是正常玩的 框架目前用不了 有时间更新直装
Signed 一只鼠.
已更新循环killGG/HOOK检测 隐藏应用列表检测 防模糊 搭配不了GG美化的用中野三玖或者其他不是GG的美化 已更换没任何禁令的过移速
❤2
Signed 一只鼠.
这个过移速确实没问题 但是我怕我更新出来了 一堆人模仿更新
👍3
Signed 一只鼠.
但是没更新我得测试
Signed 一只鼠.
已经解决加速7天问题
Signed 一只鼠.
Showing the 12 most recent of 20 posts we hold for @YZSS3. 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.
Citation-graph rank — 392,709 of 1,160,990entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“鼠窝” (@YZSS3), 167 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/YZSS3.
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.