Channel
@CloudFisher
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
14,170subscribers
+73 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002249364575 |
|---|---|
| Type | Channel |
| Username | @CloudFisher |
| Description | 永久官网 https://cloudfisher.net 官方频道 @CloudFisher 官方群组 @CloudFisherGroup 官方知识库 @CloudFisher_Knowledge |
| Created | Between 1 May 2024 and 31 October 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/CloudFisher |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 13:36 | 14,170 | +15 |
| 12 Aug 2026, 12:16 | 14,155 | +10 |
| 11 Aug 2026, 12:43 | 14,145 | +5 |
| 10 Aug 2026, 09:27 | 14,140 | +13 |
| 9 Aug 2026, 05:52 | 14,127 | +22 |
| 8 Aug 2026, 05:03 | 14,105 | +8 |
| 7 Aug 2026, 13:03 | 14,097 | first reading |
20 posts held, back to 7 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 17 pagesof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 17 July 2026 |
|---|---|
| Posts held | 20 (7 January 2025 – 17 July 2026) |
| Views total | 7,240 |
| Reactions total | 11 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Aug 2026, 16:48 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.
Lifetime counters from Telegram’s own channel header, read 13 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.
745 reactions across 19 posts, in 8 distinct kinds. The most used accounts for 78.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 587 | 78.8% | |
| 👍 | 104 | 14.0% | |
| 😁 | 32 | 4.30% | |
| 🤔 | 12 | 1.61% | |
| 👏 | 5 | 0.671% | |
| 🔥 | 2 | 0.268% | |
| 🤩 | 2 | 0.268% | |
| 😘 | 1 | 0.134% |
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 19 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 745reactions 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 7 January 2025 to 17 July 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.
【近期网络波动自救指南】 近期 GFW 网络封锁力度有所升级，部分地区可能出现节点被快速封锁（入口域名秒墙）的情况，导致服务无法连接。 为尽快恢复服务，CloudFisher 将根据实际情况及时更换相关入口域名配置。因此，请各位用户在遇到连接异常时： 及时更新订阅 / 重新导入订阅 特殊时期网络环境波动较大，相关调整可能较为频繁。我们会持续监测并尽快处理，给您带来的不便，敬请谅解。 渔云团队
❤5🤔5😘1
CloudFisher 渔云两周年庆 从一叶渔舟到二载云海 云海翻涌处，渔舟仍向前。 Still Sailing, Beyond the Clouds. 前言 不知不觉，CloudFisher 渔云已经走过两年。 这两年里，行业经历多次震荡，环境不断变化，成本与资源几经波动。渔云也走过不少困难，面对过质疑、误解与压力。但也正是在这些风浪里，我们不断补齐不足、优化服务、调整方向，并成长为今天的样子。 两周年不是终点，而是新的开始。感谢每一位曾经选择、支持、反馈、陪伴渔云的用户。 活动内容 1. 全场 83 折 活动期间使用优惠码 2year_ClouFisher 全场订阅享 83 折 优惠。 2. 30GiB 礼品卡 GC0EBADA9565E0 GCF660BAF5C7A7 GC38DB3B1C85D0 GC98CDC1B00C6C 3. 周年抽奖 奖品包含：红包 / 订阅套餐 / 五折优惠券 抽奖明细请前往群组…
❤66👍6🔥2
#重要公告 关于系统安全升级及佣金提现流程调整的通知 近期，我们监测到行业底层架构（V2Board 及相关衍生系统）披露了一项严重的 安全漏洞。该漏洞可能导致攻击者在仅知晓用户邮箱的情况下，绕过安全验证非法获取账户访问权限，并伪装成号主恶意发起佣金提现申请。 保障您的账户与资产绝对安全是我们不可妥协的底线。技术团队已在获取情报的第一时间，完成了全量系统的补丁更新与漏洞修复，目前系统已恢复最高安全级别。 为了彻底阻断潜在的资金风险，我们已采取以下保护性措施，需要您的配合： 重置所有提现工单 为防止漏洞暴露期间产生任何未经授权的恶意提现，我们已主动关闭系统中所有待处理的「佣金申请工单」。如果您近期提交了提现申请，烦请您登录官网，重新发起提现工单，我们将优先为您审核处理。 请核实账户登录状态 我们强烈建议您近期检查账户的登录情况与密码安全。如您发现密码错误或无法正常登录，请立即点击官网首页的「忘记密码」，通过您的注册邮箱重新设置新的…
❤20
📢 关于近期网络波动的说明 近期中国移动、电信、联通部分地区对境外方向连接出现明显异常，尤其是移动用户反馈最为集中。 目前属于区域性影响，不同地区表现不同，像江苏、福建、上海、四川成都等地反馈会更明显。 常见表现： • 上午基本正常 • 下午开始明显变慢 • 晚高峰出现卡顿、连接超时、频繁断流 • 夜间会相对恢复一些 • 移动数据和部分 WiFi 环境都会受到影响 很多用户会误以为是节点坏了、机场炸了，实际上： ⚠️ 这次主要是运营商阻断海外回程 ⚠️ 不是节点问题，也不是线路故障 简单理解就是： 不是我们线路坏了，而是运营商把回程线路限制了，导致数据回来变得非常困难，严重时甚至会直接中断连接。 我们这边也一直在持续处理准备新的方案。 虽然我们一直在优化，但这次问题主要发生在上游运营商侧，完全恢复时间暂时无法完全确定。 如果你目前遇到连接不稳定，可以先尝试下面这些方法（实测部分有效，但不保证长期稳定）： ① 关闭代理，直…
❤27
📢 线路更改通知 近期因客观不可抗因素，为保障使用体验，我们已完成以下更改： 架构调整： 切换至境外中转入口，避开拔线风险。 协议更换： 启用 Hysteria2 AnyTls Vless，增强安全混淆与稳定性。 ⚠️ 重要提示： 旧节点即刻失效。请务必前往官网 重新导入 / 更新订阅 以恢复连接。 ❗ 无法使用请先看这里 如果你出现“用不了 / 连不上”的情况，请优先尝试： 👉 更新订阅（非常重要！） ⚠️ 关于节点数量变少说明 当前节点较少（只有IPV6节点）属于正常情况： 👉 部分节点已切换为 HY2 协议，不支持的客户端将无法显示或使用 📱 客户端建议（务必使用支持 HY2 的） Android / Windows / macOS： 推荐使用 FlClash iOS： 推荐使用 小火箭（Shadowrocket/版本太老也会导致不支持hy2节点，如遇少节点请更新） 💬 如仍无法使用，可能是DNS污染，参考…
❤30👏3😁1
【Cloudfisher 2026 新年回馈】 新年伊始，感谢信任。为回馈用户，特推新年限时福利，折扣红包齐发！ 🛍 福利一：全场限时 8 折 • 优惠码： CF2026 • 有效期： 即日起至 2026/2/22 23:59 💸 福利二：抽奖 (仅限持有有效套餐用户参与，进入群组了解详情) 🏆 现金大奖 (支持 USDT-TRC20 / 口令红包) 🥇 一等奖 (1名)：¥ 888 | 顶级大包，鸿运当头 🥈 二等奖 (3名)：¥ 288 | 寓意发发，好运连连 🥉 三等奖 (50名)：¥ 28.88 | 普照吉利，奶茶自由 ⚡️ 流量加油包 • 四等奖 (10名)： Cloudfisher 流量 +100G • 五等奖 (20名)： Cloudfisher 流量 +50G 更新：抽奖已结束 Cloudfisher 渔云团队
❤45😁2
取消阅后即焚 经过长期监测与评估，为提升用户的体验，即日起正式取消订阅链接「阅后即焚」限制。 ✔️ 变更说明 订阅链接不再受 300 秒时效约束。您获取的链接将保持长期有效，方便您随时配置或在多设备间同步。 🔒安全提示 便捷不代表安全降级。订阅链接仍是您的私密凭证，请勿分享给他人。严禁在任何国内社交平台传播、测试或分享订阅链接。 渔云团队
👍2❤1
升级专线与价格调整公告 尊敬的用户： 感谢您长期以来的信任。过去一年多我们始终坚持价格不变，但近期面临运营成本激增的严峻挑战（包括因为 通报 而导致的高频的IP更换成本、针对 QoS 限速问题优化的多机房试错投入，以及持续上涨的服务器费用）。为打破亏损困局并提供可持续的高质量服务，我们在深思熟虑后决定进行业务升级与价格调整。 🚀核心升级内容 线路升级： 从原有的中转模式全面升级为三线接入专线，网络体验将迎来跨越式提升。 高可用性： 迁移至IP储备丰富的新专线机房。多线接入意味着更高的容灾能力，同时解决了 Qos 限速问题，即使遭遇 通报 也能避免“全线瘫痪”。 响应速度： 依托新机房资源，由于 通报 而需要的IP更换与业务恢复速度将大幅加快，确保持续在线。 💡关于价格： 目前的专线成本高昂，原有的定价体系已无法支撑运营。此次调整实属无奈之举，旨在确保我们能长久、稳定地为您提供服务。 附： 以前的优惠卷均可用，取消了额外扣…
❤45😁6👏1
📢 重要公告：入口域名变更与安全升级通知 各位用户： 由于近期监管环境极其严苛， 通报 频发。为保障服务持续可用，我们已采取手段：全面更换入口域名。由此带来的不便，我们深表歉意😞 ⚠️ 您将面临的影响 连接失效： 原有订阅入口已作废，大部分节点将出现连接超时（Timeout） 。 ✅ 您需要做的操 作 1. 重 新 导 入订阅： 请立即登录官网，重新获取并导入最新的订阅链 接。 2 . 清空缓存： 若更新后仍未生效，请尝试重 启客 户端或 清空 DNS 缓存。 🚫 严 正 警告（红线原则） 严禁在任何国内社交平台（如微信、QQ、小红书、贴吧等） 传 播 、测试或分享订阅链接。 后果： 任何源自国内 平台的泄漏，系统将执行无条件永久封号处 理。保护订阅不 外泄即是保护大家的稳定。 🎁补偿方案 我们现提供 40GiB 流量补偿，请凭借以下礼品卡任选其一进行兑换： CFB8FFC1C5078A CF71A549206BF4 …
❤70👍9
📢emby bot升级&备份 为进一步提升服务质量，我司已对 Emby 服务器 Bot 进行了为期数月的底层代码重构与优化，现已顺利完成，并实现了与 阅后即焚政策 的全面适配 ✅。 ⚠️鉴于新 Bot 的上线需要进行系统切换，届时 所有用户的观影记录及账户资料将被清空。升级完成后，所有用户需重新注册账号 才能继续使用服务。 为避免个人使用体验受影响，请有保留需求的用户务必在 升级前完成自助备份（📸例如通过截图记录观看进度）。 ⏰本次 Bot 升级计划于 9 月 5 日（周五）晚 20:00 正式实施。请广大用户相互转告，提前做好相关准备 🔔。 机器人已升级完成 请各位用户及时重新注册 —— 渔云团队
❤21
#阅后即焚 尊敬的用户您好： 近期行业整体环境持续承压，监管因素频繁升级，我司服务亦受到一定影响。为进一步加强用户数据安全与服务可持续性，我司已对订阅获取机制进行重要调整： 📢 订阅机制更新说明 1️⃣ 阅后即焚机制启用 自即日起，通过官网获取的订阅链接将在 300 秒 内自动失效。该机制旨在防止链接在用户端外泄或被非授权渠道滥用。 此举可能为您带来部分使用上的不便，但在当前形势下，此为确保服务安全性与可用性的必要手段。未来将视外部环境评估是否取消该限制。 更新指引 如遇节点无法连接等异常情况，请务必按以下步骤操作： 1️⃣ 访问官方导航跳转官网 cloudfisher.icu 获取最新订阅链接； 2️⃣ 将新链接复制至代理软件中并立即导入，完成订阅更新。 📨 如您在操作过程中仍有疑问，可提交工单与客服联系，我们将竭诚为您提供支持。 渔云团队
❤32👍9🤔7🤩1😁1
#优化通告 尊敬的用户您好： 我司在持续运行监测过程中发现，部分新入口存在明显的跨运营商 QoS 限速问题，主要影响电信及联通网络用户，移动网络用户则基本未受影响。 为改善相关用户的连接体验，我司已紧急部署电信 / 联通优化专用节点。若您为电信或联通用户，建议优先选择节点名称中标注为“电联优化”的节点进行连接。如当前节点列表中未显示相关节点，请及时前往官网重新获取并导入最新订阅链接。 经我司多轮测试，目前服务整体连接稳定性与访问速度已基本恢复正常。但考虑到当前网络环境仍存在不确定因素，我司将继续进行动态优化与实时监控，确保服务持续稳定运行。 感谢您的理解与支持。我们将持续优化服务，以保障您的良好使用体验。 渔云团队
❤36
Showing the 12 most recent of 20 posts we hold for @CloudFisher. 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.
Citation-graph rank — 311,468 of 1,340,412entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“渔云𝑪𝒍𝒐𝒖𝒅𝑭𝒊𝒔𝒉𝒆𝒓” (@CloudFisher), 14,170 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/CloudFisher.
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.