Channel
@CangShuYunVPN_notice
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
164subscribers
-16 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002208522847 |
|---|---|
| Type | Channel |
| Username | @CangShuYunVPN_notice |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 13 October 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 13 October 2026 |
| On Telegram | t.me/CangShuYunVPN_notice |
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 24 September 2026 and assigned it the closest of 31 fixed categories, at 62% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Oct 2026, 01:37 | 164 | -8 |
| 1 Oct 2026, 19:38 | 172 | -3 |
| 13 Sept 2026, 09:59 | 175 | +1 |
| 5 Sept 2026, 18:19 | 174 | -2 |
| 29 Aug 2026, 09:03 | 176 | -1 |
| 22 Aug 2026, 19:46 | 177 | -2 |
| 15 Aug 2026, 04:54 | 179 | -1 |
| 8 Aug 2026, 13:01 | 180 | no change |
| 7 Aug 2026, 13:16 | 180 | first reading |
20 posts held, back to 31 May 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 13 April 2026. An engagement rate over an empty window would be a number about nothing.
3 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 66.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 66.7% | |
| 👏 | 1 | 33.3% |
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 3 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 3 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 31 May 2025 to 13 April 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.
尊敬的用户： 由于近期国内网络大环境处于敏感整改期（受“十五五”计划相关政策影响 https://m.thepaper.cn/newsDetail_forward_32304440?commTag=true ），传统中转链路面临严峻的拔线风险。为了保障服务不中断，我们已紧急将原定于测试阶段的“直连技术”提前全面上线。 【关于近期波动】 目前新协议正处于高频调试阶段，部分节点可能出现短暂的连通性反复，技术团队正 24 小时待命进行协议完善，预计近期将趋于稳定 【客户端兼容性重要提示】 安卓用户： 官方 App 在部分机型上可能存在兼容性 Bug。我们强烈建议您下载 “FLClash” 客户端，通过导入订阅链接使用。 协议限制： 请注意，由于新协议的技术跨度，旧版 Clash 客户端将无法识别新节点并报错，请务必更新订阅并使用推荐客户端 2. 节点倍率与流量升级通知 为了回馈大家在架构升级期间的耐心等待，…
首批直连节点已测试上线 在官网 仪表盘 内 获取最新订阅链接以获取最新节点信息 【温馨提醒】：建议所以MacOS，Windows，Android用户下载我们的专属APP使用! 专属app具体详细教程请见官网“文档”处 其余节点将在近日测试后陆续上线 仓鼠云技术团队 2026年4月
👏1
🐹 仓鼠云 | 4 月服务升级与调整公告 🚀 【线路大升级】 为了彻底解决近期波动，提升使用体验，我们不计成本完成了架构调整： 💎 VIP 入口 & 家宽节点 已全部更换为专线入口！ ⚡️ 延迟更低、带宽更高、稳定性极速提升！ 💰 【资费微调通知】 由于专线成本激增，部分产品将进行价格微调： ✅ 保持原价： 9.9 元基础月付、流量包（25 元 100G / 50 元 200G） 📈 价格微调： 其余部分月付套餐将略有上调（详见官网价位表） 🛠 【技术更新 · 必看操作】 1️⃣ 协议升级： 全线节点已切换为 ss-2022 加密协议。 2️⃣ 客户端检查： 请确保您的第三方客户端（如 Shadowrocket 等）支持该协议。 3️⃣ 更新订阅： 请务必登录官网仪表盘，重新获取并导入最新订阅链接。 ⚠️ 【特别提醒】 我们的订阅链接为一次性使用机制！导入后原链接即刻失效。如需在其他设备重新导入，请务必回到仪表盘再次获取…
📣 仓鼠云 v3.0.0 发布及新春特惠公告 新春限时促销活动 (2 月 16 日 - 2 月 24 日) 🎆 新春佳节期间，特开启以下优惠活动： 全场 8 折优惠码： 20OFFALL 年付 7.5 折优惠码： 25OFFYEAR 下单时在优惠券栏输入即可享受折扣。 📱 一、官方 App v3.0.0 正式发布 官方 App 现已全面升级至 v3.0.0 版本。新版本针对 Windows、MacOS、Android 及 Linux 平台进行了底层优化，大幅提升了在复杂网络环境下的连接稳定性和速度。 请各位用户前往官网或 GitCode 发布页面获取最新版客户端。 🎆 二、春节期间值班安排 2 月 16 日至 2 月 24 日春节假期期间： 各部门人员实行轮休制。 在线客服回复时间可能存在延迟，请您谅解。 若遇到节点连接异常，请直接在官网提交工单，技术部门会及时接收并进行处理。 …
📣 仓鼠云专属 App v3.0.0 正式发布！ 亲爱的用户们，仓鼠云专属 APP 迎来重大版本更新 v3.0.0！现已全面支持 Windows、MacOS、Android 和 Linux 多端同步。无论您使用何种设备，都能享受极致流畅的高速网络服务。 以下是各平台客户端下载地址： --- 📱 安卓客户端 v3.0.0 请根据您的设备架构选择下载： • [ARM64 版本 (59 MB)] —— 适用于大部分主流安卓手机（64 位架构） • [x86_64 版本 (63 MB)] —— 适用于 Intel 架构安卓设备或模拟器 --- 🪟 Windows 客户端 v3.0.0 • [下载安装包 .exe (17 MB)] —— 适用于 64 位 Windows 操作系统，一键安装 --- 🍎 MacOS 客户端 v3.0.0 • [下载 Universal 通用版 (46 MB)] —— 同时兼…
📣 网络波动情况通告 最近境外网络正遭遇大规模不明来源攻击 🌐💥 导致整体跨境链路出现波动和延迟，部分节点可能出现短暂掉线。还请大家理解与耐心等待 🙏 以下为当前节点状态： 1️⃣ 日本节点 / 美国节点 ⚠️ 正在受到持续恶意攻击 攻击结束后会自动恢复，无需手动切换节点 我们正在与上游进行实时防护和调度 🛡️ 2️⃣ 土耳其家宽节点 🔧 因网络线路频繁抖动，正在进行维护 维护期间可能出现偶发掉线 恢复后将第一时间公告 ✅ 3️⃣ 尼日利亚家宽节点 ⏳ 上游设备存在不定时休眠现象 已与商家沟通处理中，请稍安勿躁 🤝 --- 💡 温馨提示 - 目前无需进行任何设置变更 - 波动为暂时性，系统将会自动恢复 - 请大家稍等片刻，我们正在全力处理中 💪 感谢大家的理解与支持 ( • ω • )✧ 仓鼠云技术团队
🎉 仓鼠云 · 国庆中秋双节公告 🎉 国庆 ✦ 中秋双节同庆 (｡･ω･｡)ﾉ♡ 感谢大家一直以来对仓鼠云的支持与信任！ ✨ 节日专属优惠活动来啦： 全站订阅 / 续费享 8 折优惠 活动时间：即日起至 2025 年 10 月 7 日 优惠码： 国庆快乐 📌 温馨提示：10 月 1 日 - 7 日为团队假期，工单处理等可能会有延迟，还请谅解 (つ ´▽`) つ 愿大家假期开心，网络顺畅，阖家团圆 (*≧▽≦)ﾉｼ)) 仓鼠云团队 2025 年 10 月
9 月 24 日维护公告 香港 HKT 家宽线路已恢复正常使用，新节点与台湾 Hinet 节点目前均为动态 IP 节点，每日凌晨 4 点将自动更换 IP （请各位刷新订阅链接以获取新的节点信息！） 由于通报频繁，当前 VIP 入口与普通入口均已更换为新的入口。近期检测到家宽节点稳定性不足，我们将持续监测并适时更换入口，确保服务可用性 节点调整说明 所有冷门节点调整为 0.5 倍率使用。 对于近期的不稳定情况，我们深表歉意，感谢各位用户一直以来的理解与支持 😘
近期多个入口线路出现不稳定情况，目前所有 VIP 线路已切换至新通道，普通线路已临时切换至灾备通道。 “南极”与“朝鲜”节点因维护需要已暂时下架，待更新完成后将重新开放。 部分节点正在批量维护中，具体完成时间请以站点公告为准。
❤1
📣 订阅链接更新说明 由于 GFW 对订阅链接的扫描日益频繁，为了提供更加稳定与安全的服务，仓鼠云 🐹 将从即日起启用 「订阅链接使用即焚」策略： • 当您获取订阅链接并在第三方软件中导入使用后，该链接将 永久失效 • 如需更新订阅链接，请重新获取新的链接并导入使用 💡 推荐使用我们的专属 APP： • 无需手动频繁获取订阅链接 • 每次启动时自动下发最新的订阅配置文件 • 使用更省心、更快捷 😋 ➡️ 点我下载 仓鼠云专属 APP✅
入口出现故障正在抢修中 可能会有断联，属于正常情况！ 已完成
❤1
尊敬的客户： 根据最近反馈的我们自有 app 出现的问题，以及网站断联等问题，目前已经全部完成修复。如有其他问题请提交工单联系我们的技术部门进行处理，感谢您的支持与理解 🤝
Showing the 12 most recent of 20 posts we hold for @CangShuYunVPN_notice. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
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.
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 October 2026 — this entry's latest reading, not the date you are reading this.
“仓鼠云机场📢Channel” (@CangShuYunVPN_notice), 164 subscribers as measured 13 October 2026. Telegram Register, tgregister.com/channel/CangShuYunVPN_notice.
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.