14 Jun 2026, 09:01 UTC≈1,770 viewsread 7 August 2026
NAT站通知： 日本DC2 上游更换了IP段 现已替换新的IP地址数据不变 用户中心查看最新IP地址
Channel
帕斯云频道
@pasyun1
On this record: Growth · Engagement · Posts · Telegram's recommendations · Cite this entry
2,007subscribers
+79 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 | -1002081276136 |
|---|---|
| Type | Channel |
| Username | @pasyun1 |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/pasyun1 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 06:47 | 2,007 | +11 |
| 27 Aug 2026, 15:13 | 1,996 | +20 |
| 24 Aug 2026, 06:36 | 1,976 | +16 |
| 20 Aug 2026, 17:47 | 1,960 | +17 |
| 17 Aug 2026, 21:03 | 1,943 | +3 |
| 14 Aug 2026, 13:19 | 1,940 | +12 |
| 7 Aug 2026, 17:33 | 1,928 | no change |
| 7 Aug 2026, 17:15 | 1,928 | first reading |
Engagement
20 posts held, back to 10 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 pageof 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 14 June 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
14 Jun 2026, 08:52 UTC≈1,730 viewsread 7 August 2026
轻量站通知：不要在节点丢包的时候去重装系统，这样会卡住，一直在重装中卡住，一般丢包不会持续很久 ，我发现只要一丢包就有人去喜欢重装系统
13 May 2026, 06:25 UTC≈2,670 viewsread 7 August 2026
美国故障 已通知机房排查
23 Apr 2026, 09:12 UTC≈3,190 viewsread 7 August 2026
轻量站通知 美国DC1 DC3 维护中 升级CPU 预计48小时恢复 结束后3倍故障补偿 美国DC3已维护完成 特殊原因需要更换IP 已更换完成 数据不变 故障时长24小时 按三倍补偿 额外再补偿12天共计补偿15天 美国DC1已维护完成 特殊原因需要更换IP 已更换完成 数据不变 故障时长24小时 按三倍补偿 额外再补偿12天共计补偿15天
22 Apr 2026, 04:30 UTC≈2,670 viewsread 7 August 2026
【NAT站通知】 因土耳其上游服务商跑路，该地区服务无法继续提供。本次事件导致我方产生5,000土耳其里拉的损失。已为购买土耳其地区的用户完成退款，款项已退回至账户余额。 【轻量站通知】 1. 意大利DC4、DC5节点：因上游服务商质量不达标，已予以下架。相关用户的购买款项已全额退回至账户余额。 2. 意大利DC1、DC2、DC3节点：母机尚未到期，待到期后将正式下架，届时对应款项也将退回至用户余额。 【整体说明】 经过本次调整，所有稳定性不达标的地区已完成清理。目前保留的服务地区均处于稳定运行状态。
27 Mar 2026, 03:32 UTC≈3,170 viewsread 7 August 2026
关于本项目服务稳定性说明： 本项目已稳定运行多年，采用自动化监控机制，无需人工实时值守。如遇机器故障，我会及时处理并按规则进行相应补偿。 日常运维采用"付费地区全节点在线"策略，确保核心服务质量。我的时间需要兼顾工作与生活，不会耗费在已高度自动化的3元级项目上。 另：对于无关质疑或恶意诋毁，无论出于同行竞争或其他目的，请理性发言。无根据的指责既无助于问题解决，也损害沟通效率，望自重。
13 Mar 2026, 04:17 UTC≈3,380 viewsread 7 August 2026
NAT站通知： 60+台母鸡 两会期间部分被墙 已全部恢复 使用特殊方法 可以快速解决被墙母鸡 看来这个方法真实有效 并且不需要限制任何协议 即可做到快速解除被墙限制 最快24小时即可解除被墙母鸡
6 Mar 2026, 08:44 UTC≈3,650 viewsread 7 August 2026
NAT站通知： 两会期间被墙很正常 这种常识问题 都要来群里一个劲叫个不停 就不适合用NAT 自己去买独立IP的机器吧 我不是GFW防火墙工作人员 被墙问题不要找我 被墙问题 过了这几天就好了 由于NAT共享IP的特性所以NAT被墙我们不提供更换IP 做了一个搭建节点的一键脚本，被墙也不影响使用 curl https://suoha.psai.eu.org/suoha.sh -o suoha.sh && chmod +x suoha.sh && bash suoha.sh
6 Mar 2026, 08:31 UTC≈2,820 viewsread 7 August 2026
NAT站通知： ipv6无售后
3 Mar 2026, 08:12 UTC≈3,150 viewsread 7 August 2026
Photo
荷兰上游跑路了我在他那购买了6台年费机器全部没了 正在购入新的荷兰机器替换 最新通知： NAT站荷兰地区已全部替换完毕 轻量站荷兰地区已全部替换完毕重装系统即可继续使用 NAT站 香港DC6 香港DC7 已更换至香港DC1 香港DC2三网全绿 直连线路 带宽降低 轻量站 香港DC3有人拿去爆破 机器被封刚交了10美元解封 滥用者邮箱 已封号处理 [email protected] 其他60+地区母鸡节点全部在线全部正常
14 Feb 2026, 15:52 UTC≈3,090 viewsread 7 August 2026
【轻量站通知】 荷兰节点IPv6故障已修复！已分配全新IPv6地址，原有数据不变，请登录用户中心查看。 为表歉意，所有用户（新购/老用户）统一补偿3个月服务期！此次补偿由我们个人承担，虽然上游没给赔偿，但我们的用户我们自己宠！ 目前所有母鸡均已恢复正常。假期中，其他问题将于24号后处理。祝大家新年快乐！
26 Jan 2026, 13:06 UTC≈4,030 viewsread 7 August 2026
轻量站通知： 晚些时候下架一些垃圾上游 不稳定频繁出现问题地区： 意大利（梵蒂冈 朝鲜 南极洲）永久下架 荷兰（荷兰只临时下架上游分配新ipv6后重新上架） ipv6已恢复 已上线
Showing the 12 most recent of 20 posts we hold for @pasyun1. 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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
CMLiussss 技术干货分享
@CMLiussss_channel · 66,309
Telegram ranks this channel #4 of 47 here — alongside 46 others — read 21 August 2026
@CMLiussss_channel · 66,309
Telegram ranks this channel #4 of 47 here — alongside 46 others — read 21 August 2026
Matsuridayo GitHub
@MatsuriDayo · 45,248
Telegram ranks this channel #40 of 58 here — alongside 57 others — read 30 August 2026
@MatsuriDayo · 45,248
Telegram ranks this channel #40 of 58 here — alongside 57 others — read 30 August 2026
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“帕斯云频道” (@pasyun1), 2,007 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/pasyun1.
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.