Telegram RegisterThe public register of Telegram
Telegram profile photo for SakuraFrp 状态通知

Channel

SakuraFrp 状态通知

@natfrp_status

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

4,298subscribers

+73 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001191807391
TypeChannel
Username@natfrp_status
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live6 October 2026
Measurements held14
Confirmed unchanged1 time, most recently 6 October 2026
On Telegramt.me/natfrp_status

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

4,2254,2984,261.57 August 2026 — 4,225 subscribers8 August 2026 — 4,227 subscribers12 August 2026 — 4,231 subscribers15 August 2026 — 4,238 subscribers18 August 2026 — 4,246 subscribers21 August 2026 — 4,250 subscribers24 August 2026 — 4,257 subscribers27 August 2026 — 4,258 subscribers3 September 2026 — 4,257 subscribers8 September 2026 — 4,267 subscribers12 September 2026 — 4,279 subscribers15 September 2026 — 4,281 subscribers29 September 2026 — 4,292 subscribers6 October 2026 — 4,298 subscribers7 August 20266 October 2026
14 measurements spanning 59 days, net +73. 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 4,214–4,309 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Oct 2026, 06:164,298+6
29 Sept 2026, 10:024,292+11
15 Sept 2026, 20:214,281+2
12 Sept 2026, 12:214,279+12
8 Sept 2026, 12:584,267+10
3 Sept 2026, 02:294,257-1
27 Aug 2026, 14:034,258+1
24 Aug 2026, 22:284,257+7
21 Aug 2026, 07:584,250+4
18 Aug 2026, 17:074,246+8
15 Aug 2026, 18:534,238+7
12 Aug 2026, 00:424,231+4
8 Aug 2026, 20:524,227+2
7 Aug 2026, 22:454,225first reading

Engagement

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

Reaction mix

44 reactions across 7 posts, in 7 distinct kinds. The most used accounts for 36.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🐳1636.4%
👏920.5%
😨818.2%
❤511.4%
👍36.82%
🤯24.55%
🔥12.27%

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

Measured over the 20 most recent posts we hold, published 30 March 2026 to 5 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

5 Aug 2026, 06:40 UTC213 viewsread 8 August 2026

节点 #22 [VIP]西安三线PLUS1 长时间连接中断, 可能已离线 Last Seen: 2026-08-05 14:38:37 ✅ #已恢复 (2026-08-05 17:26:17)

5 Aug 2026, 06:38 UTC216 viewsread 8 August 2026

ℹ️ 节点 #22 [VIP]西安三线PLUS1 重启 Last Uptime: 3d 5h 38m

5 Aug 2026, 06:38 UTC217 viewsread 8 August 2026

节点 #22 [VIP]西安三线PLUS1 长时间连接中断, 可能已离线 Last Seen: 2026-08-05 14:36:28 ✅ #已恢复 (2026-08-05 14:38:37)

1 Aug 2026, 08:14 UTC559 viewsread 8 August 2026

由于节点端口资源耗尽,我们已删除位于 成都移动2、重庆三线PLUS4、重庆三线PLUS5、济南三线PLUS3、枣庄多线PLUS-扩容2、江苏镇江多线PLUS-扩容1 中超过 3 个月未被使用的隧道

1 Aug 2026, 05:29 UTC548 views0 reactionsread 8 August 2026

近期,我们陆续收到多条关于跨网访问体验下降的反馈。为改善整体使用体验,我们已于 2026 年 8 月 1 日完成以下节点的三线升级及扩容: - 济南联通PLUS1、2 -> 济南三线PLUS3、4 - 济南联通1(VIP)、3 -> 济南三线PLUS5(VIP)、6 - 重庆电信PLUS1、2 -> 重庆三线PLUS4、5 由于 DNS 缓存更新需要一定时间,如您在 48 小时内使用上述节点,可能出现隧道启动失败、无法访问等问题。如遇此类问题,请耐心等待或尝试更换系统 DNS、清除 DNS 缓存后再试。

23 Jul 2026, 13:15 UTC941 views3 reactionsread 8 August 2026

SakuraFrp 安全响应 我们收到关于 MCSManager 的一个漏洞提醒,并进行了研究。 此漏洞已被修复数日并可用于未授权直接控制您的服务器面板并升级到主机接管。 尽管我们尚未注意到,但在野利用随时可能出现并攻击您,我们建议您尽快更新面板程序。 我们初步审计认为,相关漏洞影响范围为 MCSManager v9 - v10.16.2 版本,如您在使用范围内版本,请及时更新到 v10.17.0 或更高。 对于暴露到公网的服务,我们始终建议您保持服务版本最新。 此外,如无特殊需求,我们总是推荐您为此类服务启用 访问认证 以减小攻击面。

👍3

19 Jul 2026, 08:30 UTC≈1,050 views16 reactionsread 8 August 2026
Sticker

Sticker, posted without a caption

🐳16

19 Jul 2026, 08:22 UTC≈1,310 views11 reactionsread 8 August 2026

SakuraFrp 紧急安全响应 我们收到关于 幻兽帕鲁(Palworld)的一个 RCE 漏洞信息。此漏洞目前并未公开披露,但我们的初步研究认为此信息值得引起重视。 在野利用随时可能出现并攻击您,我们建议您时刻关注官方信息,在游戏和服务端程序更新可用时立即进行更新。 此漏洞 可能: - 通过您的幻兽帕鲁游戏联网的行为(推测并不需要实际加入服务器),直接控制您的电脑; - 通过您的幻兽帕鲁服务器,直接控制您的服务器所在电脑。 更进一步的利用包括但不限于,通过幻兽帕鲁联机网络在服务器和用户中传播的木马。 对于暴露到公网的服务,我们通常建议您保持服务版本最新。 特别的,对于 UDP 服务您也可以开启 访问认证,在必要时请考虑如此操作。 如日后漏洞被披露而官方未做出反应,请避免将您的幻兽帕鲁游戏联网。

😨8🤯2🔥1

18 Jul 2026, 13:03 UTC931 viewsread 8 August 2026

SakuraFrp 紧急安全响应 我们注意到 WordPress 的一个鉴权绕过漏洞已被公开披露。 此漏洞的细节目前未获披露,但是我们已对相关可能的利用链进行研究、确认其真实存在并可造成严重后果。 在野利用随时可能出现并攻击您,请立即检查做出回应。 此漏洞可以直接通过您的 WP 应用控制您的服务器,并且可稳定触发。 如您穿透了 WordPress 6.9.0 之后的版本,请选择以下两者方法之一缓解此漏洞: 1. 更新到 6.9.5 或 7.0.2 之后的版本 2. 后台安装插件 Disable WP REST API 对于暴露到公网的服务,我们通常建议您保持服务版本最新。 但是对于功能强大,攻击面也强大的 WP 来说,保持一个安全的长期版本可能也是一种保护自己的手段。

14 Jul 2026, 04:40 UTC≈1,150 viewsread 8 August 2026

由于节点端口资源耗尽,我们已删除位于 长沙电信PLUS2、石家庄联通PLUS1、重庆电信PLUS1、重庆电信PLUS2、浙江移动PLUS1、长沙电信PLUS4、镇江多线PLUS-扩容2 中超过 3 个月未被使用的隧道

4 Jul 2026, 09:39 UTC≈1,770 viewsread 8 August 2026

《SakuraFrp 个人信息处理与隐私保护政策》 已于 2026/07/04 更新。 请您在继续使用本平台服务前仔细阅读相关内容。继续使用本平台即表示完全认可更新后的《隐私策略》内容,否则您应及时提交账户注销申请。 https://www.natfrp.com/policy/privacy

29 Jun 2026, 13:18 UTC≈1,930 viewsread 8 August 2026

我们已确认国际网络连接存在异常,非内地节点可能暂时无法正常开启隧道(已开启隧道不受影响),海外用户可能暂时无法访问网站和 API。 ✅ 已恢复 (22:21)

Showing the 12 most recent of 20 posts we hold for @natfrp_status. 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 6 October 2026 — this entry's latest reading, not the date you are reading this.

“SakuraFrp 状态通知” (@natfrp_status), 4,298 subscribers as measured 6 October 2026. Telegram Register, tgregister.com/channel/natfrp_status.

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.