Telegram RegisterThe public register of Telegram
Telegram profile photo for Shadowrocket News

Channel

Shadowrocket News

@ShadowrocketNews

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry

47,272subscribers

+1,131 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001148820620
TypeChannel
Username@ShadowrocketNews
DescriptionShadowrocket 只有iOS/iPadOS/tvOS 版本. 讨论群组: @ShadowrocketApp App Store下载链接: https://apps.apple.com/us/app/shadowrocket/id932747118?l=zh-cn
CreatedBetween 1 February 2016 and 31 October 2019 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live9 November 2026
Measurements held66
Confirmed unchanged1 time, most recently 9 November 2026
On Telegramt.me/ShadowrocketNews

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 21 August 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.

Growth

46,13847,27246,7056 August 20269 November 2026
66 measurements spanning 96 days, net +1,131. 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 45,968–47,442 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 66
Measured (UTC)SubscribersChange
9 Nov 2026, 16:1147,272+11
8 Nov 2026, 10:2047,261+5
7 Nov 2026, 05:2747,256+6
6 Nov 2026, 05:2047,250+2
5 Nov 2026, 02:2847,248+12
4 Nov 2026, 02:2147,236-9
3 Nov 2026, 00:4147,245+9
2 Nov 2026, 01:1947,236+20
1 Nov 2026, 01:5747,216+8
31 Oct 2026, 01:0747,208+32
30 Oct 2026, 00:5647,176+42
29 Oct 2026, 00:1847,134+7
28 Oct 2026, 01:2847,127+20
27 Oct 2026, 03:5647,107+11
26 Oct 2026, 03:4747,096+15
25 Oct 2026, 04:2647,081+2
24 Oct 2026, 00:4947,079+6
22 Oct 2026, 22:5547,073+15
21 Oct 2026, 23:4547,058+4
20 Oct 2026, 18:5147,054first reading

Engagement

91 posts held, back to 10 July 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 192 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
13.6%
avg views ÷ 47,272 subscribers
Avg views / post
6,410
12 posts measured
Reaction rate
0.155%
reactions ÷ views · ER floor
Posts in window
12
of 91 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 8 November 2026
Posts held91 (10 July 2026 – 8 November 2026)
Views total76,920
Reactions total119
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Nov 2026, 00:48 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
≈131
Links
≈1,370

Lifetime counters from Telegram’s own channel header, read 11 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Reaction mix

566 reactions across 87 posts, in 6 distinct kinds. The most used accounts for 43.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤24843.8%
🔥15226.9%
👍14826.1%
👏71.24%
🎉61.06%
🥰50.883%

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

Measured over the 91 most recent posts we hold, published 10 July 2026 to 8 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: 0 of 12 posts held from the last 30 days (0%) 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).

8 Nov 2026, 12:05 UTC≈3,370 views3 reactionsread 11 November 2026

Shadowrocket 测试版更新 版本 2.2.94 (3501) 测试内容: · fix(keyboard): keep focused fields visible as the keyboard frame changes · fix(ui): restore the bottom scroll edge blur on iOS 27 · perf(vless): reuse framed input buffers for batched stream reads 群组 @ShadowrocketApp 频道 @ShadowrocketNews 邮箱 [email protected]

🔥3

6 Nov 2026, 03:54 UTC≈5,090 views10 reactionsread 11 November 2026

Shadowrocket 测试版更新 版本 2.2.94 (3498) 测试内容: · fix(settings): persist and normalize test URL edits · fix(lwip): enlarge receive windows for remote tcp connections · fix(wireguard): preserve active sessions during handshake recovery 群组 @ShadowrocketApp 频道 @ShadowrocketNews 邮箱 [email protected]

❤7👍2🔥1

3 Nov 2026, 10:04 UTC≈6,560 views6 reactionsread 11 November 2026

Shadowrocket 测试版更新 版本 2.2.94 (3497) 测试内容: · fix(macos): restore native rendering for menu bar speed text · fix(xhttp): resume shared HTTP/3 write queue after completion · fix(xhttp): initialize HTTP/3 request header flags · perf(tailscale): reduce DERP probe resource usage · fix(tailscale): restore connections after network changes · fix(sudoku): honor HTTP mask TLS for WebSocket connections 群组 @ShadowrocketApp 频道…

🔥4❤1👏1

1 Nov 2026, 12:33 UTC≈6,460 views7 reactionsread 11 November 2026

Shadowrocket 测试版更新 版本 2.2.94 (3494) 测试内容: · fix(anytls): add SYNACK timeout protection for reused v2 sessions 群组 @ShadowrocketApp 频道 @ShadowrocketNews 邮箱 [email protected]

👍4🔥2❤1

31 Oct 2026, 11:26 UTC≈6,370 views7 reactionsread 11 November 2026

Shadowrocket 测试版更新 版本 2.2.94 (3493) 测试内容: · fix(macos): respect network service order for proxy sharing · test(tls): cover automatic TLS connection timeouts 群组 @ShadowrocketApp 频道 @ShadowrocketNews 邮箱 [email protected]

❤3👍3🔥1

30 Oct 2026, 02:02 UTC≈6,620 views6 reactionsread 11 November 2026

Shadowrocket 测试版更新 版本 2.2.94 (3492) 测试内容: · feat(tls): add global fingerprint override toggle · fix(tailscale): correct MagicDNS node addresses and IPv6 connection setup 群组 @ShadowrocketApp 频道 @ShadowrocketNews 邮箱 [email protected]

❤3🔥2🎉1

29 Oct 2026, 16:19 UTC≈6,160 views3 reactionsread 11 November 2026

Shadowrocket 测试版更新 版本 2.2.94 (3490) 测试内容: · feat(tls): add edge profile alias mapped to chrome140 群组 @ShadowrocketApp 频道 @ShadowrocketNews 邮箱 [email protected]

❤2🔥1

29 Oct 2026, 03:45 UTC≈8,020 views59 reactionsread 11 November 2026
Photo

Shadowrocket 正式版更新 版本 2.2.93 更新内容: * 特性(macOS): 新增“启动至菜单栏”选项,并改善内嵌与独立菜单栏模式下的主窗口恢复行为 * 修复(macOS): 修复独立菜单栏模式下服务器列表的加载与更新,避免关闭窗口后在平铺窗口管理器中留下空白位置 * 修复(tunnel): 支持在强制路由模式下排除局域网,说明路由选项的优先级,并避免在 VPN 配置文件安装前更新偏好设置 * 修复(tailscale): 按端点隔离 UDP 发送失败并重试不可达目的地,避免将正常对端一并切换至 DERP * 修复(iCloud): 修复清除本地服务器后的同步恢复问题,防止非预期删除传播,并在同步时补齐缺失的服务器数据 * 修复(network): 防止匹配 MiTM 与 HTTP 全局通配符主机规则时崩溃,并在 HTTP 解析器关闭流后停止 TCP 处理 * 修复(ui): 降低启用查找功能时离开文本页…

👍50❤5🔥4

29 Oct 2026, 00:11 UTC≈5,210 views2 reactionsread 11 November 2026

Shadowrocket 测试版更新 版本 2.2.93 (3488) 测试内容: · fix(transport): preserve payloads received with handshake responses 群组 @ShadowrocketApp 频道 @ShadowrocketNews 邮箱 [email protected]

❤1🔥1

27 Oct 2026, 09:29 UTC≈6,030 views6 reactionsread 11 November 2026

Shadowrocket 测试版更新 版本 2.2.93 (3487) 测试内容: · fix(tunnel): resolve on-demand early startup issue 群组 @ShadowrocketApp 频道 @ShadowrocketNews 邮箱 [email protected]

❤5🔥1

26 Oct 2026, 01:29 UTC≈7,630 views3 reactionsread 11 November 2026

Shadowrocket 测试版更新 版本 2.2.93 (3486) 测试内容: · fix(scripting): preserve range semantics when rewriting 206 responses 群组 @ShadowrocketApp 频道 @ShadowrocketNews 邮箱 [email protected]

❤2🔥1

22 Oct 2026, 01:50 UTC≈9,400 views7 reactionsread 11 November 2026

Shadowrocket 测试版更新 版本 2.2.93 (3485) 测试内容: · fix(config): unify certificate pinning alias handling · fix(wireguard): preserve persistent keepalive and traffic during rekey 群组 @ShadowrocketApp 频道 @ShadowrocketNews 邮箱 [email protected]

🔥5❤2

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

Posts edited after publishing

@ShadowrocketNews edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
13 August 2026
Most recent edit
28 August 2026

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.

Mentions

Named by 11 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.

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.

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

Loon News
@LoonNews · 48,270
#1
 Apple Nuts
@AppleNuts · 37,705
#2
Surge TestFlight Feed
@SurgeTestFlightFeed · 13,052
#3
Surge & Loon & QX 脚本收集
@NobyDa · 64,479
#4
折腾啥
@zhetengsha · 53,830
#5
Cool Scripts
@cool_scripts · 16,359
#6
前女友们用过的机场—始于机场,不止机场
@gebaopiCloud · 101,582
#7
Surge Channel
@SurgeChannel · 4,705
#8
V2Fly - Notification and Updates, V2Ray the second new
@v2fly · 6,290
#9
叮当猫のiOS资源分享频道
@ddm1023 · 50,298
#10
少数派sspai
@sspai · 39,123
#11
Hell Cell 功能教学
@HellCellZC123 · 10,894
#12
蓝点网订阅频道
@landiansub · 47,142
#13
APTV通知频道
@AptvPlayerChannel · 37,270
#14
COALCLOUD(NEW)
@coalcloud · 5,978
#15
SaltyFish.IO
@SaltyFishIO · 3,929
#16
层叠 - The Cascading
@outvivid · 9,324
#17
AKILE NOTICE
@akile_notice · 19,019
#18
广告必须死Ⅱ
@GitCube · 11,483
#19
AppPie
@AppPie · 3,529
#20
整点猫咪Channel
@GetMoeCats · 4,541
#21
Appinn Feed|小众软件
@appinnfeed · 34,958
#22
Egern 频道
@egern_news · 7,668
#23
Nexitally Official Channel
@Nexitally_Official · 21,086
#24
CubeCloud News
@CubeCloudNews · 1,169
#25
每日沙雕墙
@woshadiao · 114,495
#26
XP Digital Lab
@rocCHL · 37,274
#27
不止QuantumultX
@Quantumultxxxx · 21,980
#28
iOS优质应用
@ioskk · 50,613
#29
LANG=zh_CN tail -f /var/log/DMIT.log
@DMIT_INC_CN · 11,122
#30
在花🎗️科技圈
@zaihuapd · 289,745
#31
Project X Channel
@projectXtls · 30,507
#32
风向旗参考快讯
@xhqcankao · 168,108
#33
Yummy 😋
@GodlyNews1 · 71,143
#34
竹新社
@tnews365 · 167,192
#35
Newlearnerの自留地
@NewlearnerChannel · 68,274
#36
VPS信号旗播报
@vps_xhq · 50,835
#37
iBeta 尝鲜派|公告栏
@ibeta_channel · 13,618
#38
广告必须死
@Aa28413761 · 26,843
#39
Surfboard News
@surfboardnews · 28,395
#40
APPDO 数字生活指南
@AppDoDo · 40,978
#41
LoopDNS资讯播报
@DNSPODT · 73,241
#42
Solidot
@solidot · 48,812
#43
Z-Turns
@Z_Turns · 5,669
#44
机场稽查局
@VPN_Police · 8,337
#45
每日消费电子观察
@CE_Observe · 77,552
#46
M-Team
@M_Team · 22,274
#47
2019-nCoV疫情实时播报🅥
@nCoV2019 · 32,452
#48
Github_2dust
@github_2dust · 92,921
#49
LetITFly News
@LetITFlyW · 9,732
#50
学习强国公告
@UOVZNEWS · 5,042
#51
荔枝木
@lychee_wood · 17,830
#52
你有一个打折需要了解
@SteamNy · 16,263
#53
即刻精选
@jike_collection · 35,883
#54
时间的切片
@mactalk · 6,869
#55
杰尼龟和他的订阅们
@jngchannel · 17,014
#56
APPDO的互联网记忆
@appdopic · 16,938
#57
Faker的个人频道
@wtfbugtoday · 3,176
#58
Yet Another Public Notification Channel
@yapnc · 7,612
#59
tail -f /var/log/DMIT.log
@DMIT_INC · 6,626
#60

Read from Telegram’s recommendation API, most recently 27 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

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.

Github_2dust
@github_2dust · 92,921
Telegram ranks this channel #11 of 71 here — alongside 70 others — read 17 August 2026
Loon News
@LoonNews · 48,270
Telegram ranks this channel #18 of 49 here — alongside 48 others — read 27 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 9 November 2026 — this entry's latest reading, not the date you are reading this.

“Shadowrocket News” (@ShadowrocketNews), 47,272 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/ShadowrocketNews.

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.