Channel
@halocloudinfo
On this record: Growth · Engagement · Posts · Citations · Cite this entry
2,743subscribers
+10 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001371186662 |
|---|---|
| Type | Channel |
| Username | @halocloudinfo |
| Created | 10 June 2020 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 7 August 2026 |
| Last confirmed live | 27 August 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 27 August 2026 |
| On Telegram | t.me/halocloudinfo |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Aug 2026, 06:13 | 2,743 | +6 |
| 24 Aug 2026, 08:05 | 2,737 | +5 |
| 14 Aug 2026, 10:26 | 2,732 | -4 |
| 11 Aug 2026, 09:33 | 2,736 | +3 |
| 7 Aug 2026, 09:31 | 2,733 | no change |
| 7 Aug 2026, 09:23 | 2,733 | first reading |
20 posts held, back to 13 July 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 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 1 August 2026 |
|---|---|
| Posts held | 20 (13 July 2026 – 1 August 2026) |
| Views total | 6,532 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 16:12 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.
国际站新加坡区域迁移完成通知 尊敬的用户： 新加坡区域迁移及网络调整工作现已全部完成，相关产品及网络服务已于： 2026 年 8 月 2 日 01:00（北京时间，UTC+8） 恢复正常。 本次不可用时间自 2026 年 7 月 31 日 11:00 起计算，至 2026 年 8 月 2 日 01:00 恢复，共计： 38 小时 按照此前公告中的补偿规则： 实际不可用时长 × 1.5 倍，并向上取整至完整天数 本次补偿时长为 57 小时，向上取整后，统一补偿： 3 天有效期 补偿将统一添加至受影响产品的有效期，无需重复提交工单。请用户及时检查业务运行状态；如恢复后仍存在连接异常，请通过工单联系我们处理。 对于本次迁移给您带来的不便，我们深表歉意，感谢您的耐心等待与理解配合。 HaloCloud Network Limited
国际站新加坡区域迁移进度更正通知 尊敬的用户： 经进一步检查，新加坡区域迁移工作尚未完全完成，部分产品及网络服务仍存在异常。此前发布的《国际站新加坡区域迁移完成通知》现予以撤回，其中关于服务已恢复及补偿时长的内容不再作为最终结算依据。 目前迁移及网络调整工作仍在继续。实际不可用时长将继续从 2026 年 7 月 31 日 11:00（北京时间，UTC+8） 起累计计算，直至相关产品及网络服务确认完全恢复。 最终补偿仍按照此前公告规则执行： 实际不可用时长 × 1.5 倍，补偿至对应产品有效期。 具体恢复时间及最终补偿时长，请以我们后续发布的正式通知为准。在此期间请耐心等待，无需重复提交工单。 对于本次通知更正及迁移延长给您带来的不便，我们深表歉意，感谢您的理解与配合。 HaloCloud Network Limited
国际站新加坡区域迁移完成通知 尊敬的用户： 新加坡区域迁移工作现已全部完成，相关产品及网络服务已于 2026 年 7 月 31 日 23:00（北京时间，UTC+8） 恢复正常。 本次迁移期间，服务自 11:00 起停止，至 23:00 恢复，实际不可用时长为 12 小时。按照此前公告中“实际不可用时长按 1.5 倍补偿至产品有效期”的规则： 12 小时 × 1.5 = 18 小时 因此，所有参与本次迁移的产品将统一补偿 24 小时有效期。补偿将陆续添加至对应产品，请耐心等待。 请各位用户及时检查产品运行及网络连接情况，如发现异常，请通过工单联系我们处理。 感谢您的理解与配合。 HaloCloud Network Limited
国际站新加坡区域迁移补充通知 尊敬的用户： 新加坡区域退款及不迁移申请的提交期限已于 2026 年 7 月 31 日 00:00（北京时间，UTC+8）截止。由于申请时间已经结束，目前已不再支持任何拒绝迁移、不参与迁移或例外处理的选项，亦不接受以任何理由补交相关申请。 所有新加坡区域产品将按照既定方案统一进行迁移，请相关用户配合迁移安排，并耐心等待服务恢复。 如产品符合服务条款（TOS）规定的常规退款条件，用户仍可按照现行 TOS 提交退款申请。退款资格、金额及处理方式均以 TOS 为准，不再适用迁移专项退款方案。 感谢您的理解与配合。 HaloCloud Network Limited
国际站新加坡区域停机迁移最终通知 尊敬的用户： 新加坡区域产品的退款及不迁移申请将于 2026 年 7 月 31 日 00:00（北京时间，UTC+8）截止。截止后，我们将不再接受相关申请；未在规定时间内提交申请的用户，将视为接受本次迁移安排。 我们计划于 2026 年 7 月 31 日 11:00（北京时间，UTC+8）暂停新加坡区域相关服务，并正式开始迁移操作。 迁移期间，相关产品将暂时无法使用，迁移及网络恢复预计需要数天时间。请您务必提前备份重要数据，并妥善安排相关业务，以避免造成不必要的损失。 迁移完成并恢复服务后，我们将另行发布通知。 感谢您的理解与配合。 HaloCloud Network Limited
使用小技巧 HaloCloud 中国站客户可以直接导入你的服务器哟
HaloShell 已发布新版本： 桌面端：v1.0.0 移动端：v1.0.0 修复部分已知问题 优化功能细节 改善整体使用体验 下载地址： iOS： https://apps.apple.com/app/id6778709602 桌面端及安卓平台： https://haloshell.halocloudnet.com/ 了解HaloShell：https://www.halocloudnet.com/haloshell
🧭 HaloCloud 国内站在售产品如下 💼 独享产品 1. 深港 IEPL 专线 支持入口：广东电信、广东移动、广东联通、广东三线、广州BGP 香港 BGP 出口：HKIX、EIE、NTT、PCCWG、TATA、Telia、Cogent、HE、RETN、Lumen 延迟：1.5–2ms 需要押一付一。 不承接存在通报风险或违规用途的业务。请勿以“绝对不会被通报”等口头承诺作为免除押金的依据，我司不接受任何形式的口头保证。
沪日 卒 发工单申请退款
HaloAI Token Plan 大抽奖！！ 点击参加 https://my.halocloud.net/index.php?m=HaloAI&page=raffle_public
🧭 HaloCloud 国内站在售产品如下 💼 独享产品 1. 深港 IEPL 专线 支持入口：广东电信、广东移动、广东联通、广东三线、广州BGP 香港 BGP 出口：HKIX、EIE、NTT、PCCWG、TATA、Telia、Cogent、HE、RETN、Lumen 延迟：1.5–2ms 需要押一付一。 不承接存在通报风险或违规用途的业务。请勿以“绝对不会被通报”等口头承诺作为免除押金的依据，我司不接受任何形式的口头保证。
Opus 5 已上线 HaloAI！ 了解 Opus 5： https://www.anthropic.com/news/claude-opus-5 👉 使用入口： my.halocloud.net/index.php?m=HaloAI
Showing the 12 most recent of 20 posts we hold for @halocloudinfo. 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 — 1,255,639 of 1,621,754entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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.
“HaloCloud通知频道” (@halocloudinfo), 2,743 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/halocloudinfo.
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.