Telegram RegisterThe public register of Telegram
Telegram profile photo for Stash Channel

Channel

Stash Channel

@StashFeed

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

27,153subscribers

+1,087 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-1001540020738
TypeChannel
Username@StashFeed
DescriptionStash 信息官方发布渠道。 Stash 是 Clash 规则在 iOS 平台的最佳选择。 Stash macOS 下载 https://stash.ws Stash AppleStore https://apps.apple.com/app/stash/id1596063349 Stash 用户手册 https://stash.wiki 讨论组 @StashFans
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live18 September 2026
Measurements held35
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/StashFeed

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

26,06627,15326,609.56 August 2026 — 26,066 subscribers6 August 2026 — 26,066 subscribers6 August 2026 — 26,077 subscribers7 August 2026 — 26,118 subscribers8 August 2026 — 26,133 subscribers9 August 2026 — 26,156 subscribers10 August 2026 — 26,183 subscribers11 August 2026 — 26,202 subscribers12 August 2026 — 26,222 subscribers13 August 2026 — 26,273 subscribers14 August 2026 — 26,278 subscribers16 August 2026 — 26,259 subscribers17 August 2026 — 26,283 subscribers18 August 2026 — 26,331 subscribers19 August 2026 — 26,362 subscribers20 August 2026 — 26,395 subscribers21 August 2026 — 26,412 subscribers23 August 2026 — 26,462 subscribers24 August 2026 — 26,436 subscribers25 August 2026 — 26,459 subscribers26 August 2026 — 26,691 subscribers27 August 2026 — 26,753 subscribers28 August 2026 — 26,788 subscribers29 August 2026 — 26,775 subscribers30 August 2026 — 26,794 subscribers31 August 2026 — 26,812 subscribers1 September 2026 — 26,892 subscribers3 September 2026 — 26,916 subscribers4 September 2026 — 26,964 subscribers7 September 2026 — 26,961 subscribers10 September 2026 — 26,985 subscribers12 September 2026 — 26,947 subscribers14 September 2026 — 26,986 subscribers15 September 2026 — 27,108 subscribers18 September 2026 — 27,153 subscribers6 August 202618 September 2026
35 measurements spanning 43 days, net +1,087. 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 25,903–27,316 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 35
Measured (UTC)SubscribersChange
18 Sept 2026, 03:1527,153+45
15 Sept 2026, 23:1727,108+122
14 Sept 2026, 03:1526,986+39
12 Sept 2026, 09:1726,947-38
10 Sept 2026, 07:2026,985+24
7 Sept 2026, 02:1426,961-3
4 Sept 2026, 08:1726,964+48
3 Sept 2026, 00:0526,916+24
1 Sept 2026, 19:0526,892+80
31 Aug 2026, 19:0526,812+18
30 Aug 2026, 22:3526,794+19
29 Aug 2026, 20:1126,775-13
28 Aug 2026, 23:4426,788+35
27 Aug 2026, 21:5326,753+62
26 Aug 2026, 21:5326,691+232
25 Aug 2026, 20:1126,459+23
24 Aug 2026, 18:4526,436-26
23 Aug 2026, 06:2526,462+50
21 Aug 2026, 15:1526,412+17
20 Aug 2026, 17:0426,395first reading

Engagement

45 posts held, back to 25 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 63 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
21.8%
avg views ÷ 27,153 subscribers
Avg views / post
5,920
20 posts measured
Reaction rate
0.247%
reactions ÷ views · ER floor
Posts in window
20
of 45 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 19 of 20 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 25 September 2026
Posts held45 (25 March 2026 – 25 September 2026)
Views total118,460
Reactions total283
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken26 Sept 2026, 20:30 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
79
Videos
2
Links
121

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

Reaction mix

984 reactions across 44 posts, in 14 distinct kinds. The most used accounts for 44.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤43344.0%
👍23123.5%
💯979.86%
🎉697.01%
🤩434.37%
👏383.86%
😱242.44%
🥰191.93%
🔥161.63%
🍾40.407%
🏆40.407%
🎄30.305%
🆒20.203%
😎10.102%

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

Measured over the 45 most recent posts we hold, published 25 March 2026 to 25 September 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

25 Sept 2026, 06:13 UTC≈2,500 views12 reactionsread 26 September 2026

▎Stash TestFlight / Beta 更新 新功能 • 全局隧道可排除配对设备通信:开启后,Apple Watch 等配对设备可继续与手机通信;不支持此选项的系统不会显示该设置。 修复 • 兼容更多节点传输配置:现在可以正常加载使用 `raw` 传输方式的 VLESS、VMess 和 Trojan 节点。 • 修复特殊转义正则导致的配置加载失败:包含 `\c` 或 `\e` 转义的正则表达式配置现在可以正常加载。 Platform: iOS Build: 1313

👍7🎉4💯1

23 Sept 2026, 04:22 UTC≈3,520 views12 reactionsread 26 September 2026

▎Stash TestFlight / Beta 更新 新功能 • 支持更多 REALITY 节点组合:现在可使用 VLESS 的 REALITY+h2、REALITY+WebSocket 和 HTTP 传输组合,也可使用 VMess、Trojan 的 REALITY+WebSocket 节点。 • VLESS Vision 支持 XHTTP 传输:使用 VLESS Encryption 时,可将 XTLS Vision 与 XHTTP 传输方式配合使用。 • 可按网络接口使用 DNS:指定网络接口的 DNS 服务器会随网络变化自动更新。 • Mieru 支持会话复用:支持多个会话共享连接和无需等待的握手模式,减少连接建立等待。 修复 • 兼容新版 REALITY 节点:现在可以连接要求 X25519MLKEM768 握手的 Xray REALITY 节点。 • 修复 MitM 证书域名不匹配:通过 MitM 访问部分网站时…

👍6❤2💯2🔥2

23 Sept 2026, 04:18 UTC≈2,830 views7 reactionsread 26 September 2026

▎Stash TestFlight / Beta 更新 新功能 • 控制端口冲突时自动切换:默认控制端口被占用时,Stash 会改用其他可用端口,让相关连接继续正常工作。 • 支持更多 DNS 配置写法:现在支持更多 DNS 响应类型,以及用逗号分隔多个 DNS 策略匹配项。 • VLESS HTTP 传输支持 REALITY:VLESS 使用 HTTP 传输时,现在可以配置 REALITY 并正常连接。 • VLESS Vision 支持搭配 XHTTP:使用 VLESS Encryption 时,XTLS Vision 现在可以与 XHTTP 传输方式配合使用。 • Mieru 支持会话复用:支持会话复用和无需等待的握手模式,减少连接建立等待,并让多个会话共享连接。 修复 • 支持更多 REALITY 节点组合:现在可正常加载并连接 VLESS 的 REALITY+h2、REALITY+WebSocket,以及 VMes…

👍4🎉2🤩1

23 Sept 2026, 04:15 UTC≈2,610 views7 reactionsread 26 September 2026

▎Stash TestFlight / Beta 更新 新功能 • 支持 Snell v6:现在可以添加和使用 Snell v6 代理,并配置对应模式和 userkey。 • 支持配置本地成功 DNS 响应:现在可以配置本地成功 DNS 响应来处理 DNS 查询。 • 支持发现局域网中的 Stash 设备:开启后,Stash 可在局域网发布控制服务并发现其他设备,便于建立远程控制连接。 • 支持 Mieru 流量特征:现在可以使用 Mieru TCP 流量特征建立连接,并在代理编辑器中配置该选项。 • 支持匹配缺少地理或 ASN 信息的地址:使用 GeoIP 或 IP-ASN 规则时,可以匹配缺少相应信息的地址。 • 控制端口冲突时自动切换:默认控制端口被占用时,应用会改用其他可用端口,让相关连接继续工作。 • 支持更多 DNS 配置写法:现在支持更多 DNS 响应类型,也支持用逗号分隔多个 DNS 策略匹配项。 • VLES…

❤3💯2🥰2

21 Sept 2026, 11:12 UTC≈3,480 views2 reactionsread 26 September 2026

▎Stash TestFlight / Beta 更新 新功能 • 支持配置成功 DNS 响应:现在可以配置 rcode://success 响应来处理 DNS 查询。 • 支持发现局域网中的 Stash 设备:开启后可在局域网中发现其他 Stash 设备并建立远程控制连接,macOS 还可从“附近设备”中直接选择设备。 • 支持 Mieru 流量特征:现在可以在代理编辑器中配置 Mieru 流量特征并建立连接。 • 规则可以匹配未知地址:使用 GeoIP 或 IP-ASN 规则时,也可以匹配缺少相应地理或 ASN 信息的地址。 • 支持更多 DNS 配置写法:现在支持更多 DNS 响应类型,也支持用逗号分隔多个 DNS 策略匹配项。 • 丢包和延迟变化时传输更稳定:网络丢包、延迟变化或连接暂时受阻后,传输可以更及时、准确地恢复,减少速度波动。 优化 • 下载占用的网络资源更少:闲置或已完成的下载不再持续占用过多资源,弱网环…

❤2

21 Sept 2026, 05:32 UTC≈3,470 views4 reactionsread 26 September 2026

▎Stash TestFlight / Beta 更新 新功能 • 支持 Mieru 流量特征:现在可以使用 Mieru 流量特征建立连接,并可在代理编辑器中进行配置。 • 支持匹配未知地址:使用 GeoIP 或 IP-ASN 规则时,现在可以匹配缺少对应地理或 ASN 信息的地址。 • 弱网下更快恢复传输:在高延迟或丢包网络中,传输可以更快恢复,减少下载停顿和长时间传输空档。 • 丢包和高延迟时恢复更稳定:网络延迟变化、连接暂时受阻或连续丢包后,传输可以更准确、更及时地恢复,减少连接停顿和速度波动。 优化 • 网络连接速度更智能:Stash 会根据当前网络状况自动选择更合适的传输方式,帮助提升连接速度和稳定性。 修复 • 兼容旧版 DHCP DNS 配置:现在可以正确识别使用旧版 DHCP DNS 名称的网络配置,提升网络连接兼容性。 • 自动调节更适应网络变化:网络延迟或连接速度发生变化后,自动调节可以更准确地更新判断…

❤4

20 Sept 2026, 16:18 UTC≈3,850 viewsread 26 September 2026

▎Stash TestFlight / Beta 更新 新功能 • 支持配置本地成功 DNS 响应:让 DNS 查询处理更加灵活。 • 支持发现局域网中的 Stash 设备:开启后,Stash 可在局域网中发布控制服务并发现其他 Stash 设备,远程控制器还能从“附近的设备”列表中直接选择设备,无需手动输入地址。 • 大日志文件支持分页查看:打开超大的日志文件更加稳定,并可在更早、更新和最新日志之间快速切换。 优化 • 资源下载错误更易查看和复制:下载失败时可以展开查看完整错误信息,并一键复制内容。 修复 • 发送过大的 UDP 数据包会立即失败:避免请求长时间等待或无法发出。 • 修复 Tailscale 登录问题:减少同时发起登录操作导致的失败或状态异常。 • 恢复脚本和小组件的数据保存:重启或再次运行后,设置与状态也能正常保留。 Platform: iOS Build: 1307

18 Sept 2026, 22:45 UTC≈4,380 views6 reactionsread 26 September 2026

▎Stash TestFlight / Beta 更新 新功能 • Tailscale 管理功能更完善:macOS 现在可以打开 Tailscale 管理页面,查看并更新连接状态、登录、选择出口节点、管理连接,还能一键复制控制服务器、设备名、IP 地址、授权链接和错误信息。 修复 • 发送过大的 UDP 数据包会立即失败:避免请求长时间等待或无法发出。 Platform: macOS Build: 545

❤6

18 Sept 2026, 03:21 UTC≈4,630 views14 reactionsread 26 September 2026

▎Stash macOS Beta 更新 新功能 • 配置编辑器支持更多内容:现在可以编辑命名提供方、序列配置项、内联规则、策略组、单条规则、本地代理、HTTP 重写和覆写文件等内容。 • IPv6 路由支持自动适配:IPv6 路由现在支持 Auto、On 和 Off 三种模式,选择 Auto 时会根据当前网络能力自动决定是否启用。 • 设置引导和权限管理更加清晰:设置引导会显示可用地址并支持复制,权限页面可以检测和请求所需权限,首次设置也会正确引导授权网络扩展。 • 远程控制面板更加完整:连接远程 Stash 时可以查看代理、日志、提供方和策略组,连接列表还会显示局域网设备的名称、类型和图标。 • 可在设置中安装命令行工具:现在可以在“设置”>“通用”中安装或更新 Stash 命令行工具,并将其设置为系统中的 stash 命令。 • 支持切换回本地配置文件夹:使用 iCloud 存储配置时,可以直接切回上次使用的本地文件夹。…

❤6🎉4👍3🤩1

15 Sept 2026, 23:25 UTC≈5,400 views20 reactionsread 26 September 2026
Photo

📌 Stash 3.6:关于两处 CA 证书设置的说明 更新到 Stash 3.6 后,可视化编辑器既可以编辑配置文件,也可以编辑覆写。因此,你可能会在不同入口看到相似的 CA 证书页面,但它们编辑的是不同位置的数据。 许多用户使用的是订阅配置。订阅内容不适合直接修改:它可能是只读的,也可能在定期更新后覆盖本地改动。因此,Stash 提供了由应用管理的 「Stash MitM」覆写,用来保存 CA 证书及相关 MitM 设置。 将证书保存在「Stash MitM」覆写中有几个好处: • 不会被订阅更新覆盖; • 切换配置文件时仍可继续使用; • 可以通过 iCloud 在自己的设备之间同步; • 无需给每一份配置重复添加证书。 而从某个配置文件进入「可视化编辑 → CA 证书」时,页面显示的是该配置文件自身是否保存了证书。因此,即使你已经通过首页 MitM 入口配置好了证书,这里仍可能显示“未配置”。这不代表证书…

💯10❤6👍2🥰1😱1

15 Sept 2026, 04:05 UTC≈14,700 views92 reactionsread 26 September 2026
Photo

Hello, Stash for Windows 最近我们正积极地把 Stash 拓展到全平台 🎉 继 Stash for Android 开始公测后,我们也将开始公测 Stash for Windows 。 当前版本已经实现 Stash 的大部分功能,并且采用 Windows 原生开发。 💡 作为早期版本,功能和稳定性与 iOS 版仍有差距,我们会保持快速的更新节奏,把功能逐步补齐。如遇到任何问题,请通过 Telegram 向我们反馈,你的反馈会帮助我们把 Android & Windows 版打磨得更稳定。感谢你的支持! ▎Stash for Windows 下载 https://releases.stash.ws/windows/Stash-latest-setup.exe

👍64🎉12💯6❤4🤩3🥰3

13 Sept 2026, 15:23 UTC≈5,850 views6 reactionsread 26 September 2026

▎Stash TestFlight / Beta 更新 新功能 • 配置编辑器可在可视化和 YAML 之间切换:编辑配置时,现在可以直接在两种编辑方式之间切换,无需离开当前页面;调整顺序后,列表项也会保持正确对应。 优化 • 兼容更多 TLS 证书:连接到使用不同证书体系的网站和服务器时更加稳定,同时减少重复验证等待。 修复 • Hysteria 连接不再意外中断:修复部分服务器认证成功后连接立即断开的问题。 Platform: iOS Build: 1300

👍4❤1👏1

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

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 18 September 2026 — this entry's latest reading, not the date you are reading this.

“Stash Channel” (@StashFeed), 27,153 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/StashFeed.

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.