Telegram RegisterThe public register of Telegram
Telegram profile photo for 星尘云|通知频道

Channel

星尘云|通知频道

@StardustCloud_Offcial

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

101subscribers

+2 since we began measuring on 13 August 2026

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

Register entry

Telegram ID-1003889640168
TypeChannel
Username@StardustCloud_Offcial
CreatedBetween 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live13 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/StardustCloud_Offcial

Growth

9910110013 Aug 2026, 00:31 — 99 subscribers13 Aug 2026, 05:05 — 101 subscribers13 Aug 2026, 00:3113 Aug 2026, 05:05
2 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 99–101 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 05:05101+2
13 Aug 2026, 00:3199first reading

Engagement

20 posts held, back to 19 July 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
214.8%
avg views ÷ 101 subscribers
Avg views / post
217
18 posts measured
Reaction rate
1.27%
reactions ÷ views · ER floor
Posts in window
18
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 6 of 18 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 12 August 2026
Posts held20 (19 July 202612 August 2026)
Views total3,905
Reactions total18
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 00:31 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.

Reaction mix

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

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1161.1%
🥰316.7%
🫡316.7%
👍15.56%

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 6 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 18reactions 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 19 July 2026 to 12 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

12 Aug 2026, 23:09 UTC43 viewsread 13 August 2026
Photo

我们上线了新节点📣 我们拥有了腾讯云HK边缘BGP顶尖优化服务器,这个服务器非常的极品,并且全国没有阻断,上线节点为Tencent Optimized 我们会带来更好的节点质量和服务质量 更新订阅即可获取 StardustTech星尘云🚀

12 Aug 2026, 17:15 UTC94 viewsread 13 August 2026

我们上线了新节点 Gomami 美国US节点 此节点为三网各自优化,电信CN2,联通9929,移动CMIN2 大家可以使用此节点作为冗余,如果不需要亚太的话 StardustTech星尘云🚀

12 Aug 2026, 14:38 UTC150 views8 reactionsread 13 August 2026

经过今天这件事我深刻的意识到了得深思熟虑后再做决策,做事情得马上做完不能拖,说到的事得做到不能画大饼,经过这次事件导致三边全部惹了一边(我太啥比了)但是得吸取教训,没有下次,再次给频道主和用户道一声歉 Stardust星尘云运营者

🥰3🫡32

Signed 𝓢𝓽𝓪𝓻𝓭𝓾𝓼𝓽

11 Aug 2026, 12:24 UTC220 viewsread 13 August 2026

UTC+8时区11:00日本GM1节点将进行例行维护与割接,请大家做好分流准备

8 Aug 2026, 16:31 UTC263 views2 reactionsread 13 August 2026

我们上线了新节点 云南入口内网通东京机房线路,流量倍率1倍 这个国内入口位于西南,到东京核心区其实延迟算挺高的,但是没有地区阻断,三台300M服务器冗余,单线程速率也是可以跑起来,大家觉得好用就用,不好用就当普通节点玩就行 禁止下载,发布违禁内容,严禁违反DMCA法案,严禁BTPT以及违反TOS协议 StardustTech星尘云🚀

2

8 Aug 2026, 16:12 UTC221 viewsread 13 August 2026

HK Gomami服务器1号机现在为重置续费状态,恢复后会马上通知,大家可以切换至其他节点进行冗余使用,我们将尽快恢复

5 Aug 2026, 17:04 UTC232 viewsread 13 August 2026

美国DMIT服务器1号机流量已重置,速率已恢复

4 Aug 2026, 17:27 UTC275 views2 reactionsread 13 August 2026

新公告👏 我们现在支持了Surge以及Egern等ios代理工具的导入,也同时支持了Vless与Anytls的协议 无需使用Sub store即可直接导入 StardustTech星尘云🚀

1👍1

31 Jul 2026, 14:25 UTC318 viewsread 13 August 2026

大家可以暂时使用美国🇺🇸DMIT EB Optimized 我的DMIT Optimized没流量了,可能会有限速,还剩4天重置,感谢大家理解

30 Jul 2026, 17:13 UTC223 viewsread 13 August 2026

我们上线了新节点 英国地区节点,可以用于激活wificalling以及日常使用 线路为三网9929线路,TCP延迟优化,单线程下载能跑满 我们会带来更好的服务质量以及节点质量 StardustTech星尘云🚀

29 Jul 2026, 17:50 UTC218 viewsread 13 August 2026

我们上线了新节点 台湾地区更新Neburst Optimized服务器以及日本地区更新原生日本Gomami Optimized服务器,非中转 StardustTech星尘云🚀

28 Jul 2026, 17:55 UTC195 views1 reactionsread 13 August 2026
Photo

我们将美国家宽更改为独立静态ISP家宽服务器 服务商为Cogent communications StardustTech星尘云🚀

1

Showing the 12 most recent of 20 posts we hold for @StardustCloud_Offcial. 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 — 959,447 of 1,549,376entries 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 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.

Names

Channels on the register whose handles appear in this channel's posts.

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

“星尘云|通知频道” (@StardustCloud_Offcial), 101 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/StardustCloud_Offcial.

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.