祝大家2023新年快乐呀🥹

Channel
CordCloud相约2028
@cordcloud
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Cite this entry
8,211subscribers
-26 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001118877056 |
|---|---|
| Type | Channel |
| Username | @cordcloud |
| Created | Between 1 February 2017 and 30 June 2019— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 23 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 23 August 2026 |
| On Telegram | t.me/cordcloud |
Topic
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 20 August 2026 and assigned it the closest of 31 fixed categories, at 94% 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 23 Aug 2026, 05:55 | 8,211 | -4 |
| 20 Aug 2026, 02:52 | 8,215 | -7 |
| 16 Aug 2026, 20:14 | 8,222 | -8 |
| 9 Aug 2026, 20:12 | 8,230 | -5 |
| 7 Aug 2026, 01:15 | 8,235 | -2 |
| 6 Aug 2026, 03:03 | 8,237 | no change |
| 6 Aug 2026, 02:22 | 8,237 | first reading |
Engagement
20 posts held, back to 7 February 2021 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 18 pagesof 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 31 December 2022. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 2
- Links
- 20
Lifetime counters from Telegram’s own channel header, read 25 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.
Recent posts
为了不影响使用,不会重置所有人的连接密码,但为了保险起见,您可以在网站->资料编辑->点击节点连接密码修改右边的“√”进行重置。
由于出现订阅泄露问题,我们将重置所有用户的订阅链接,如您出现无法连接情况,可以到网站重新获取订阅链接更新使用。本次因为订阅链接出现流量被用等问题可以联系客服进行补偿,很抱歉出现此次问题。
网站主域名暂时停用,请您先使用备用域名。
(已经完成,请更新订阅)广东/广州移动因为上游正在升级暂时无法使用,正在询问具体时间,之后会更新。
祝大家新春快乐!
我们上架了春节限定套餐(202.2元,2880G流量,365天),截止至2月6日(周四)24:00,提前祝大家新春快乐。
祝大家2022新年快乐!🥳
晚些间我们将会对所有节点进行维护,网站也将更换为其他系统,届时可能会无法连接节点,更换新系统后可能会有部分不兼容问题导致账户出错,我们会持续在此频道更新进展以及其他消息。
官网已经恢复,抱歉为您带来不便。
昨天关于SSR/SSTAP客户端无法获取订阅,目前已经修复,抱歉为您带来不便。
我们上架了中秋限定套餐(192.1元,2815G流量,365天),截止至9月26日(周日)24:00,祝大家中秋快乐。
Showing the 12 most recent of 20 posts we hold for @cordcloud. 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.
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 23 August 2026 — this entry's latest reading, not the date you are reading this.
“CordCloud相约2028” (@cordcloud), 8,211 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/cordcloud.
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.