#通知 我们正在对官方客户端进行额外加密程序部署,如果有自动退出账号的情况,烦请重新登录下。感谢理解🙏

Channel
TTCLOUD
@ttcloudxyz
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
2,666subscribers
+767 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001788041083 |
|---|---|
| Type | Channel |
| Username | @ttcloudxyz |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 24 October 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 24 October 2026 |
| On Telegram | t.me/ttcloudxyz |
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 16 September 2026 and assigned it the closest of 31 fixed categories, at 74% 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 |
|---|---|---|
| 24 Oct 2026, 12:29 | 2,666 | +151 |
| 21 Oct 2026, 19:17 | 2,515 | +84 |
| 18 Oct 2026, 08:21 | 2,431 | +96 |
| 15 Oct 2026, 07:06 | 2,335 | +51 |
| 11 Oct 2026, 23:59 | 2,284 | +119 |
| 5 Oct 2026, 11:40 | 2,165 | +111 |
| 27 Sept 2026, 19:37 | 2,054 | +29 |
| 18 Sept 2026, 04:39 | 2,025 | +10 |
| 14 Sept 2026, 08:15 | 2,015 | +5 |
| 10 Sept 2026, 08:38 | 2,010 | +3 |
| 5 Sept 2026, 12:40 | 2,007 | +7 |
| 1 Sept 2026, 13:17 | 2,000 | +4 |
| 29 Aug 2026, 15:54 | 1,996 | +33 |
| 26 Aug 2026, 12:04 | 1,963 | +5 |
| 23 Aug 2026, 16:35 | 1,958 | +24 |
| 20 Aug 2026, 05:18 | 1,934 | +7 |
| 17 Aug 2026, 12:06 | 1,927 | +8 |
| 14 Aug 2026, 00:36 | 1,919 | +9 |
| 10 Aug 2026, 14:58 | 1,910 | +11 |
| 7 Aug 2026, 12:02 | 1,899 | first reading |
Engagement
21 posts held, back to 12 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 2 pages of 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 21 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
70 reactions across 16 posts, in 10 distinct kinds. The most used accounts for 44.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 31 | 44.3% | |
| 👏 | 10 | 14.3% | |
| 👍 | 7 | 10.0% | |
| 💯 | 7 | 10.0% | |
| 😁 | 5 | 7.14% | |
| 🐳 | 4 | 5.71% | |
| 🎉 | 3 | 4.29% | |
| 🏆 | 1 | 1.43% | |
| 🕊 | 1 | 1.43% | |
| 🤣 | 1 | 1.43% |
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 18 of the 21 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 70 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 21 most recent posts we hold, published 12 May 2026 to 7 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
#通知 第三方客户端(如小火箭/clash不同版本)订阅泄漏(订阅链接泄漏,不是数据泄漏)可能会导致不可用情况,请更换TTCLOUD官方客户端,感谢理解
🏆1
#通知 ios用户下载官方客户端的共享账号已更新
咱们在发送推特x的时候可以 @ttcloud579694,这样我们的账号运营看到就会帮助你们转发了获得更多曝光啦
❤2
#通知 服务器供应商于今日凌晨进行了临时维护导致部分用户无法登录,目前已恢复正常。抱歉带来不便
👏4
#通知 ttcloud客户端新增香港sx优化,点击刷新按钮获取
❤3🤣1😁1
#通知 新加坡/日本/美国 等优化节点皆上线TTCLOUD客户端中
❤1
#提示 如果客户端显示“当前无套餐”情况,在后台退出app然后重新打开就可以了
#提示 美国dx1/dx2是目前市场上最昂贵的gia线路,消耗倍率会有所提升
🕊1
#通知 如果不小心重复购买了套餐,可以在用完套餐之后再联系客服将被覆盖的套餐进行恢复
👏2
#更新 正在逐步更新电信优化节点,但由于外部环境限制目前只能在ttcloud客户端中获取 点击右上角刷新按钮或者等待客户端自动刷新 部分用户在全局状态下无法更新,可以切换到分流模式在进行刷新
👏4
#通知 由于系统更新导致很多用户客户端自动退出登陆状态,重新登录即可。如果忘记密码可以在网页中找回
❤4
Showing the 12 most recent of 21 posts we hold for @ttcloudxyz. 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.
Mentions
Named by 5 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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@ttcloudxyz named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 8 August 2026 – 8 August 2026
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 24 October 2026 — this entry's latest reading, not the date you are reading this.
“TTCLOUD” (@ttcloudxyz), 2,666 subscribers as measured 24 October 2026. Telegram Register, tgregister.com/channel/ttcloudxyz.
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.