Channel
@SurgeChannel
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
4,782subscribers
+4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001715468006 |
|---|---|
| Type | Channel |
| Username | @SurgeChannel |
| Description | Surge唯一官方频道：https://t.me/SurgeTestFlightFeed 以下为第三方创建： 群连接 https://t.me/+TO9iLpyTE1FjZTM1 群频道 https://t.me/+nZUgB3lPosQ2Y2Y1 |
| Created | Between 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 10 August 2026 |
| On Telegram | t.me/SurgeChannel |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 20:41 | 4,782 | +4 |
| 8 Aug 2026, 03:52 | 4,778 | no change |
| 7 Aug 2026, 09:47 | 4,778 | first reading |
20 posts held, back to 6 August 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 8 pagesof 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 1 July 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
分享一个我最近做的 macOS App：Surge Relay GitHub： https://github.com/EEliberto/SurgeRelay-macOS 主要是给 Surge 用户管理模块用的，尤其是经常用 Script-Hub 把 Loon / Quantumult X 模块转成 Surge .sgmodule 的场景。 之前最大的问题是：上游作者一改仓库地址或文件路径，Surge 里已经装好的模块就很难批量维护，多台设备还要重复处理。这个 App 就是把这些操作集中到一台 Mac 上完成。 目前支持： • 统一管理模块来源和备用地址 • 调用 Script-Hub 本地转换逻辑 • 生成稳定的 .sgmodule • 发布到 GitHub 或 iCloud Drive • 编辑 / 删除 / 汇总模块 • 屏蔽 MITM hostname • 禁用部分 Script / Rewrite • Web…
Signed 🅼🅄🆃🅄
已适配 iOS 26 UI 的新版本 Surge iOS 5.16.0，由于近期 App Store 审核工作量较大，依然在排队等待审核中。
#iOS #TestFlight Surge 5 5.101.0 (3572) is ready to test on iOS. What to Test: - 细节优化与修正 5.16.0 RC1 Official Channel: @SurgeTestFlightFeed
#iOS #TestFlight Surge 5 5.101.0 (3571) is ready to test on iOS. What to Test: - 修正卡片自定义页面的问题 - Widget 全面适配 iOS 26 的各种风格选项 Official Channel: @SurgeTestFlightFeed
#iOS #TestFlight Surge 5 5.101.0 (3570) is ready to test on iOS. What to Test: - 重做请求页过滤器系统，以适配 iOS 26 - 其他细节修正 Official Channel: @SurgeTestFlightFeed
#iOS #TestFlight Surge 5 5.101.0 (3569) is ready to test on iOS. What to Test: - 全面细节优化 - 卡片页开始按钮新增长按菜单，作为 iOS 26 上的 tab bar 菜单替代 Official Channel: @SurgeTestFlightFeed
#iOS #TestFlight Surge 5 5.101.0 (3568) is ready to test on iOS. What to Test: - 使用 iOS 26 SDK 编译，全面适配 iOS 26 UI。 原本我们打算借机重新设计 Surge iOS 的 UI，但是进度较慢，预计要到年末完成，因此目前先在当前 UI 上进行 iOS 26 的适配工作。 （图标尚未适配） - 优化 HTTP 引擎的兼容性 Official Channel: @SurgeTestFlightFeed
#iOS #TestFlight Surge 5 5.101.0 (3567) is ready to test on iOS. What to Test: - 外部 IP 展示新增 ASN/ASO 信息 Official Channel: @SurgeTestFlightFeed
#iOS #TestFlight Surge 5 5.101.0 (3566) is ready to test on iOS. What to Test: Bug fixes Official Channel: @SurgeTestFlightFeed
#iOS #TestFlight Surge 5 5.101.0 (3565) is ready to test on iOS. What to Test: - 完成代理的外部 IP 检查功能和 NAT 类型测试 - [Host] 段正式支持 IP 地址请求的映射（先前版本仅支持代理模式下的映射，现在同时支持直连情况下的映射） - 修正 timeout 相关参数，写入配置时无法保留小数的问题 Official Channel: @SurgeTestFlightFeed
#iOS #TestFlight #订阅功能 Surge 5 5.101.0 (3562) is ready to test on iOS. What to Test: 新的订阅功能：外部 IP 与 NAT 类型查看 - 可在网络诊断页面查看当前网络的外部 IPv4 地址和 NAT 类型 - 该功能稍后将扩充至代理线路的外部 IPv4 地址和 NAT 类型查看 - 修正在开启状态下清除统计数据会导致日志持续报错的问题 - 其他细节问题修正 Official Channel: @SurgeTestFlightFeed
#iOS #AppStore Version 5.15.2 Release Date: 2025/8/13 14:30:07(UTC+08:00) What’s New: Bug fixes and minor enhancements Official Channel: @SurgeTestFlightFeed
Showing the 12 most recent of 20 posts we hold for @SurgeChannel. 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.
Citation-graph rank — 992,867 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“Surge Channel” (@SurgeChannel), 4,782 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/SurgeChannel.
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.