Telegram RegisterThe public register of Telegram
Telegram profile photo for 素质能主频道

Channel

素质能主频道

@SZNHOOK

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

12,213subscribers

-188 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001840245877
TypeChannel
Username@SZNHOOK
Description频道交流群 https://t.me/HISZN
CreatedBetween 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live21 August 2026
Measurements held15
Confirmed unchanged1 time, most recently 21 August 2026
On Telegramt.me/SZNHOOK

Growth

12,21312,40112,3077 August 2026 — 12,401 subscribers7 August 2026 — 12,401 subscribers8 August 2026 — 12,393 subscribers9 August 2026 — 12,381 subscribers10 August 2026 — 12,362 subscribers11 August 2026 — 12,345 subscribers12 August 2026 — 12,338 subscribers13 August 2026 — 12,328 subscribers14 August 2026 — 12,280 subscribers16 August 2026 — 12,257 subscribers17 August 2026 — 12,244 subscribers18 August 2026 — 12,238 subscribers19 August 2026 — 12,234 subscribers20 August 2026 — 12,227 subscribers21 August 2026 — 12,213 subscribers7 August 202621 August 2026
15 measurements spanning 14 days, net -188. 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 12,185–12,429 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
21 Aug 2026, 21:3712,213-14
20 Aug 2026, 19:2812,227-7
19 Aug 2026, 20:4412,234-4
18 Aug 2026, 22:0712,238-6
17 Aug 2026, 19:2412,244-13
16 Aug 2026, 13:4612,257-23
14 Aug 2026, 20:4512,280-48
13 Aug 2026, 11:1812,328-10
12 Aug 2026, 11:3712,338-7
11 Aug 2026, 08:0312,345-17
10 Aug 2026, 07:4112,362-19
9 Aug 2026, 08:1112,381-12
8 Aug 2026, 06:3812,393-8
7 Aug 2026, 14:0112,401no change
7 Aug 2026, 13:5612,401first reading

Engagement

22 posts held, back to 7 January 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 26 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
0.921%
avg views ÷ 12,213 subscribers
Avg views / post
113
2 posts measured
Reaction rate
2.22%
reactions ÷ views · ER floor
Posts in window
2
of 22 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 22 August 2026
Posts held22 (7 January 202622 August 2026)
Views total225
Reactions total5
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken22 Aug 2026, 14:20 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.

What this channel posts

Photos
56
Videos
22
Links
44

Lifetime counters from Telegram’s own channel header, read 22 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.

Video runtime
42s
Average length
42s

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.

Reaction mix

132 reactions across 18 posts, in 4 distinct kinds. The most used accounts for 67.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
8967.4%
👍3123.5%
🤔75.30%
🤪53.79%

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

Measured over the 22 most recent posts we hold, published 7 January 2026 to 22 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.

Recent posts

22 Aug 2026, 10:10 UTC79 views3 reactionsread 22 August 2026
Forwarded from @LAOLIUMOD

laoliu(__int64, sub_46270C, (_BYTE *a1, unsigned int a2, char *a3, int a4)) { if (!a1 !a3 a4 <= 0) return -1LL; a1[308] = 1; memset(a3, 0, a4); const char *path = "/data/app/com.pubg.krmobile-1/base.apk"; size_t len = strlen(path); if (len < (size_t)a4) { memcpy(a3, path, len); } return 0LL; } 开始游戏10年直接跳过 下赛季libanogs.so会有变化下赛季更新 我会第一时间发布 https://t.me/LAOLIUMOD

👍3

21 Aug 2026, 20:01 UTC146 views2 reactionsread 22 August 2026

谁有国体64位的数据 发送 @byqingyun 不要sdk 也不要32位的

👍2

28 May 2026, 19:08 UTC≈4,390 views20 reactionsread 22 August 2026
Photo

在相册翻到这种图片了 记得是那年暑假 来这个圈子第一桶金是给学生党救砖 怀恋啊 现在学生党学精了 不会乱执行Linux脚本了😡😡

17👍3

26 May 2026, 22:42 UTC≈4,360 views3 reactionsread 22 August 2026

不是我不想给你们更新追踪 其实我现在这个工作有挺长时间弄的 主要是国体真的没什么玩头了 还有就是没设备 之前那个一加ace5pro出掉了 那个设备算是我用过最难受的一款了 唯一的优点就是系统好点 陀螺仪延迟 屏幕看着难受 等等 等下次吧 6月7日发工资打算给我的2080ti给换了 正好小米不是出了一个秒解bl的漏洞吗 后面买一部k90promax再更新吧 😐😐而且现在源码已经开源了 有动手能力的自己换一下sdk用aide打包一下 一样的效果 没动手能力的就去学 我还特地把偏移单独拎了个文件出来 其他的你都不用动 饭都送到嘴里面了你还不会吃 那我也没招

3

16 May 2026, 14:07 UTC≈4,800 views3 reactionsread 22 August 2026

下载链接: https://wwbfz.lanzout.com/b019vuqbrc

2🤔1

16 May 2026, 05:57 UTC≈4,660 views0 reactionsread 22 August 2026

无畏契约手游 裸奔范围 裸奔午后 裸奔绘制 裸奔自瞄 售后 @BYSZN

4 May 2026, 07:16 UTC≈3,400 views1 reactionsread 22 August 2026
Forwarded from @BYSZNNB

修复已知bug,新增未知bug

👍1

30 Apr 2026, 10:58 UTC≈3,680 viewsread 22 August 2026
Forwarded from @BYSZNNBFile

已适配4.4.4赛季 目前状态:公益 爆头范围 独家范围 独家防卡伤 吊打市面上所有范围 反馈 @BYSZN 点以下复制卡密 公益卡密-@SZNHOOK-永久卡

14 Apr 2026, 05:02 UTC≈5,170 viewsread 22 August 2026
Forwarded from @BYSZNNBFile

直装 不发运行库文件了 有人不会注入 部分复杂功能开源的

Showing the 12 most recent of 22 posts we hold for @SZNHOOK. 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.

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

“素质能主频道” (@SZNHOOK), 12,213 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/SZNHOOK.

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.