Telegram RegisterThe public register of Telegram

Channel

磐石云

@rock_server

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

866subscribers

+2 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1003319857090
TypeChannel
Username@rock_server
Description官网 中国站 https://www.rockcloud.vip 群组 @rockcoinw 客服/滥用举报 @panshiyun
CreatedBetween 1 November 2025 and 31 March 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live6 August 2026
Measurements held3
On Telegramt.me/rock_server

Growth

8648668656 Aug 2026, 02:31 — 864 subscribers6 Aug 2026, 12:20 — 866 subscribers6 Aug 2026, 14:35 — 866 subscribers6 Aug 2026, 02:316 Aug 2026, 14:35
3 measurements taken within a single day, 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 864–866 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Aug 2026, 14:35866no change
6 Aug 2026, 12:20866+2
6 Aug 2026, 02:31864first reading

Engagement

20 posts held, back to 23 June 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
89.3%
avg views ÷ 866 subscribers
Avg views / post
773
9 posts measured
Reaction rate
4.10%
reactions ÷ views · ER floor
Posts in window
9
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. It is computed over the 8 of 9 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 6 August 2026
Posts held20 (23 June 20266 August 2026)
Views total6,960
Reactions total280
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 14:35 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
35
Videos
1
Links
54

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

669 reactions across 19 posts, in 10 distinct kinds. The most used accounts for 13.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🎉8913.3%
👍8512.7%
💯8212.3%
7911.8%
🤩7611.4%
❤‍🔥7010.5%
🥰6810.2%
🔥659.72%
😍548.07%
🗿10.149%

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 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 669reactions 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 23 June 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.

Recent posts

6 Aug 2026, 11:01 UTC133 viewsread 6 August 2026

AWS B区,控制面板部分用户更换ip时报错的问题已解决,若用户需更换ip,请现在进行尝试

2 Aug 2026, 16:22 UTC481 views26 reactionsread 6 August 2026
Photo

AWS 服务器新的面板正在开发IP被墙自动更换ip的功能

❤‍🔥54👍4🎉3🥰3🔥2🤩2😍2

1 Aug 2026, 11:30 UTC539 views21 reactionsread 6 August 2026

阿里云香港入口 流量转发150/T单向计费 每季度 200Mbps独享宽带 三网优化堪比专线的延迟 允许协议: Anytls vless hy2 ip被墙解决方案: ip被墙自动更换ip 另外提供阿里云其他地区转发入口 若有需求请联系客服 @panshiyun

👍5🥰4🎉3💯3❤‍🔥2🤩21🔥1

28 Jul 2026, 14:15 UTC930 views38 reactionsread 6 August 2026

🔥阿里云ECS独享不限速宽带全新上架 ⚠️优惠仅50份,抢完即止 ✅200Mbps全独享带宽|200G单向流量23元起 ✅阿里云海外全区域可选,中途可换IP、长期续费 ✅大批量采购可联系客服议价 🎁优惠码:EC2-2 首月立减2元 购买链接:https://www.rockcloud.vip/index.php?rp=/store/a-li-yun-fu-wu-qi 咨询频道:https://t.me/rock_server

🤩10🎉6😍53❤‍🔥3👍3💯3🥰3

26 Jul 2026, 04:33 UTC≈1,030 views28 reactionsread 6 August 2026

阿里云轻量服务器已上架 阿里云轻量服务器目前业务限制(ECS不限制) 禁止做 机场,cdn,诈骗,影视侵权这些业务 阿里云ECS 独享宽带不限速已上架 (量大价格可联系客服议价) 订购链接 https://www.rockcloud.vip/index.php?rp=/store/a-li-yun-fu-wu-qi

👍7🎉54💯3🥰3🤩2😍2❤‍🔥1

26 Jul 2026, 03:46 UTC936 views44 reactionsread 6 August 2026

重要通知! 阿里云ECS流量款服务器即将来袭 200Mbps独享宽带不限速 200G流量 23元起

8❤‍🔥7💯7🤩7😍4🎉3👍3🥰3

25 Jul 2026, 16:08 UTC873 views45 reactionsread 6 August 2026

AWS S区,日本,新加坡目前售空,预计补货时间,下周二 若需要其他地区可联系客服补货,其他地区大量有货

🔥10👍6🎉5💯5🤩5🥰54😍3

21 Jul 2026, 13:23 UTC938 views39 reactionsread 6 August 2026

重要通知! GCP日本已重新开通,已购用户已补发10天使用时间

💯7🤩7🎉64🥰4❤‍🔥3👍3😍3

14 Jul 2026, 15:46 UTC≈1,100 views39 reactionsread 6 August 2026

通知:AWS新加坡(S区)底层架构全面升级改造,工期约5天。升级完成后将大批量补充Lightsail服务器库存,缺货用户可耐心等候补货上线。

👍9❤‍🔥5🥰54🔥4🤩4💯3😍3

6 Jul 2026, 16:21 UTC≈1,190 views24 reactionsread 6 August 2026

AWS 产品重要公告 1、AWS B区相关产品补发、全额退款工作已全部完成,如您还有未处理遗漏问题,请提交工单联系客服; 2、AWS S区现已补货10台 (人工开通) 3、AWS产品售后无忧保障政策: 客户正常使用场景下,实例发生非人为宕机故障,支持全额退款申请。 以下情况不享受本保障: ① 用户利用服务开展挖矿、DDoS攻击等违规行为; ② 套餐流量耗尽引发停机故障; ③ 用户自行在服务端操作不当造成宕机。 磐石云对本保障规则拥有最终解释权。

🎉7❤‍🔥6💯3🔥3🤩2👍1🥰1😍1

6 Jul 2026, 04:26 UTC972 views41 reactionsread 6 August 2026

荷兰10GBPS NAT已重新开通,已购用户补发3天时间

😍9🎉7👍5🔥54💯4❤‍🔥3🥰3

6 Jul 2026, 04:02 UTC895 views38 reactionsread 6 August 2026

GCP新加坡 NAT已重新开通,已购用户补发3天时间

8🔥7❤‍🔥5🎉4💯4😍4🥰3👍2

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

Citation-graph rank — 280,788 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.

Mentions

Named by 2 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.

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

“磐石云” (@rock_server), 866 subscribers as measured 6 August 2026. Telegram Register, tgregister.com/channel/rock_server.

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.