Telegram RegisterThe public register of Telegram
Telegram profile photo for Surge TestFlight Feed

Channel

Surge TestFlight Feed

@SurgeTestFlightFeed

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

13,167subscribers

+343 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002003550519
TypeChannel
Username@SurgeTestFlightFeed
DescriptionThis channel provides information about the latest beta versions of Surge for iOS, Mac, and tvOS.
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 November 2026
Measurements held64
Confirmed unchanged1 time, most recently 13 November 2026
On Telegramt.me/SurgeTestFlightFeed

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 11 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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 the other topics.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 2 other registered channels. This entry also sits inside a group of 4 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

No sample pairs were kept for this entry. The counts below were measured, but without the pairs there is nothing here for you to open and check, so treat the relationship as recorded rather than demonstrated.

Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@SurgeTestFlight52 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (47–5)
@zhetengsha10 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (10–0)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 75 comparable posts for this entry, running 15 May 2026 to 12 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 4 channels, the one whose matching posts we hold earliest is @SurgeTestFlightChangelog. That channel is not among the channels listed above, so this entry may share no posts with it and this does not say where this entry’s content came from. It is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 13 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 4 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

12,82413,16712,995.56 August 202613 November 2026
64 measurements spanning 99 days, net +343. 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 12,773–13,218 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 64
Measured (UTC)SubscribersChange
13 Nov 2026, 00:0013,167+115
10 Nov 2026, 16:1013,052+5
9 Nov 2026, 01:4713,047+7
7 Nov 2026, 20:5913,040+7
6 Nov 2026, 18:3513,033+5
5 Nov 2026, 20:2013,028+7
4 Nov 2026, 18:0113,021+7
3 Nov 2026, 20:3013,014+9
2 Nov 2026, 20:0613,005+5
1 Nov 2026, 23:2513,000+13
31 Oct 2026, 22:0612,987+13
30 Oct 2026, 23:2812,974+6
30 Oct 2026, 00:2812,968+6
29 Oct 2026, 03:4112,962+3
28 Oct 2026, 02:5712,959+5
26 Oct 2026, 23:2812,954-3
26 Oct 2026, 02:0712,957+7
25 Oct 2026, 02:3512,950-2
24 Oct 2026, 03:2112,952+2
22 Oct 2026, 05:3612,950first reading

Engagement

80 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 69 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
43.1%
avg views ÷ 13,167 subscribers
Avg views / post
5,670
33 posts measured
Reaction rate
0.363%
reactions ÷ views · ER floor
Posts in window
33
of 80 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 32 of 33 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 12 November 2026
Posts held80 (15 May 2026 – 12 November 2026)
Views total187,140
Reactions total671
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Nov 2026, 08:45 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
23
Videos
2
Links
73

Lifetime counters from Telegram’s own channel header, read 13 November 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.

Video runtime
17s
Average length
17s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

2,098 reactions across 74 posts, in 10 distinct kinds. The most used accounts for 45.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍96345.9%
❤50324.0%
🤯1647.82%
😱1446.86%
🤔1306.20%
🔥864.10%
👏422.00%
🤩281.33%
🎉271.29%
🥰110.524%

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 77 of the 80 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 2,098 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 80 most recent posts we hold, published 15 May 2026 to 12 November 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

Telegram’s own ‘edited’ marker: 6 of 33 posts held from the last 30 days (18.2%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

12 Nov 2026, 15:28 UTC≈4,420 views19 reactionsread 13 November 2026

Beta Updates Surge Engine Performance • Hysteria 2 and TUIC downloads are faster and use less CPU. Surge now acknowledges received packets in batches. On a 10 GbE test machine, Hysteria 2 went from 2.86 to 3.84 Gbps, with CPU dropping from 137% to 108%. • Hysteria 2 and TUIC uploads no longer send the whole congestion window in one burst, which overran the server and caused packet loss. Several uploads sharing one…

❤19

11 Nov 2026, 15:50 UTC≈5,180 views29 reactionsread 13 November 2026

• Fixed uploads through SSH policies getting corrupted after the session rekeyed, which happens after 1 GB. • Fixed SSH servers dropping the whole session, and every tunnel on it, after Surge closed a channel twice. • Fixed several MASQUE issues with Envoy: • The first packet to each new UDP destination was lost. • UDP to new destinations failed once about 100 were open on one connection. • 1,200-byte UDP repli…

👍16😱9❤4

11 Nov 2026, 15:50 UTC≈5,140 views25 reactionsread 13 November 2026

Beta Updates Surge Engine AI-powered Testing Platform We have built a fully automated, AI-powered testing platform for Surge Engine. The platform continuously evaluates compatibility and performance against the latest official client implementations of all supported proxy protocols, helping ensure that Surge matches or exceeds their performance. Going forward, every change to Surge Engine will be validated throug…

👍14❤6😱4🤔1

11 Nov 2026, 15:49 UTC≈11,500 views117 reactionsread 13 November 2026

VLESS and REALITY Support in Surge Beta The latest Surge beta adds support for the VLESS protocol, including connections secured with REALITY. Configuration is currently available through text-based profiles only; see https://manual.nssurge.com/policies/vless.html for syntax and supported options. Why We're Adding VLESS and REALITY In an era where AI has made writing code dramatically simpler, implementing a featu…

😱62👍25🤩8❤7🤔6🤯5🎉4

11 Nov 2026, 15:06 UTC≈4,430 views2 reactionsread 13 November 2026

• Profile errors now explain why a line is invalid, not only where it is. • New log-file-size-limit option in [General] sets the maximum log file size in MB. You can also set it in General → Log. When it is not set, the old limits still apply: 200 MB on Mac and 50 MB on iOS. Fixes • Fixed an issue where an external policy used directly as the underlying-proxy of another policy did not start its process automatically…

❤2

11 Nov 2026, 15:06 UTC≈3,040 views0 reactionsread 13 November 2026

Improvements • Snell v6: UDP data is now sent right after the tunnel command, without waiting a round trip for the server's response. QUIC over Snell v6 connects noticeably faster. This requires a v6 server. • Ponte: a device no longer stays stuck in "LAN-only mode" when its record was captured while its remote channels were restarting. Surge refreshes the device list before giving up, and the error message now expla…

11 Nov 2026, 15:06 UTC≈2,150 viewsread 13 November 2026

MITM with Your Own Certificates • New [MITM] server-certificates = <hostname>:<keystore item>, ... decrypts the listed hosts with your own certificate, such as a publicly trusted one, instead of one signed by Surge's CA. Use it to inspect apps that pin their certificate or reject user-installed CAs. • Hosts in this list work even without a CA configured. • The first matching entry wins. If its PKCS #12 item cannot be…

11 Nov 2026, 15:06 UTC≈2,220 views1 reactionsread 13 November 2026

MCP Server • The HTTP API can now serve a Model Context Protocol endpoint at /v1/mcp, so AI agents such as Claude Code can inspect and control Surge. Enable it with the MCP Server switch in the HTTP API settings, or with http-api-mcp = true. It is off by default. HTTP API • GET /v1/policies of the HTTP API now accepts the include_external=true query parameter. The response then contains an additional external-polici…

❤1

11 Nov 2026, 15:06 UTC≈2,690 views5 reactionsread 13 November 2026

Surge Mac 6.11.0 has now been officially released. SOCKS5 UDP • The built-in SOCKS5 proxy server now supports UDP ASSOCIATE. SOCKS5 clients can send UDP traffic through Surge, and it goes through your rules and policies the same way as TCP. The first datagram of each association is matched against your rules, and later datagrams use the same policy. Avoid in Automatic Groups • You can now mark a policy as avoided. …

❤3👍2

11 Nov 2026, 14:46 UTC≈3,410 views7 reactionsread 13 November 2026

Known Issue: Surge May Stop Unexpectedly on iOS 27.3 Beta 1 On iOS 27.3 beta 1, a problem in the system’s Network Extension framework can cause Surge to stop unexpectedly. The problem is in iOS itself, and we are waiting for Apple to fix it in a future update. In the meantime, the next Surge beta gives you clearer information when this happens. If Surge is stopped, you will receive a notification that states the ex…

❤5🤯1😱1

10 Nov 2026, 14:22 UTC≈3,410 views6 reactionsread 13 November 2026

Beta Updates Surge Engine Surge CLI • surge-cli dump now accepts dns-lookup-times, traffic-stat-hourly and policy-usage and shows readable output for them. Before, these dumps only worked with --raw. Modules • Updating a module, or reinstalling it from the same URL, now downloads its scripts and rule sets again right away. Before, new versions of these resources waited for their update interval. Improvements •…

❤6

9 Nov 2026, 14:41 UTC≈3,510 views5 reactionsread 13 November 2026

Beta Updates Surge Engine External Control • module list now returns details for each module: its type, every #! header field, the declared argument names, the file modification time, and the effective lines in each section after loading with the stored arguments (or the load error). The new module show <name> command also includes the module's text. Available in surge-cli, MCP (list_modules and the new get_module…

😱4👍1

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

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.

Mentions

Named by 18 registered channels — 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.

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.

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.

Shadowrocket News
@ShadowrocketNews · 47,300
Telegram ranks this channel #3 of 60 here — alongside 59 others — read 27 August 2026
折腾啥
@zhetengsha · 54,121
Telegram ranks this channel #3 of 50 here — alongside 49 others — read 26 August 2026
 Apple Nuts
@AppleNuts · 37,701
Telegram ranks this channel #5 of 56 here — alongside 55 others — read 1 September 2026
🍟 整点薯条: 频道
@GetSomeFriesChannel · 20,348
Telegram ranks this channel #6 of 45 here — alongside 44 others — read 29 September 2026
不止QuantumultX
@Quantumultxxxx · 22,065
Telegram ranks this channel #6 of 37 here — alongside 36 others — read 25 September 2026
Loon News
@LoonNews · 48,288
Telegram ranks this channel #6 of 49 here — alongside 48 others — read 27 August 2026
Clash Verge Rev Channel
@clash_verge_re · 86,158
Telegram ranks this channel #7 of 64 here — alongside 63 others — read 19 August 2026
APTV通知频道
@AptvPlayerChannel · 37,338
Telegram ranks this channel #8 of 38 here — alongside 37 others — read 5 September 2026
XP Digital Lab
@rocCHL · 37,277
Telegram ranks this channel #9 of 28 here — alongside 27 others — read 3 September 2026
CMLiussss 技术干货分享
@CMLiussss_channel · 72,074
Telegram ranks this channel #9 of 47 here — alongside 46 others — read 21 August 2026
TestFlightX
@TestFlightX · 43,389
Telegram ranks this channel #11 of 37 here — alongside 36 others — read 28 August 2026
FlClash Channel
@FlClash · 54,591
Telegram ranks this channel #14 of 53 here — alongside 52 others — read 28 August 2026
小果子|iOS越狱交流频道
@guozhiapp · 21,873
Telegram ranks this channel #15 of 25 here — alongside 24 others — read 20 September 2026
Surfboard News
@surfboardnews · 28,395
Telegram ranks this channel #15 of 64 here — alongside 63 others — read 9 September 2026
deb+dylib插件收集
@deb_dylib · 22,226
Telegram ranks this channel #18 of 23 here — alongside 22 others — read 21 September 2026
少数派sspai
@sspai · 39,143
Telegram ranks this channel #18 of 58 here — alongside 57 others — read 31 August 2026
Odyssey+
@odysseyplus · 24,727
Telegram ranks this channel #19 of 29 here — alongside 28 others — read 15 September 2026
懒猫的频道
@lanmaoshare · 20,893
Telegram ranks this channel #22 of 27 here — alongside 26 others — read 3 October 2026
刀刀源 | iOS | 越狱
@ae86_dao · 29,298
Telegram ranks this channel #22 of 25 here — alongside 24 others — read 14 September 2026
Surge & Loon & QX 脚本收集
@NobyDa · 64,555
Telegram ranks this channel #22 of 42 here — alongside 41 others — read 21 August 2026
折腾搞机频道
@tossichannel · 36,146
Telegram ranks this channel #24 of 28 here — alongside 27 others — read 5 September 2026
iOS宝藏
@iosrxwy · 100,301
Telegram ranks this channel #24 of 28 here — alongside 27 others — read 31 August 2026
叮当猫のiOS资源分享频道
@ddm1023 · 50,362
Telegram ranks this channel #24 of 41 here — alongside 40 others — read 26 August 2026
MoviePilot频道
@moviepilot_channel · 19,991
Telegram ranks this channel #26 of 40 here — alongside 39 others — read 30 September 2026

This channel appears in 47 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. 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 13 November 2026 — this entry's latest reading, not the date you are reading this.

“Surge TestFlight Feed” (@SurgeTestFlightFeed), 13,167 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/SurgeTestFlightFeed.

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.