Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝑌𝑖𝑋𝑢𝑎𝑛的储物间

Channel

𝑌𝑖𝑋𝑢𝑎𝑛的储物间

@zsH0HQfk

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

303subscribers

+14 since we began measuring on 6 September 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001896634984
TypeChannel
Username@zsH0HQfk
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 September 2026
Last confirmed live9 September 2026
Measurements held3
Confirmed unchanged1 time, most recently 9 September 2026
On Telegramt.me/zsH0HQfk

Growth

2893032966 September 2026 — 289 subscribers8 September 2026 — 289 subscribers9 September 2026 — 303 subscribers6 September 20269 September 2026
3 measurements spanning 3 days, net +14. 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 287–305 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Sept 2026, 17:01303+14
8 Sept 2026, 06:22289no change
6 Sept 2026, 23:17289first reading

Engagement

17 posts held, back to 8 August 2026the 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.

ERR · 30 days
101.2%
avg views ÷ 303 subscribers
Avg views / post
307
11 posts measured
Reaction rate
0.327%
reactions ÷ views · ER floor
Posts in window
11
of 17 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. It is computed over the 3 of 11 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 1 September 2026
Posts held17 (8 August 20261 September 2026)
Views total3,374
Reactions total3
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Sept 2026, 06:22 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

Video runtime
46s
Average length
46s

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

3 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 66.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍266.7%
🤣133.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 3 of the 17 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 17 most recent posts we hold, published 8 August 2026 to 1 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.

Recent posts

1 Sept 2026, 01:46 UTC291 views1 reactionsread 8 September 2026

魔怔了,酷安小编也司马,这玩意也要给所有人发个app通知消息

🤣1

1 Sept 2026, 01:45 UTC273 viewsread 8 September 2026
Forwarded from @saltplayerupdatePhoto

早上打开酷安,我是不是没睡醒......

31 Aug 2026, 12:46 UTC278 views2 reactionsread 8 September 2026

mihomo sniffer模块,一些参数的详细说明 force-dns-mapping 是控制是否嗅探的一个参数,默认下只会嗅探无法获得域名的流量,当强制开启他,则会嗅探由 DNS 映射逻辑获得的域名(不包括 SOCKS5、HTTP、SS 和 TUIC 等能直接传输域名的入站协议),也就是开启他就会强制嗅探所有透明代理流量 至于还有个 parse-pure-ip 则在支持域名传输入站的协议上强制嗅探所有无域名流量。 https://github.com/MetaCubeX/mihomo/issues/399#issuecomment-1437080847 #mihomo #clash

👍2

24 Aug 2026, 10:47 UTC341 viewsread 8 September 2026

mihoyo坏事做尽😡,什么叫我连主线任务里的怪都打不过,唉数值膨胀,过个主线还得降世界等级

23 Aug 2026, 04:15 UTC290 viewsread 8 September 2026
Photo

https://forum.koishi.xyz/t/topic/12615 https://github.com/ra1nyxin/tentacle-monster-roleplay-esp32 过于震撼,让 AI 扮演触手怪控制小玩具 GPT:典型的碳基生物思维

21 Aug 2026, 22:26 UTC268 viewsread 8 September 2026
Photo

多少?你说多少?吓哭了😭,比™内/闪存涨的还离谱

18 Aug 2026, 15:13 UTC299 viewsread 8 September 2026
Video

世纪难题:装一台5000元电脑到底需要多少钱? 世纪难题迎来终极答案。#装机配置 #电脑diy #显卡涨价 #内存涨价 #rtx5060 ▎Source

12 Aug 2026, 23:30 UTC350 viewsread 8 September 2026

这种打着玩机旗号,实际助长开挂的频道主,也应该受到制裁 频道主一直有个观点,如果罪犯(or 嫌疑人)因为root了手机,就能影响对局公平,那么说明手机厂商对Bootloader的管控是有缺陷的

12 Aug 2026, 07:28 UTC282 viewsread 8 September 2026
Photo

电信集团调整多项业务规则,包括收紧开卡数量和保号套餐涨价 据群友消息,电信集团于今日 9 时 30 分下发通知,调整异地及线上过户、停机保号、复机及存量套餐等业务流程,部分地区已开始执行。低价保号套餐价格上调:原 5 元档调至 8 元、8 元档调至 10 元;山东 3 元、5 元无忧卡并入 8 元档,河北部分 8 元套餐调至 10 元档。 此外,四川线上新开卡收紧,名下号码达 6 张后将限制新办卡。相关治理主要针对长期停机的「僵尸卡」和已下架的历史套餐,复机后可能需变更至在售套餐。各省执行时间和口径存在差异,以当地运营商实际落地为准。 via 𝑹𝒂𝒏 🌸 在花频道 · 茶馆水群 · 投稿通道

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

Mentions

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.

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.

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

“𝑌𝑖𝑋𝑢𝑎𝑛的储物间” (@zsH0HQfk), 303 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/zsH0HQfk.

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.