Telegram RegisterThe public register of Telegram
Telegram profile photo for 星链云机场|VPN|科学上网

Channel

星链云机场|VPN|科学上网

@xlcloud

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

3,387subscribers

+39 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001889607949
TypeChannel
Username@xlcloud
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live18 September 2026
Measurements held14
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/xlcloud

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 14 September 2026 and assigned it the closest of 31 fixed categories, at 88% 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

3,3403,3873,363.56 August 2026 — 3,348 subscribers6 August 2026 — 3,348 subscribers9 August 2026 — 3,349 subscribers12 August 2026 — 3,351 subscribers16 August 2026 — 3,349 subscribers19 August 2026 — 3,340 subscribers23 August 2026 — 3,343 subscribers26 August 2026 — 3,340 subscribers29 August 2026 — 3,346 subscribers1 September 2026 — 3,361 subscribers5 September 2026 — 3,371 subscribers10 September 2026 — 3,378 subscribers14 September 2026 — 3,384 subscribers18 September 2026 — 3,387 subscribers6 August 202618 September 2026
14 measurements spanning 43 days, net +39. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 3,333–3,394 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 06:403,387+3
14 Sept 2026, 11:223,384+6
10 Sept 2026, 13:203,378+7
5 Sept 2026, 13:573,371+10
1 Sept 2026, 12:363,361+15
29 Aug 2026, 19:273,346+6
26 Aug 2026, 14:093,340-3
23 Aug 2026, 09:353,343+3
19 Aug 2026, 12:463,340-9
16 Aug 2026, 08:243,349-2
12 Aug 2026, 17:283,351+2
9 Aug 2026, 19:223,349+1
6 Aug 2026, 20:333,348no change
6 Aug 2026, 09:363,348first reading

Engagement

21 posts held, back to 5 June 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 3 pages 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 21 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

29 reactions across 8 posts, in 2 distinct kinds. The most used accounts for 65.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1965.5%
❤1034.5%

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 14 of the 21 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 29 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 21 most recent posts we hold, published 5 June 2026 to 7 August 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.

Recent posts

7 Aug 2026, 09:33 UTC219 views2 reactionsread 7 August 2026

开业3年多之前的老域名都被污染了,大家请收藏好我们的入口,这边会定时更新域名。

❤2

5 Aug 2026, 05:12 UTC532 views3 reactionsread 7 August 2026
Photo

比机场稳定 正规渠道和国内运营商合作 国内能用的ESIM卡:香港,日本,新加坡,美国 买了这些地区一样能翻墙 出发前装好,落地就能上网 ✈️ 青柠 eSIM 提供多国流量套餐: ✓ 不用更换实体卡 ✓ 在线购买,扫码安装 ✓ 日本、韩国、泰国、欧洲、美国等目的地可选 ✓ 支持支付宝、微信支付和 USDT 建议出发前完成安装,抵达目的地后再开启数据漫游。 点击主页链接选择旅行套餐。 #出境旅行 #日本旅行 #韩国旅行 #eSIM #旅行上网 前往购买ESIM: https://www.limeesim.com/r/55CE552EB7

👍3

30 Jul 2026, 08:24 UTC≈1,190 views5 reactionsread 7 August 2026
Photo

新增美国住宅IP,(双Isp)只能添加链式代理使用,可前往官网文档获取。

❤5

29 Jul 2026, 06:29 UTC≈1,250 views6 reactionsread 7 August 2026
Photo

官网添加新功能,每天签到获得流量。

👍6

25 Jul 2026, 11:46 UTC≈1,790 views9 reactionsread 7 August 2026

最近防火墙发力了,一天墙几十个IP。现在已经找到新资源,优点稳定,缺点就是宽带小。

👍9

23 Jul 2026, 09:48 UTC≈12,700 viewsread 7 August 2026
Photo

湖南图书馆因读者翻墙违规临时关停公用 Wi-Fi 湖南图书馆发布公告称,因部分读者连接馆内公用 Wi-Fi 后擅自使用翻墙软件访问境外违规网站,引发异常流量并造成网络安全隐患,自 2026 年 7 月 22 日起临时关停馆内公用 Wi-Fi 进行整改。公告显示,相关行为涉嫌违反《中华人民共和国网络安全法》,已有部分涉事手机号被核实。 整改期间,馆内公用 Wi-Fi 将全面关闭,待网络安全排查、系统加固及调试完成后视实际情况逐步恢复,具体时间另行公告。馆方强调,将对读者入网违规行为“零容忍”,一经查实将永久禁止涉事手机号接入,情节严重涉嫌违法的,将依法移交公安、网信等部门处置-最好是不要用公告网络翻墙

21 Jul 2026, 13:25 UTC≈1,910 viewsread 7 August 2026

3.0客户端-在(我的-工具设置-进阶配置-DNS-打开DNS复写)

18 Jul 2026, 05:53 UTC≈2,270 views0 reactionsread 7 August 2026

推广佣金上调30%👉35%,可提现可购买套餐。暑期8折优惠码:ZEY9

18 Jul 2026, 05:10 UTC≈2,260 views1 reactionsread 7 August 2026

最近anytls协议大量被墙出现Timeout没关系一样能用,现在入口几台服务器轮询,机器挂了基本无感。

👍1

11 Jul 2026, 17:47 UTC≈2,990 views0 reactionsread 7 August 2026

无法连接到api,主机不可用?尝试以下方法排查 1,windows用户不能安装在路径不能有中文,不然软件无法获取权限,安装后右键给予管理员运行 2,显示没订阅是电脑权限问题,客户端登录后如果出现无节点状态可以重新登录获取API 3,安装了杀毒软件(360,腾讯管家,火绒)之类的卸载后重启节点就正常了,这些软件都有流量监控功能会接管代理流量。 4,如果是1.2.1-2.2.3版本升级到3.0版本试试,或者可以安装另外几个客户端。 5,IOS如果无法使用可能是远古版本,建议更新到最新版本

Showing the 12 most recent of 21 posts we hold for @xlcloud. 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

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 18 September 2026 — this entry's latest reading, not the date you are reading this.

“星链云机场|VPN|科学上网” (@xlcloud), 3,387 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/xlcloud.

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.