Channel
@eggtartcloud
On this record: Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
1,960subscribers
+8 since we began measuring on 15 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001924497397 |
|---|---|
| Type | Channel |
| Username | @eggtartcloud |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 15 August 2026 |
| Last confirmed live | 4 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 4 September 2026 |
| On Telegram | t.me/eggtartcloud |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Sept 2026, 21:22 | 1,960 | -2 |
| 31 Aug 2026, 20:17 | 1,962 | +2 |
| 28 Aug 2026, 13:12 | 1,960 | +3 |
| 25 Aug 2026, 23:24 | 1,957 | +4 |
| 23 Aug 2026, 00:06 | 1,953 | +2 |
| 19 Aug 2026, 07:47 | 1,951 | +1 |
| 16 Aug 2026, 08:46 | 1,950 | -2 |
| 15 Aug 2026, 19:30 | 1,952 | first reading |
20 posts held, back to 27 January 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 1 page 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 20 posts for this entry, the most recent from 17 June 2026. An engagement rate over an empty window would be a number about nothing.
136 reactions across 15 posts, in 10 distinct kinds. The most used accounts for 30.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😭 | 42 | 30.9% | |
| ❤ | 38 | 27.9% | |
| 🤡 | 25 | 18.4% | |
| 👍 | 15 | 11.0% | |
| 🥰 | 7 | 5.15% | |
| 🤨 | 4 | 2.94% | |
| 🔥 | 2 | 1.47% | |
| 👎 | 1 | 0.735% | |
| 😁 | 1 | 0.735% | |
| 😢 | 1 | 0.735% |
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 17 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 136 reactions 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 27 January 2025 to 17 June 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.
蛋挞云 官方频道 pinned «🌐 官方域名：https://eggtart.pro 🔄 跳转域名：https://蛋挞云.com 🛟 备用域名：https://danta26.biz ━━━━━━━━━━━━━━ 🚀 V-Ninja 定制协议更新公告 近期我们持续对 V-Ninja 客户端进行升级与优化，修复了多个已知问题，并新增多项实用功能（包括不限于）： ✅ 支持链式代理（Proxy Chain） ✅ 支持 Mihomo 内核替换 ✅ 支持 Windows 7 系统 ✅ 优化连接稳定性与兼容性 ✅ 提升客户端性能与使用体验 📢 官方频道：…»
🌐 官方域名：https://eggtart.pro 🔄 跳转域名：https://蛋挞云.com 🛟 备用域名：https://danta26.biz ━━━━━━━━━━━━━━ 🚀 V-Ninja 定制协议更新公告 近期我们持续对 V-Ninja 客户端进行升级与优化，修复了多个已知问题，并新增多项实用功能（包括不限于）： ✅ 支持链式代理（Proxy Chain） ✅ 支持 Mihomo 内核替换 ✅ 支持 Windows 7 系统 ✅ 优化连接稳定性与兼容性 ✅ 提升客户端性能与使用体验 📢 官方频道： https://t.me/ninja_ss2 建议所有用户升级至最新客户端，以获得最佳的稳定性、兼容性及功能支持。 V-Ninja 将持续迭代，为大家带来更强大、更稳定、更流畅的网络连接体验。
❤4
成本上涨了很多，而且还是专线，早就要涨价了，但是我们计划在15号涨价。
😭42😢1
公告：关于官网模板调整的通知 为了提升服务稳定性，我们计划于 4月30日 暂停使用当前官网模板。 原因是迁移后该模板缺乏适配的配置支持，且开发者已停止维护与升级，导致部分用户在账单相关操作中频繁出现报错。 调整后，官网将暂时采用市场通用模板进行展示。 如您在访问过程中对网站产生疑问，请认准页面 右下角的客服支持入口，以确认您访问的是我们的官方平台。 感谢您的理解与支持！
非常抱歉，近期给（部分ios/路由器）用户带来不好的体验，因为普通协议（ss/anytls）的不可抗力，机器被不断的拔线，我们无法提供稳定的服务。 多方面考虑下，本月普通协议我们暂时只能提供海外入口或直连过度，但是我们会尽量优化海外连接效果。 预计下个月我们会从新增加中转为普通协议客户提供更好的服务。 补充： 1. ninja 客户不受到影响，并且随着ninja的使用量，我们不断的增加带宽。
❤1
已初步上架 anytls 节点，请大家及时更新订阅，在这个特殊时期，我们无法保证服务的完整性，只能确保最大程度的可用性，感谢您的支持，我们会坚持下去！！！ （除了 ios/路由器客户，我们强烈推荐您使用官方 ninja 客户端）
❤2
ss 协议在接下来的时间可能无法保持稳定，我们新增直连节点 VLess-Reality 作为替代，并会在后续持续优化直连线路。 另外，ninja 在很多方便不受到影响，如果您可以使用 ninja 协议，就继续使用即可。
❤1
📢 重要通知 近期平台受外部环境影响（DDoS、政策变化等），整体网络波动加剧，目前市面上约 80%+ 服务受到影响。 为此，我们已正式推出全新官方协议：Ninja（已测试近一年） 📱 已支持设备 Windows / macOS / iOS / Android / Linux / OpenWrt ⚠️ 当前部分客户端仍有小问题，后续会持续优化 ‼️ 重要建议 👉 请尽快切换至【官方客户端】以保证正常使用 ⬇️ 官方下载 Windows：http://www.appkcc.com/b00jepz0qb iOS：https://apple.co/4m42pIL Android：https://www.appkcc.com/b00jereybg Mac：https://www.appkcc.com/b00jepz0lg OpenWrt：http://wwbce.appboz.com/b00jexhkej Linux：https:…
❤3
【官方离线客户端 + Ninja】 Ninja 已支持 iOS 外部测试！！！ 🔗 下载地址 Windows： https://www.appkcc.com/b00jepz0qb 🔗 下载地址 iOS：https://apple.co/4m42pIL 🔗 下载地址 Android： https://www.appkcc.com/b00jereybg 🔗 下载地址 macOS： https://www.appkcc.com/b00jepz0lg 🔗 下载地址 OpenWrt： http://wwbce.appboz.com/b00jexhkej 🔗 下载地址 Linux： https://www.appkcc.com/b00jepz0di 🔗 备用下载地址1： 点击下载OneDrive 🔗 备用下载地址2： 点击下载Github Ninja 为官方定制协议，搭配官方离线客户端，带来安全、稳定、流畅的上网体验，任何时候都能放心
❤2
#重要公告 由于大陆中转不可抗性，导致普通的ss节点持续不稳定，以及后续可能会有更多的问题会出现，请大家尽快转移使用官方客户端。（注：由于ios审核未通过，我们在尝试其他方案）
🤨4❤2
优惠码： 2026 截止日期： 2月22号晚 优惠额度： 20% off 感谢大家往年的支持，今年继续稳定~~
❤10👍3🔥2
【官方离线客户端 + Ninja】 Ninja 已支持路由器使用，家庭与多设备场景更方便！！ 🔗 下载地址 Windows： https://www.appkcc.com/b00jepz0qb 🔗 下载地址 Android： https://www.appkcc.com/b00jereybg 🔗 下载地址 macOS： https://www.appkcc.com/b00jepz0lg 🔗 下载地址 OpenWrt： http://wwbce.appboz.com/b00jexhkej 🔗 下载地址 Linux： https://www.appkcc.com/b00jepz0di 🔗 备用下载地址1： 点击下载OneDrive 🔗 备用下载地址2： 点击下载Github Ninja 为官方定制协议，搭配官方离线客户端，带来安全、稳定、流畅的上网体验，任何时候都能放心冲浪。
Showing the 12 most recent of 20 posts we hold for @eggtartcloud. 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.
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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 4 September 2026 — this entry's latest reading, not the date you are reading this.
“蛋挞云 官方频道” (@eggtartcloud), 1,960 subscribers as measured 4 September 2026. Telegram Register, tgregister.com/channel/eggtartcloud.
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.