⚙️ 【重要】客户端版本强制升级要求由于节点参数升级,客户端版本过低将直接导致节点无法使用。 请务必检查并升级: 💻 v2rayN (Windows):请使用 7.2 及以上版本(版本号在主界面左上角查看)。 📱 v2rayNG (Android):请使用 v2.17 及以上版本(版本号在“关于”中查看)。 📱 Clash Verge:请使用 v2.4.5 及以上版本(版本号在“设置”中查看)。 📱 Shadowrocket:教程里面提供免费共享账号,半年以上未更新请自行更新 🌐 其他客户端:若无法使用,大概率是版本过低不支持新参数,请前往【使用教程】重新下载最新版。 karing,nekobox等长期未更新的客户端暂时无法使用💡 提示:若版本低于上述要求,请直接前往官网【使用教程】页面重新下载安装。

Channel
佰速云-通知频道
@bscloud_notice
On this record: Topic · Growth · Engagement · Posts · Cite this entry
85subscribers
+1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002217782895 |
|---|---|
| Type | Channel |
| Username | @bscloud_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 | 9 August 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 6 times, most recently 11 October 2026 |
| On Telegram | t.me/bscloud_notice |
Topic
Other / unclassifiable — 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 27 September 2026 and assigned it the closest of 31 fixed categories, at 47% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 24 Aug 2026, 01:18 | 85 | +1 |
| 9 Aug 2026, 17:17 | 84 | no change |
| 7 Aug 2026, 13:01 | 84 | first reading |
Engagement
20 posts held, back to 29 September 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 31 July 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
近日墙加高了,我们对参数进行了优化,请参考网站弹窗公告进行客户端升级和订阅更新
由于节点大面积被墙,需要对节点参数进行升级,目前先添加了少量节点先用着, 其他节点需要点时间陆续添加,建议隔日后更新订阅!
近日由于服务器被封禁造成数据丢失,还有剩余时间的用户请重新注册等待订阅恢复(一天内),事后会统一补偿!
更新订阅
机房被拔线了,先用名字里面有直连的节点顶上,下午会加更多直连的,隧道中转节点等后面处理
对部分节点参数进行了安全优化,更新下订阅
近日已对大部分节点进行参数调整,用三方客户端的 请及时更新订阅
入口被dns污染了,更新一下订阅,近期还会加入新的入口域名,建议隔天更新下
邀请佣金改成了循环返利5%,首反的邀请不予计算(即被邀请用户后续每次充值都返利)
邀请佣金调整为首次50%返利,大于100可USDT(POL链) 申请提现(即被邀请用户首次充值购买年付72元,可得36佣金)
自研客户端已发布,无需繁琐的导入订阅,由于是纯手搓的BUG难免会有,有问题请及时反馈,目前只发布windows和安卓,其他系统后续发布 安卓客户端 https://share.feijipan.com/s/nzYhFXPn Windows解压版 https://share.feijipan.com/s/MqYhEadr
Showing the 12 most recent of 20 posts we hold for @bscloud_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.
Cite this entry
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 24 August 2026 — this entry's latest reading, not the date you are reading this.
“佰速云-通知频道” (@bscloud_notice), 85 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/bscloud_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.