Telegram RegisterThe public register of Telegram

Channel

Stash Channel

@StashFeed

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

26,222subscribers

+156 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 31 January 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/StashFeed

Growth

26,06626,22226,1446 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 subscribers6 August 202612 August 2026
9 measurements spanning 6 days, net +156. 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 26,043–26,245 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 14:1426,222+20
11 Aug 2026, 17:1226,202+19
10 Aug 2026, 20:4226,183+27
9 Aug 2026, 21:2226,156+23
8 Aug 2026, 20:5226,133+15
7 Aug 2026, 23:5726,118+41
6 Aug 2026, 23:0326,077+11
6 Aug 2026, 04:1526,066no change
6 Aug 2026, 04:0826,066first reading

Engagement

19 posts held, back to 25 March 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 17 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
24.4%
avg views ÷ 26,222 subscribers
Avg views / post
6,410
7 posts measured
Reaction rate
0.187%
reactions ÷ views · ER floor
Posts in window
7
of 19 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 12 August 2026
Posts held19 (25 March 202612 August 2026)
Views total44,850
Reactions total84
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 22:14 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
71
Videos
2
Links
114

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.

Reaction mix

500 reactions across 18 posts, in 11 distinct kinds. The most used accounts for 48.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
24048.0%
👍9919.8%
💯5511.0%
🎉336.60%
🤩306.00%
😱142.80%
🔥132.60%
🥰102.00%
🍾40.8%
🏆10.2%
👏10.2%

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

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

12 Aug 2026, 12:28 UTC≈1,700 views12 reactionsread 12 August 2026

Stash 3.6 TF Build 1268 已放出 🎉 本次更新: - 新增 VLESS XHTTP 传输支持,可使用 Stream One、Stream Up 和 Packet Up 模式,并可配合 Reality 使用,文档:https://stash.wiki/proxy-protocols/proxy-types#xhttp - 实验性支持 Mieru 代理 - 新增代理专用 DNS 服务器,避免递归查询和 DNS 泄露 - 完善 Hysteria 2 Gecko 混淆、ShadowTLS v3 和 MRS 规则集支持 - 提升 Juicity UDP、系统 DNS 和 GEOSITE DNS 策略的兼容性 已知问题: 1. Provider 中的 dialer-proxy 可能无法被识别 2. Tailscale 可能暂时无法使用交互式登录 如遇到任何问题,请通过 Telegram 或邮件向我们反馈。感谢

👍84

12 Aug 2026, 04:03 UTC≈2,620 views10 reactionsread 12 August 2026

MASQUE 协议配置格式已更新到文档: https://stash.wiki/proxy-protocols/proxy-types#masque 我们将会在今天晚些时候邀请更多用户通过 TestFlight 参与 3.6 版本的测试。 感谢首批用户的热烈反馈 ❤️

6🍾1🎉1👏1🤩1

10 Aug 2026, 16:25 UTC≈3,640 views0 reactionsread 12 August 2026

Stash 3.6 Build 1267 已放出。 本次更新: - 新增 MASQUE 代理支持,可通过 HTTP/3 或 HTTP/2 建立 CONNECT-IP 隧道 - 修复 VLESS Reality,以及 WebSocket、HTTP/2、gRPC 和 HTTP 混淆传输支持 - 提升 VMess、Hysteria 2、IPv6 DNS 及订阅配置的兼容性 - 丰富正则表达是语法支持 - 修复策略组测速遇到不可用节点后,其余节点延迟无法更新的问题 - 改进规则集配置错误提示 - 优化权限说明的多语言显示 如遇到任何问题,请通过 Telegram 或邮件向我们反馈。感谢你的支持!

10 Aug 2026, 06:44 UTC≈6,490 views27 reactionsread 12 August 2026

Stash 3.6 已开启小范围 TestFlight 测试,首批邀请正在陆续发出。 这一版本对底层进行了大规模重构,重点改善响应速度、耗电与内存占用。欢迎收到邀请的朋友多多体验;如果遇到异常,请通过 Telegram 或邮件告诉我们,你的反馈会帮助我们把正式版打磨得更稳定。

💯20🎉2😱21🤩1🥰1

16 Jul 2026, 04:23 UTC≈10,800 views13 reactionsread 12 August 2026

▎Stash TestFlight / Beta 更新 优化 • 优化 StashTun 稳定性 Platform: macOS Build: 487

👍85

16 Jul 2026, 04:20 UTC≈10,400 views9 reactionsread 12 August 2026

▎Stash TestFlight / Beta 更新 优化 • 优化 StashTun 稳定性 修复 • 修正翻译 • 修复网络切换时,可能会导致断开的问题 Platform: iOS Build: 1249

8👍1

15 Jul 2026, 02:02 UTC≈9,200 views13 reactionsread 12 August 2026

▎Stash TestFlight / Beta 更新 优化 • 优化 StashTun 上传延迟表现 修复 • 修复部分情况下网络切换可能导致断开的问题 • 修复 benchmark-timeout 不能设置为 -1 的问题 • 修复 iCloud 在后台同步时可能导致闪退的问题 • 修复 StashTun 部分情况下可能导致断开的问题 Platform: iOS Build: 1244

🎉5👍42🥰2

11 Jul 2026, 06:07 UTC≈10,300 views9 reactionsread 12 August 2026

▎Stash TestFlight / Beta 更新 修复 • 修复 iCloud 在后台同步时可能导致闪退的问题 Platform: macOS Build: 483

5👍2🥰2

2 Jul 2026, 05:39 UTC≈17,200 views52 reactionsread 12 August 2026
Photo

不小心忘了新的 TestFlight 版本号需要等待苹果的审核,所以暂时还看不到更新。 先给大家看看新版的 tvOS 界面。等审核通过即可更新测试。

35🤩8💯5🥰2🍾1🔥1

2 Jul 2026, 05:20 UTC≈13,500 views17 reactionsread 12 August 2026

▎Stash TestFlight / Beta 更新 新功能 • 全新重构的 StashTun • 优化 Tun 在网络不可用时表现 • 新增 Hysteria2 salamander 混淆模式 • 引用 Provider 可以设置请求的 headers • DNS Nameserver Policy 支持 GEOSITE 匹配,支持设置多个 Nameserver 并发访问 • 支持 TrustTunnel 协议 • Hysteria2 混淆方式新增 gecko 支持 优化 • 优化 tvOS 的页面 • 优化快捷组件开关的状态显示 • 重新设计 tvOS 首页 • 优化 tvOS 代理选择 • 优化 QUIC 协议的拥塞控制 • 全面优化本地化翻译 • 优化 StashTun DNS 请求处理 • 优化 StashTun 上传延迟 • 优化闲置 HTTP 代理请求 • 优化 Block QUIC 处理 • 优化网络切换时

🤩85💯2👍1🔥1

2 Jul 2026, 05:13 UTC≈8,180 views5 reactionsread 12 August 2026

▎Stash TestFlight / Beta 更新 优化 • 修复无覆写状态下的按钮跳转问题 • 优化 StashTun 上传延迟 • 优化 classical 规则集索引域名规则的性能 修复 • 修复部分页面翻译异常的问题 • 修复域名匹配大小写不敏感的问题 Platform: iOS Build: 1230

5

27 Jun 2026, 00:07 UTC≈9,490 views14 reactionsread 12 August 2026

▎Stash TestFlight / Beta 更新 优化 • 优化 StashTun DNS 请求处理 修复 • 修复导航栏多语言异常 • 修复 StashTun 上传可能出现缓慢的问题 Platform: iOS Build: 1219

8👍3🎉2🤩1

Showing the 12 most recent of 19 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.

Citation-graph rank

Citation-graph rank — 113,343 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.

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 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.

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

“Stash Channel” (@StashFeed), 26,222 subscribers as measured 12 August 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.