7 measurements spanning 20 days, net +2. 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 1,382–1,388 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
26 Aug 2026, 04:43
1,386
-1
23 Aug 2026, 08:42
1,387
+1
19 Aug 2026, 16:14
1,386
+2
16 Aug 2026, 17:37
1,384
+1
12 Aug 2026, 22:07
1,383
-1
7 Aug 2026, 01:01
1,384
no change
6 Aug 2026, 15:46
1,384
first reading
Engagement
20 posts held, back to 8 April 2023 — 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 23 April 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
71 reactions across 11 posts, in 4 distinct kinds. The most used accounts for 52.1% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
37
52.1%
😢
21
29.6%
❤
12
16.9%
🤩
1
1.41%
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 14 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 71reactions 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 8 April 2023 to 23 April 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.
关于废弃vmess协议节点、启用AnyTLS协议节点的公告
近期,由于国内机房检测力度加强,我们决定即日起逐步关停全部vmess协议节点(名称以[V2ray]开头的节点]),并增加AnyTLS协议节点。
因为时间比较紧张,所以本次切换不会像上一次从ssr协议节点切换到vmess协议节点时那样有长达三年的平滑过渡期,预计将会在公告发出的几天内完全全部的切换。
请所有用户提前安装好支持AnyTLS节点的客户端,例如Clash Verge rev、最新版Shadowrocket等,可以缩短大家的业务中断时间。(原先从官网下载的2022年版的Clash for Windows 和2023年版的Clash for Android都不支持AnyTLS协议,必须更换软件)
此条公告会给全部VIP用户发送邮件。
再见了,vmess。(2020年2月~~2026年4月)
壹速云五周年活动延期的通知
因成本上涨、政策影响等多重因素,原定于8月15日开展的五周年优惠活动将会延期举行。具体时间另行通知。
Due to multiple factors such as rising costs and policy impacts, the 5th anniversary promotion on August 15 has been delayed. The holding time will be announced a few days later.
我们的入口服务器遇到了ddos洪水攻击,来源不明。目前服务器仍然处于封禁状态中,为了尽快恢复使用,暂时启用了备用服务器。
The gateway servers had encountered a DDoS flood attack from an unknown source. The servers are still blocked. In order to resume service as soon as possible, a backup server has been temporarily enabled.
Showing the 12 most recent of 20 posts we hold for @yisuyun. 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.
Polls
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
The shares total 142%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 20 most recent posts we hold, published 8 April 2023 to 23 April 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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 26 August 2026 — this
entry's latest reading, not the date you are reading this.
“壹速云 公告板” (@yisuyun), 1,386 subscribers as measured 26 August 2026. Telegram Register, tgregister.com/channel/yisuyun.
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.