Channel
@cloud_nas
On this record: Growth · Engagement · What this channel posts · Posts · Cite this entry
11,686subscribers
-15 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001519823827 |
|---|---|
| Type | Channel |
| Username | @cloud_nas |
| Description | CloudNAS发布频道，相关问题讨论请加入CloudNAS讨论群：https://t.me/cloudnaschat 官方网站： https://www.clouddrive2.com |
| Created | Between 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 27 August 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 27 August 2026 |
| On Telegram | t.me/cloud_nas |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Aug 2026, 07:44 | 11,686 | +4 |
| 26 Aug 2026, 07:54 | 11,682 | +1 |
| 25 Aug 2026, 04:34 | 11,681 | -3 |
| 23 Aug 2026, 23:39 | 11,684 | +2 |
| 22 Aug 2026, 03:54 | 11,682 | +1 |
| 20 Aug 2026, 18:55 | 11,681 | -2 |
| 19 Aug 2026, 17:58 | 11,683 | -5 |
| 18 Aug 2026, 17:25 | 11,688 | +3 |
| 16 Aug 2026, 07:04 | 11,685 | -2 |
| 14 Aug 2026, 17:35 | 11,687 | -6 |
| 12 Aug 2026, 09:03 | 11,693 | -2 |
| 10 Aug 2026, 11:45 | 11,695 | -5 |
| 9 Aug 2026, 14:21 | 11,700 | -1 |
| 8 Aug 2026, 12:37 | 11,701 | +2 |
| 7 Aug 2026, 12:31 | 11,699 | -2 |
| 7 Aug 2026, 01:15 | 11,701 | no change |
| 7 Aug 2026, 01:06 | 11,701 | first reading |
29 posts held, back to 19 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 37 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 24 August 2026 |
|---|---|
| Posts held | 29 (19 May 2026 – 24 August 2026) |
| Views total | 22,740 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 27 Aug 2026, 18:13 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 27 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.
CloudDrive2 1.0.16 第四批更新 Windows 1.0.16.4 · macOS 直接下载版 1.0.16 (12)（Apple Silicon + Intel）· Android 1.0.16（versionCode 336）· Apple 四端 TestFlight 1.0.16 (12) · Meta Quest VR 1.0.16 (build 33)（Meta Store BETA 渠道） 更新内容 -------------------------------------------------------------------------------- ★ 下载引擎升级到 1.0.15：播放和下载速度都有明显提升。同一个文件被多处同时读取时 （例如播放蓝光原盘镜像），不再出现播放中途的等待。（全平台） • 影视库（Emby / Jellyfin）：界面跟随应用主题，不再固定深色；AI…
V1.0.15(Web3.0.14) 1. 优化后台多线程下载算法，提高从网盘下载的速度，高码率视频播放会更流畅 2. 备份：实时监控启动失败时会明确报错。 以前监控没有真正启动时，界面仍然显示空闲，与正常状态无法区分，实际上文件改动没有被备份，现在会显示错误原因，Linux上如果被监控的目录数量超过系统上限（群晖默认 8192），以前整个监控会失效且没有任何提示；现在会提示如何调大这个上限，并保留已经生效的那部分监控 3. 修复备份导致的磁盘空间不释放。 源文件删除后空间不会被回收，需要重启服务才能恢复的问题 4. 修复将文件或文件夹重命名为一个已存在的名字时，缓存报错并在日志中重复输出错误的问题 5. 修复修改设备名称后需要重新登录的问题 6. 其它bug修复和性能改进 https://github.com/cloud-fs/cloud-fs.github.io/releases/tag/v1.0.15
CloudDrive2 1.0.16 第三批更新 Windows 1.0.16.3 · macOS 直接下载版 1.0.16 (11)（Apple Silicon + Intel）· Android 1.0.16（versionCode 335）· Apple 四端 TestFlight 1.0.16 (11) · Meta Quest VR 1.0.16 (build 32)（Meta Store BETA 渠道） 更新内容 -------------------------------------------------------------------------------- ★ 安卓电视：4K UHD 原盘用光盘菜单模式播放也流畅了，以前只有直接播放流畅； 进碟更快，拖动进度后恢复也更快。（已在 TCL 电视上验证） • 字幕：修复部分视频自带字体导致的整行字叠在一起、或整行不显示。（全平台） • 蓝光…
CloudDrive2 App 1.0.16 第二批更新 Windows 1.0.16.2 · macOS 直接下载版 1.0.16 (10)（Apple Silicon + Intel）· Android 1.0.16（versionCode 334）· Apple 四端 TestFlight 1.0.16 (10) · Meta Quest VR 1.0.16 (build 31)（Meta Store BETA 渠道） 这一批的重点：Windows 新增下载管理器、文件列表显示观看进度、云盘存储管理修复， 以及 Android 电视端的遥控器操作和杜比视界原盘改进。 ★ Windows：新增下载管理器 -------------------------------------------------------------------------------- 「任务 → 下载」新增「下载到本机」列表：能看到每个下…
CloudDrive2 1.0.16 更新说明 Windows 1.0.16.1 · macOS 直接下载版 1.0.16 (9)（Apple Silicon + Intel）· Android 1.0.16（versionCode 333）· Apple 四端 TestFlight 1.0.16 (9) Meta Quest VR 本次不更新。 ★ Windows 用户请优先升级 -------------------------------------------------------------------------------- 如果你之前打开任何视频或音乐都提示「此版本未包含播放引擎」、完全播不了，这一版修好了。 原因是播放引擎依赖了一个由显卡驱动附带安装的组件，部分电脑上没有它。现在应用自带了。 字幕 ---------------------------------------------------…
CloudDrive2官网已全面改版，有关于CloudDrive2 App的详细说明，及终身会员升级App Pro会员的福利 https://www.clouddrive2.com
CloudDrive2 App 更新 —— v1.0.14（build 7）：杜比视界 P7 增强层，终于播出来了 🎬 本次最大的变化：**杜比视界 Profile 7 的增强层（FEL）现在由 App 自己实时合成**，本次可在 Windows、macOS 直接下载版、Android 手机 / 平板 / TV 上使用；macOS / tvOS / visionOS 的 App Store 版与 Meta Quest VR 版本次不更新，暂不包含该功能。此前这类片源（蓝光原盘及其重封装最常见的档次）在没有杜比视界解码芯片的设备上只播基础层、按 HDR10 呈现，增强层携带的暗部与高光细节全部丢失。 同时修复了两个长期影响体验的问题：播放中切换字幕 / 音轨要等几十秒才生效；以及高负载下挂载可能长时间无响应。 ================================================== 下载 / 获取 …
v1.0.14(Web3.0.14) 1. 新增帐号注销功能，在个人资料里可以选择注销帐号，注销帐号需要向注册邮箱发送确认码，输入确认码后方能注销，设备自动注册的帐号和迅雷帐号如需注销帐号，请先在个人资料里修改邮箱及密码后再注销帐号。注销帐号后帐号内的余额和会员权限将全部取消，不支持退款 2. 修复高负载下挂载盘卡死 —— 传输繁忙、并发访问较多时，挂载的网盘曾可能长时间无响应（极端情况可达数小时）。现已彻底修复：繁忙时访问平滑排队不再卡死，个别请求异常也会及时返回错误、系统自动恢复 3. 限速更平滑，更不易触发 115 等网盘的风控；提高限速设置后立即生效 4. 修复 115 新建文件夹后偶发"文件不存在"/同名冲突 —— 刚建好的文件夹因网盘索引有几秒延迟而被误判，现在会自动识别延迟并短暂重试，操作可正常完成 5. 备份更可靠 —— 遇网络抖动等临时问题自动重试，不再直接跳过（减少漏备份） 6. 修复备份把"文件夹"误当"…
CloudDrive2 App 更新 —— v1.0.14（build 6）：Windows 版首发 🪟🎉 本次更新最大的变化：**CloudDrive2 原生 Windows 客户端首次公开发布**，功能与 macOS 直接下载版（Developer ID）完全一致，包括蓝光 BD-J 光碟菜单、免挂载播放蓝光 / SACD 镜像、ASIO 原生 DSD。 同时：Emby / Jellyfin 全平台接入 CloudDrive 服务端插件（自动路径映射、.strm 直连播放）；Android 杜比视界 Profile 5 在无杜比视界芯片的设备上终于能输出色彩正确的 HDR10；直接下载 / 非应用商店渠道现在支持站内购买（支付宝 / 余额 / 优惠券 / 激活码）。 ================================================== 下载 / 获取 ===================…
🎉 CloudDrive2 × Emby / Jellyfin 服务端插件正式发布 v1.0.0 把 Emby / Jellyfin 与同一台机器上的 CloudDrive2 连起来。 装插件就能用 —— 前两项功能完全不需要安装 CloudDrive2 App。 ━━━━━━━━━━━━━━━━ 📌 核心：媒体库实时更新，而且可以把「实时监控」全部关掉 以前是个两难： • 开实时监控 —— Linux 的 inotify 不支持递归监视，Emby/Jellyfin 必须先把整个媒体库目录树递归遍历一遍，给每一个子目录单独注册 watch。库挂在网盘上，就等于每次启动都要把整棵目录树从云端重新列一次：启动慢得离谱，还打出一大片云端请求。 • 关实时监控 —— 那个媒体库就完全无人监视，只能等定时整库扫描。而整库扫描正是网盘风控封号的主要原因。 装上插件后不用再选了：插件直接订阅 CloudDrive2 的文件变化推…
CloudDrive2 App 测试版更新 —— v1.0.12（build 3）：全平台流式 PDF 阅读器 + Apple 真杜比视界 P7 🎉 本次更新带来两大跨平台能力：全新的「流式 PDF 阅读器」覆盖全平台；Apple 端的「真杜比视界 Profile 7」现已可在直接播放与蓝光光碟菜单模式下输出。Android、Meta Quest 同步更新。 ================================================== 下载 / 获取 ================================================== • Android App（手机 / 平板 / TV）+ macOS 直接下载版（Developer ID，含本地挂载）： https://github.com/cloud-fs/cloud-fs.github.io/releases/tag/app…
V1.0.13(Web3.0.13) 1. 多网盘备份增加全量扫描资源占用控制功能：1) 默认并发备份扫描数为1，可以在备份页面修改最大并发数，超过的备份全量扫描会排队等待; 2) 可以设置上传任务队列上下限，当上传任务数超过设置的上限时，扫描任务会暂停等待，当上传任务数回落到设置的下限时，扫描任务自动恢复，避免因扫描大文件造成太多上传任务堆积，默认为不限制，可以在备份页面修改 2. 跨云盘复制时，可在系统设置下载上传页面设置是否在计算哈希阶段将下载的数据保存到临时文件，上传时将无需再次下载源文件，复制完成后临时文件自动删除，该选项默认为关闭 3. Windows版修复在系统文件管理器对挂载盘图片编辑时可能出错，执行图片旋转后缩略图不自动刷新的问题 4. 修复Web界面实时显示的任务数可能不准确的问题 5. Web界面修复把本地文件拖动到根目录会产生一个无法完成的上传任务，并且创建一个无法删除的文件的问题 https://g…
Showing the 12 most recent of 29 posts we hold for @cloud_nas. 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.
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 27 August 2026 — this entry's latest reading, not the date you are reading this.
“CloudNAS” (@cloud_nas), 11,686 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/cloud_nas.
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.