11 measurements spanning 9 days, net +388. 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 48,276–48,780 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
15 Aug 2026, 20:26
48,722
+57
14 Aug 2026, 13:36
48,665
+15
13 Aug 2026, 03:17
48,650
+44
12 Aug 2026, 01:12
48,606
+62
10 Aug 2026, 21:41
48,544
+96
9 Aug 2026, 21:15
48,448
+29
8 Aug 2026, 19:04
48,419
+32
7 Aug 2026, 18:57
48,387
+45
6 Aug 2026, 16:23
48,342
+8
6 Aug 2026, 12:45
48,334
no change
6 Aug 2026, 12:37
48,334
first reading
Engagement
20 posts held, back to 1 May 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 23 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
57.5%
avg views ÷ 48,722 subscribers
Avg views / post
28,000
3 posts measured
Reaction rate
0.969%
reactions ÷ views · ER floor
Posts in window
3
of 20 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
Window
Rolling 30 days · latest post in window 6 August 2026
Posts held
20 (1 May 2026 – 6 August 2026)
Views total
84,000
Reactions total
814
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
16 Aug 2026, 02:37 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
25
Links
426
Lifetime counters from Telegram’s own channel header, read 16 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.
Reaction mix
5,047 reactions across 20 posts, in 46 distinct kinds. The most used accounts for 17.2% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
💩
870
17.2%
🤡
569
11.3%
😱
557
11.0%
😁
479
9.49%
👎
415
8.22%
🤮
285
5.65%
🤣
270
5.35%
❤
259
5.13%
👍
241
4.78%
🤬
226
4.48%
😨
146
2.89%
🔥
129
2.56%
🤯
124
2.46%
🍾
97
1.92%
👏
64
1.27%
😭
62
1.23%
🖕
30
0.594%
🥰
28
0.555%
😡
24
0.476%
😢
24
0.476%
26 further kinds
148
2.93%
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 20 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 5,047reactions 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 1 May 2026 to 6 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.
Telegram Stars
Stars received
8
across the posts below
Posts paid on
3
of 20 we hold a reading for · 15%
Most on one post
4
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @vps_xhq. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 20 most recent posts we hold for this entry, published 1 May 2026 to 6 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
甲骨文云将削减ARM实例免费配额
甲骨文云已悄然修改文档中关于“免费资源”的部分描述。在OCI Ampere A1 计算实例（Arm 处理器）部分，将原先的“4 OCPUs and 24 GB of memory”修改为“2 OCPUs and 12 GB of memory”。
由于A1实例仅对免费配额部分免费，这意味着升级成付费账号的用户将需要为此支付费用。A1实例资源紧缺，免费号开到满配A1实例的机会渺茫，因此有大量用户选择升级到付费账号。这些用户可能需要降低配置来避免昂贵的配置费用。
[消息等级 Level B · #重要 ]
Showing the 12 most recent of 20 posts we hold for @vps_xhq. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Posts edited after publishing
@vps_xhq edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
First edit seen
11 August 2026
Most recent edit
11 August 2026
Citation-graph rank
Citation-graph rank — 32,391 of 1,481,217entries 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.
Forward network
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.
Mentions
Named by 6 registered channels — 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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
风向旗参考快讯 @xhqcankao · 158,504 Telegram ranks this channel #5 of 45 here — alongside 44 others — read 12 August 2026
竹新社 @tnews365 · 156,603 Telegram ranks this channel #6 of 59 here — alongside 58 others — read 12 August 2026
科技圈🎗在花频道📮 @zaihuapd · 275,781 Telegram ranks this channel #8 of 40 here — alongside 39 others — read 12 August 2026
科学上网观察与机场测速 @jichangtj · 133,388 Telegram ranks this channel #13 of 54 here — alongside 53 others — read 15 August 2026
前女友们用过的机场—始于机场，不止机场 @gebaopiCloud · 100,041 Telegram ranks this channel #16 of 56 here — alongside 55 others — read 15 August 2026
每日沙雕墙 @woshadiao · 115,315 Telegram ranks this channel #35 of 52 here — alongside 51 others — read 14 August 2026
This channel appears in 6 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 15 August 2026 — this
entry's latest reading, not the date you are reading this.
“VPS信号旗播报” (@vps_xhq), 48,722 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/vps_xhq.
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.
