Telegram RegisterThe public register of Telegram
Telegram profile photo for 奶云MilkCloud

Channel

奶云MilkCloud

@milkcloudorg

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

9,588subscribers

+3,510 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1002476064035
TypeChannel
Username@milkcloudorg
DescriptionMilkCloud – 高速VPN服务 稳定连接,全球节点覆盖,确保您的网络隐私和安全。 🔗 访问官网:https://www.naiyun.vip 📢 加入Telegram群:https://t.me/acowcloud
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live10 November 2026
Measurements held27
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/milkcloudorg

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 12 September 2026 and assigned it the closest of 31 fixed categories, at 64% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.

Growth

6,0789,5887,8337 August 2026 — 6,078 subscribers8 August 2026 — 6,084 subscribers11 August 2026 — 6,138 subscribers14 August 2026 — 6,210 subscribers17 August 2026 — 6,335 subscribers20 August 2026 — 6,447 subscribers23 August 2026 — 6,588 subscribers26 August 2026 — 6,707 subscribers29 August 2026 — 6,791 subscribers2 September 2026 — 6,905 subscribers6 September 2026 — 7,030 subscribers11 September 2026 — 7,225 subscribers14 September 2026 — 7,604 subscribers18 September 2026 — 7,832 subscribers27 September 2026 — 8,220 subscribers5 October 2026 — 8,534 subscribers11 October 2026 — 8,745 subscribers14 October 2026 — 8,836 subscribers17 October 2026 — 8,957 subscribers20 October 2026 — 9,048 subscribers23 October 2026 — 9,180 subscribers26 October 2026 — 9,294 subscribers29 October 2026 — 9,356 subscribers1 November 2026 — 9,431 subscribers4 November 2026 — 9,488 subscribers7 November 2026 — 9,530 subscribers10 November 2026 — 9,588 subscribers7 August 202610 November 2026
27 measurements spanning 95 days, net +3,510. 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 5,552–10,115 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)SubscribersChange
10 Nov 2026, 15:599,588+58
7 Nov 2026, 07:009,530+42
4 Nov 2026, 07:519,488+57
1 Nov 2026, 13:069,431+75
29 Oct 2026, 21:049,356+62
26 Oct 2026, 21:519,294+114
23 Oct 2026, 19:199,180+132
20 Oct 2026, 18:059,048+91
17 Oct 2026, 19:378,957+121
14 Oct 2026, 18:408,836+91
11 Oct 2026, 12:398,745+211
5 Oct 2026, 05:218,534+314
27 Sept 2026, 01:378,220+388
18 Sept 2026, 04:187,832+228
14 Sept 2026, 09:017,604+379
11 Sept 2026, 03:007,225+195
6 Sept 2026, 11:557,030+125
2 Sept 2026, 00:146,905+114
29 Aug 2026, 14:026,791+84
26 Aug 2026, 18:536,707first reading

Engagement

30 posts held, back to 2 October 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 25 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
—
no view readings in window
Avg views / post
—
no view readings
Reaction rate
—
this channel exposes no reaction counts
Posts in window
1
of 30 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
WindowRolling 30 days · latest post in window 23 October 2026
Posts held30 (2 October 2025 – 23 October 2026)
Views total—
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Nov 2026, 23:34 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
26
Links
12

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

1,277 reactions across 29 posts, in 23 distinct kinds. The most used accounts for 30.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
💩39430.9%
🤬21917.1%
🤡13510.6%
❤1118.69%
👏856.66%
👍685.32%
👎614.78%
🥰443.45%
😭403.13%
😁332.58%
🤮191.49%
🗿120.94%
🤝120.94%
💔90.705%
🔥70.548%
😡60.47%
👌50.392%
🥴40.313%
😱30.235%
🤨30.235%
3 further kinds70.548%

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 29 of the 30 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 1,277 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 30 most recent posts we hold, published 2 October 2025 to 23 October 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

Telegram’s own ‘edited’ marker: 0 of 1 post held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

29 Sept 2026, 05:31 UTC≈14,400 views150 reactionsread 11 November 2026

修改了部分节点协议,请及时在客户端内刷新订阅获取最新节点信息

💩100👎22👏16❤7🥴4🤮1

13 Sept 2026, 02:42 UTC≈21,700 views93 reactionsread 11 November 2026

加回了Reality节点,在客户端内更新订阅即可使用

💩62👏27👍2❤1🤮1

12 Sept 2026, 11:47 UTC≈22,200 views62 reactionsread 11 November 2026

修复了点击主页上的下载客户端按钮下载到旧版客户端的问题

👏27💩23❤6🤨3🔥2🤮1

11 Sept 2026, 17:19 UTC≈22,800 views218 reactionsread 11 November 2026

请更新Clash Verge Rev, Clash Meta for Android和Clash Mi到最新版,旧版客户端不支持当前协议使用的部分功能导致无法连接,Clash Verge Rev和Clash Meta For Android 可以在官网使用教程内下载最新版进行安装,Clash Mi可以直接在App Store内进行更新,如果当前无法连接节点请更新客户端

🤬113👍31👎26🤡15💩13😭11❤5😁3

11 Sept 2026, 10:38 UTC≈21,100 views121 reactionsread 11 November 2026

修复了Clash Meta系客户端中xhttp前置配置导致的dns解析问题,请及时刷新订阅

🤬95💩8🗿7🥰4❤3🤯3🤮1

11 Sept 2026, 09:56 UTC≈20,200 views133 reactionsread 11 November 2026

经过测试后发现Hysteria协议已经被精准识别阻断,服务器上线数秒后被阻断,目前已经下线Hysteria协议的节点,后续如果发现解决方案会尝试重新上线,刷新订阅以获取最新的节点信息

🤡51💩31😭29😡6🗿5❤4🤬3😱3

9 Sept 2026, 00:30 UTC≈19,200 views38 reactionsread 11 November 2026

部分节点已经恢复,刷新订阅获取最新节点信息,新加入的xhttp跳板选项可以缓解部分情况下的阻断,可以在xhttp前置组内选择跳板,选择后所有xhttp节点会先通过跳板后再连接到节点(该功能仅支持clash meta/mihomo系客户端)

👏15🤬8👎6❤3💩3🤔2🤮1

8 Sept 2026, 11:19 UTC≈17,300 views127 reactionsread 11 November 2026

当前连接协议遭到阻断,目前具体表现为连接几秒后被断开,目前正在处理中

🤡69👍25💩18💔9❤2😘2🤮1🥰1

8 Aug 2026, 06:11 UTC≈24,600 views75 reactionsread 11 November 2026

修改了节点的连接协议,请在客户端内刷新订阅获取最新的节点信息

💩32🥰32👌5👍5🤮1

22 May 2026, 12:34 UTC≈38,200 views73 reactionsread 11 November 2026

近期本机场所使用的V2board面板爆出无验证码修改账号密码的漏洞,已经处理并修复了该漏洞,请所有用户检查自己的账户密码是否被更改,如果被更改请及时使用忘记密码功能重置密码并及时在面板中我的订阅界面点击“重置订阅信息”

😁25💩21❤11👎5🤝5🥰5🤮1

15 Mar 2026, 11:31 UTC≈46,100 views24 reactionsread 11 November 2026

已经修复香港节点访问Gemini问题

💩14❤9🤮1

Showing the 12 most recent of 30 posts we hold for @milkcloudorg. 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 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.

27 Feb 2026, 14:54 UTCAnonymous Poll4,420 voters approx.

你使用的运营商是

  1. 中国电信37%
  2. 中国移动37%
  3. 中国联通21%
  4. 其它(鹏博士,教育网……)5%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

27 Oct 2025, 03:37 UTCAnonymous Poll343 voters

我们发现基于TCP的协议AnyTLS在连接效果上不如基于UDP的Hysteria2,是否隐藏AnyTLS节点?

  1. 是64%
  2. 否36%

Shares as published. No per-option vote count is published by Telegram, so none is 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 30 most recent posts we hold, published 2 October 2025 to 23 October 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.

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.

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

“奶云MilkCloud” (@milkcloudorg), 9,588 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/milkcloudorg.

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.