有在马来的同学吗

Channel
RuiCloud锐云@私房菜
@RuiCloud
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
1,331subscribers
+17 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001310711370 |
|---|---|
| Type | Channel |
| Username | @RuiCloud |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 10 October 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 10 October 2026 |
| On Telegram | t.me/RuiCloud |
Topic
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 18 September 2026 and assigned it the closest of 31 fixed categories, at 84% 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 |
|---|---|---|
| 10 Oct 2026, 20:40 | 1,331 | -1 |
| 4 Oct 2026, 19:59 | 1,332 | +1 |
| 25 Sept 2026, 13:15 | 1,331 | +1 |
| 12 Sept 2026, 18:59 | 1,330 | +5 |
| 3 Sept 2026, 10:47 | 1,325 | -2 |
| 31 Aug 2026, 01:17 | 1,327 | +2 |
| 28 Aug 2026, 07:54 | 1,325 | +2 |
| 25 Aug 2026, 14:25 | 1,323 | +1 |
| 19 Aug 2026, 16:23 | 1,322 | +2 |
| 16 Aug 2026, 18:38 | 1,320 | +2 |
| 13 Aug 2026, 12:34 | 1,318 | +1 |
| 10 Aug 2026, 21:45 | 1,317 | +3 |
| 7 Aug 2026, 05:16 | 1,314 | no change |
| 7 Aug 2026, 05:09 | 1,314 | first reading |
Engagement
20 posts held, back to 15 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 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 2 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
Location, posted without a caption
#通知 所有预定的 香港BGP优化 TC专线 基本已交付完, 如有遗漏请 @Sam94566
海外BGP线路开始陆续按订单交付, 请私聊提供网站账号
#维护通知 海外BGP线路: 因为月底线路扩容,其中传输环节有施工作业影响导致电信方向故障,目前已经保障给上游传输运营商! 预计很快恢复!!!
#通知 江苏联通因海外流量占比问题,上游要求上调价格。 即日起我们将对定价进行小幅度调整,持有该线路产品用户请知悉!
#资源动态 承接: 腾讯BGP,华为BGP等云厂入口专线 国内单线入口专线 海外入口专线(回程优化,可电信优化) 国内单线公网(电信,联通,移动) 国内融合多线(公网): 电信+移动,联通+移动,电信+联通 华为BGP+移动|联通 腾讯BGP+移动|联通 ps:国内线路存在起订量+押金,具体详询 7x24小时热线: @Sam94566
#资源动态 香港BGP专线、开放老客户预定! (海外入口,回程优化,月底交付) Ps: 着急的话,可马上交付 ——————国内资源—————— 承接国内5-10-100G 大带宽单线、多线、BGP、IEPL定制业务! 业务无违规通报,可提供各种线路 ————————————————— 业务详询 @Sam94566
#维护通知 海外BGP专线-电信方向,,临时网络割接,可能会有1分钟左右的网络波动
#资源动态 极致优化,海外BGP入口(专线)私人定制款
#资源动态 对于海外BGP专线的高端线路套餐,为实现双向BGP线路智能分流,我们于近日投入巨资部署了路由设备,并于今日正式上线投入使用。 目前智能分流能根据国内访客IP所属运营商进行对应回程优化,具体分流效果示例如下: 移动方向访问,回程走移动 联通方向访问,回程走联通 电信方向访问,回程走电信 ———————————————————- 近期可接资源: 海外BGP专线系列 国内专线(单线入口,云厂BGP入口) 国内单线(移动、联通、电信) 融合多线:电信或联通入 联通或移动出 可包 5G-10G-100G 端口,提供独立物理机;可接托管 Ps:国内入口资源需要押金上量,自带前置可免押 业务详询 @Sam94566
开始交付,预定了该产品的用户请私聊 @Sam94566
Showing the 12 most recent of 20 posts we hold for @RuiCloud. 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.
Mentions
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.
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 10 October 2026 — this entry's latest reading, not the date you are reading this.
“RuiCloud锐云@私房菜” (@RuiCloud), 1,331 subscribers as measured 10 October 2026. Telegram Register, tgregister.com/channel/RuiCloud.
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.