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,813subscribers

+1,747 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 live9 November 2026
Measurements held65
Confirmed unchanged1 time, most recently 9 November 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 the other topics.

Growth

26,06627,83326,949.527,8136 August 20269 November 2026
65 measurements spanning 96 days, net +1,747. 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,801–28,098 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 65
Measured (UTC)SubscribersChange
9 Nov 2026, 17:1027,813-20
8 Nov 2026, 10:3627,833+14
7 Nov 2026, 02:1127,819-5
6 Nov 2026, 03:3727,824+3
5 Nov 2026, 05:1627,821+56
4 Nov 2026, 04:3827,765+49
3 Nov 2026, 05:1627,716+28
2 Nov 2026, 04:4127,688+14
1 Nov 2026, 07:3927,674+23
31 Oct 2026, 06:4527,651+37
30 Oct 2026, 07:5727,614-1
29 Oct 2026, 05:0927,615+36
27 Oct 2026, 23:3927,579+22
27 Oct 2026, 00:0927,557-7
26 Oct 2026, 03:3927,564+19
25 Oct 2026, 00:4927,545+10
24 Oct 2026, 00:1527,535+9
23 Oct 2026, 01:1927,526+1
21 Oct 2026, 23:2927,525+30
20 Oct 2026, 21:3527,495first reading

Engagement

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

ERR · 30 days
18.5%
avg views ÷ 27,813 subscribers
Avg views / post
5,140
25 posts measured
Reaction rate
0.177%
reactions ÷ views · ER floor
Posts in window
25
of 85 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 7 November 2026
Posts held85 (25 March 2026 – 7 November 2026)
Views total128,430
Reactions total227
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Nov 2026, 02:52 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
83
Videos
2
Links
121

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. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

1,332 reactions across 84 posts, in 15 distinct kinds. The most used accounts for 38.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤51038.3%
👍29422.1%
💯18113.6%
🎉1138.48%
🤩644.80%
👏443.30%
🥰392.93%
🔥332.48%
😱322.40%
🏆70.526%
🆒60.45%
🍾40.3%
🎄30.225%
😍10.075%
😎10.075%

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

Measured over the 85 most recent posts we hold, published 25 March 2026 to 7 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: 1 of 25 posts held from the last 30 days (4.00%) 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).

7 Nov 2026, 19:34 UTC≈2,740 views6 reactionsread 11 November 2026

▎Stash TestFlight / Beta 更新 新功能 • Tailscale 连接支持对等中继:Tailscale 会优先使用可用的直连,无法直连时通过对等中继连接,直连恢复后自动切回,减少 DERP 使用。 • Tailscale 与 DNS 设置更完整:新增“对端 UDP 直连”设置,默认关闭;开启后,对端直连和中继 UDP 使用本机网络,控制服务器与 DERP 仍通过代理链,本机公网 IP 会对控制服务器和 Tailscale 网络内设备可见,DNS 页面也可设置代理服务器 DNS 策略。 • 新增 REJECT-NO-DROP 策略 • Tailscale 连接路径显示更清晰:连接信息会区分对等中继和 DERP,并显示对应的中继地址或区域。 优化 • 高负载下 UDP 传输更流畅 修复 • MitM 主机规则匹配更准确 • 脚本处理更可靠 • MTProto 切换后可正常恢复 • GLOBAL 默认使用 …

❤5👍1

29 Oct 2026, 04:13 UTC≈35,700 views40 reactionsread 11 November 2026
Photo

Hello StashLink Terminal,你的 Mac,随手可及 在外面想看一眼 Agent 跑到哪了、重启个进程、翻一下日志,现在打开 Stash 就能做到。 连接经由 StashLink,在你的设备之间直接完成。无需开启远程登录,无需暴露端口,无需公网 IP。设备之间使用端到端加密直连传输和私有 iCloud 交换信息,密钥只在你的设备上,StashLink 会自动选择合适的直连方式,包括穿越 NAT。StashLink Terminal 的每一次请求都会使用保存在钥匙串的私钥签名,Stash Mac 只有在验签通过后才会开 shell。 你还可以为每个会话命名标题,终端会话内容保留在 Mac 上,锁屏、断网等情况均不影响。 本次更新需同时升级 Stash for iOS(Build 1358) 与 Stash for Mac(Build 577) ,并且需要在 Mac 的 Stash > StashLink…

💯25❤6🆒4🤩3🏆1👍1

29 Oct 2026, 00:03 UTC≈8,860 views49 reactionsread 11 November 2026
Photo

在 Stash for iOS 最新的测试版中,我们深度调优了 Stash 内核的性能,经优化后的 Stash 隧道性能更好、更省电,在 iPhone Duo 上测试内核处理速度高达 20 Gbps。 ⚡️

💯30😱8👍4🔥4🎉1🏆1👏1

27 Oct 2026, 04:16 UTC≈4,550 views7 reactionsread 11 November 2026

▎Stash TestFlight / Beta 更新 新功能 • 脚本支持 gzip 和 zlib 解压 • 脚本支持 GeoIP 查询 • VLESS 支持 StashLink 中继:VLESS 代理现在可以承载 StashLink 中继连接。 优化 • 提升高流量和多连接下载表现 • 提升虚拟网卡传输效率 • 提升 UDP 传输效率 • 兼容仅支持 HTTP/1.1 的 DoH 服务 修复 • 修复登录后增强模式恢复失败 • 修复状态菜单中的表情图标裁切 Platform: macOS Build: 576

❤2💯2🔥2🎉1

27 Oct 2026, 04:09 UTC≈4,280 views5 reactionsread 11 November 2026

▎Stash TestFlight / Beta 更新 新功能 • 脚本支持解压 gzip 和 zlib 数据 • 脚本新增 GeoIP 查询 优化 • 提升网络传输速度与稳定性 • DoH 兼容仅支持 HTTP/1.1 的服务器 Platform: tvOS Build: 1357

👍2🥰2❤1

27 Oct 2026, 04:05 UTC≈4,040 views6 reactionsread 11 November 2026

▎Stash TestFlight / Beta 更新 新功能 • 脚本支持解压 gzip 和 zlib 数据 • 脚本新增 GeoIP 查询 优化 • 提升网络传输速度与稳定性 • 减少连接空闲时的资源占用 • 大型规则集加载更快 • 改善 UDP 连接与 DNS 响应 • DoH 兼容仅支持 HTTP/1.1 的服务器 • 覆写配置错误提示更清楚 Platform: iOS Build: 1357

🤩2🥰2👍1💯1

21 Oct 2026, 01:20 UTC≈5,200 views5 reactionsread 11 November 2026

▎Stash TestFlight / Beta 更新 新功能 • 新增 StashLink 设备在线检测:现在可以检测 StashLink 设备是否在线,并查看往返延迟。 • 查看 StashLink 设备详情:详情页会显示设备名称、设备 ID 和型号,方便识别已连接的设备。 优化 • 让 JSON 改写错误提示更准确 • 加快隧道内的域名解析:WireGuard 和 MASQUE 隧道会缓存解析结果,减少重复查询的等待。 • 可视化规则编辑支持 MTPROTO:编辑 PROTOCOL 规则时,可以选择 MTPROTO 作为匹配内容。 • 在 StashLink 中显示设备域名:设备页面会显示 .stash 域名,也可以通过域名搜索设备。 修复 • 修复 YAML 编辑内容丢失与卡顿:编辑 YAML 时,内容不再被错误修改或丢失;复杂内容也不再造成持续处理或崩溃。 • 修复部分 TLS 连接卡住:使用 VLESS Vis…

👍2💯1🔥1🥰1

21 Oct 2026, 01:15 UTC≈4,240 views6 reactionsread 11 November 2026

▎Stash TestFlight / Beta 更新 新功能 • 所有用户均可使用 Graphite 主题:现在可在“设置 › 外观”中选择默认或 Graphite 主题。 优化 • 可视化规则编辑支持 MTPROTO:编辑 PROTOCOL 规则时,现在可以选择 MTPROTO 作为匹配内容。 • 编辑菜单图标适配主题:配置编辑菜单中的图标会随主题调整外观,在 Graphite 等主题下显示彩色图案和浅色背景。 • Graphite 主题界面显示更清晰:图标、文字、状态和卡片的颜色对比更加清楚,深色模式下的页面层次也更易辨认。 • Graphite 主题适配更多界面元素:标签栏、请求信息、搜索提示、通知图标和开关等元素会更协调地跟随所选主题显示。 修复 • 代理信息检测准确使用所选节点:检测会通过所选的远程代理集节点运行;如果指定节点不存在,检测会报错而不会改用其他代理。 • 修复 Snell 的 IPv4 UDP 响…

❤3🎉1👍1🤩1

21 Oct 2026, 01:12 UTC≈3,650 views3 reactionsread 11 November 2026

▎Stash TestFlight / Beta 更新 优化 • 提升隧道内域名解析效率:WireGuard 和 MASQUE 隧道会缓存解析结果,减少重复查询的等待。 修复 • 重启后保留缓存数据 • 修复 VLESS Vision 部分连接卡住 • 无效 JSON 路径不再阻止隧道启动 • 正文改写支持更多响应 • 脚本可读取完整响应头 • 修复 Snell 的 IPv4 UDP 响应 • 提升局域网服务发现可靠性 Platform: tvOS Build: 1353

🎉2👍1

20 Oct 2026, 03:41 UTC≈3,630 views11 reactionsread 11 November 2026

▎Stash TestFlight / Beta 更新 新功能 • 通过 Tailscale DNS 解析目标域名:使用 Tailscale 时,域名解析会遵循 tailnet 的 DNS 配置;通过出口节点连接时,会优先使用该节点的 DNS 代理,并在不可用时尝试 tailnet 配置的 DNS 服务器。 优化 • 隧道内的域名解析更快、更稳定 修复 • 正文改写支持更多响应 Platform: iOS Build: 1350

🔥5❤3🎉2👏1

20 Oct 2026, 02:42 UTC≈3,790 views6 reactionsread 11 November 2026

▎Stash TestFlight / Beta 更新 优化 • 编辑器中选择和编辑文本更方便:打开后即可输入,长按可选择文本;编辑菜单、跨行选区和光标移动也更准确。 • 大型配置打开更流畅:打开较大的配置时,编辑器不再因加载内容而长时间卡住;加载完成后即可继续编辑。 • 滚动文本时键盘会自动收起:滚动编辑器中的文本时,键盘会自动收起;点按文本即可在相应位置继续编辑。 • 大篇幅搜索结果显示更流畅:在大型文档中搜索大量内容时,编辑器响应更快,搜索高亮也能更快显示。 • 跳转到指定行时滚动更顺畅 Platform: iOS Build: 1349

👍3👏1🤩1😍1

19 Oct 2026, 00:21 UTC≈3,640 views6 reactionsread 11 November 2026

▎Stash TestFlight / Beta 更新 优化 • 改写规则错误提示更清晰:JSON 正文改写规则无效时,提示会更准确地指出问题并说明正确写法。 修复 • 修复 YAML 编辑异常:修复编辑时部分内容被错误修改或丢失的问题,并避免复杂内容导致卡顿或崩溃。 • 提升 SSH 连接安全性与兼容性:SSH 连接可通过证书中的公钥匹配已固定的主机密钥。 • 修复部分 TLS 连接卡住:使用 VLESS Vision 时,部分 TLS 1.3 请求现在可以正常继续。 • 证书状态说明更清晰:证书页面会说明证书未生效的原因及处理方式;没有配置文件时,也可以继续将证书应用到运行配置并完成安装。 Platform: iOS Build: 1345

🥰3❤1🎉1👍1

Showing the 12 most recent of 85 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 9 November 2026 — this entry's latest reading, not the date you are reading this.

“Stash Channel” (@StashFeed), 27,813 subscribers as measured 9 November 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.