Telegram RegisterThe public register of Telegram
Telegram profile photo for Anywhere Official Channel

Channel

Anywhere Official Channel

@anywhere_channel

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

799subscribers

+128 since we began measuring on 15 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003782669391
TypeChannel
Username@anywhere_channel
Created3 March 2026 — measured — dated from the channel’s first post
First recorded15 August 2026
Last confirmed live18 November 2026
Measurements held13
Confirmed unchanged1 time, most recently 18 November 2026
On Telegramt.me/anywhere_channel

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

67179973515 August 2026 — 671 subscribers15 August 2026 — 671 subscribers16 August 2026 — 701 subscribers24 August 2026 — 717 subscribers1 September 2026 — 729 subscribers10 September 2026 — 747 subscribers19 September 2026 — 758 subscribers13 October 2026 — 769 subscribers19 October 2026 — 773 subscribers27 October 2026 — 770 subscribers3 November 2026 — 774 subscribers9 November 2026 — 790 subscribers18 November 2026 — 799 subscribers15 August 202618 November 2026
13 measurements spanning 94 days, net +128. 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 652–818 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Nov 2026, 01:18799+9
9 Nov 2026, 22:55790+16
3 Nov 2026, 13:08774+4
27 Oct 2026, 18:39770-3
19 Oct 2026, 21:30773+4
13 Oct 2026, 15:21769+11
19 Sept 2026, 04:41758+11
10 Sept 2026, 14:21747+18
1 Sept 2026, 13:04729+12
24 Aug 2026, 20:53717+16
16 Aug 2026, 18:27701+30
15 Aug 2026, 15:00671no change
15 Aug 2026, 14:45671first reading

Engagement

14 posts held, back to 3 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 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 14 posts for this entry, the most recent from 15 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

183 reactions across 10 posts, in 9 distinct kinds. The most used accounts for 37.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤6837.2%
👎4926.8%
👍2915.8%
💩1910.4%
🤮73.83%
👏42.19%
🎃31.64%
🔥31.64%
🥰10.546%

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

Measured over the 14 most recent posts we hold, published 3 March 2026 to 15 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

15 Aug 2026, 04:31 UTC≈1,000 views30 reactionsread 15 August 2026

关于友商对 Anywhere 的抹黑 近期 Anywhere 开发团队注意到网络上有关友商对于 Anywhere 的无端节奏,在此特意说明。 大家都知道国行的设备在 App 首次访问网络时,会询问相关网络权限,因此我们在首次使用时有相关的处理逻辑来触发权限弹窗。 Anywhere 选择官方网站来触发此权限请求,友商通过这一随手写的完全无害代码恶意揣测并以此带节奏抹黑。 请大家不要收看相关内容,这会增加视频播放量为图谋不轨者增加收入,如果大家对审计内容感兴趣,已有热心用户发送 issue 到项目仓库,大家可前往查看。与此同时,我们迅速跟进并进一步提升了代码严谨性。 https://github.com/NodePassProject/Anywhere/issues/105 这一事件更体现了 Anywhere 的开源优势,任何的抹黑只会让 Anywhere 变得更强大、更严谨、更安全。友商无论花费多少推广成本,到最后只会…

👍18❤9👏3

31 Jul 2026, 06:24 UTC≈1,130 views12 reactionsread 15 August 2026
Photo

Anywhere 2.0 for iOS 现已正式上线 Anywhere 2.0 聚焦于底层架构更新和线程安全,将 Swift Concurrency 与现代任务管理理念融入 Anywhere 架构,带来更高效的线程利用效率和现代化的生命周期管理。 - 协议测 • 支持 Nowhere 1.5 • 修复 VLESS Encryption XOR random 模式 - 新功能 • 细颗粒度 DNS 设置:允许自定义订阅、IP规则匹配、代理服务器地址、ECH DNS以及非 A/AAAA DNS 回落地址 - 优化 • iCloud 同步:iCloud 同步现使用更新策略实现无缝同步 • 广告屏蔽系统:全新升级的连接屏蔽策略 • UI 系列优化:主页面 UI 优化、订阅详细信息展示优化 • 其他系列优化:移除吞吐量瓶颈、DNS 解析器优化、规则集新增与更新、内存用量优化、延迟测试器优化 Anywhere 带来的所有优…

❤12

28 Jun 2026, 23:21 UTC≈2,290 views5 reactionsread 15 August 2026

加入 Anywhere Voyager TestFlight https://voyager.anywhere-proxy.com/public-beta

❤5

28 Jun 2026, 02:47 UTC≈1,570 views2 reactionsread 15 August 2026

Anywhere TestFlight 方案调整 • 原有 Public TestFlight 公开群组将不再接受新成员 • 原有 Public TestFlight 公开群组成员如果已开通“娱乐版”免费会员,安装正式版后将依然解锁会员功能

❤2

24 Jun 2026, 03:32 UTC≈2,300 views97 reactionsread 15 August 2026
Photo

Anywhere 1.13 for iOS 现已正式上线 - 协议侧 • 支持 TLS ECH with ECHConfigList • 支持 VLESS Encryption 0-rtt • 支持 VLESS XHTTP XMUX • 支持 Hysteria Port Hopping - 新功能 • iCloud 同步 • App 图标/首页/设置页 自定义 - 优化 • UI 系列优化 • MITM 系统系列优化 - Anywhere Voyager Anywhere 虽是开源软件,但打造 Anywhere 的各平台版本、规则集和脚本仍然需要不少社区工作者。为了维持 Anywhere 的长期运转和持续维护,我们在 Anywhere 1.13 版本正式推出 Anywhere Voyager 付费选项以支持 Anywhere 的可持续发展。 加入 Voyager 成员可以使用 Voyager 专属功能。所有关于…

👎49💩19❤12🤮7👍5🔥3👏1🥰1

17 Jun 2026, 04:17 UTC≈1,640 views8 reactionsread 15 August 2026

Everywhere Proxy 1.3 for iOS 现已正式上线 匹配的上游核心版本: • Xray-core v26.3.27 • sing-box v1.13.13 • mihomo v1.19.27 Everywhere Proxy 已进入稳定维护期,请大家使用 App Store 版本。

❤8

10 Jun 2026, 04:09 UTC≈14,200 views12 reactionsread 15 August 2026
Photo

Anywhere 1.12 for iOS 现已正式上线 继 Everywhere Proxy 推出后,我们的 Anywhere Proxy 也依旧在持续演化与精进,而 Anywhere 1.12 则是我们另一次里程碑式的进步。 - 协议侧 • 支持 VLESS h3 • 支持 VLESS XHTTP 上下行分离,并带有美观的编辑器 • 支持 VLESS Encryption 以及 VLESS Encryption + Vision - 优化 • 架构更新与优化,大幅提升稳定性,完善链式代理机制 • UDP 优化,针对性提升极重负载下 UDP 的表现 • 精调设备端性能表现,移除客户端侧瓶颈 - 新功能 • Minimal UI(极简主义)/ Pro UI (专业风格) 风格切换,适应不同使用场景的需求 • Anywhere MITM 现拥有更加完善的 Anywhere API 套件来帮助构建高效的脚本,在保留脚本…

❤12

13 May 2026, 01:40 UTC≈2,770 views10 reactionsread 15 August 2026
Photo

Everywhere Proxy 1.0 for iOS 现已正式上线 极致兼容性: • 兼容所有内核,所有协议,三个愿望,一次满足 • 可自定义核心可读取的文件 极致性能: • 虽然我们支持三个核心和尽可能多的可选功能,但占用存储空间仍少于 100 MB(其他 App 单核心就占用大于 100 MB) • 所有核心采用 TUN 桥接,且仅选用核心会被激活,保证极致的性能和占用 安全: • Everywhere Proxy 为开源软件,源代码公开透明

❤7🎃3

12 May 2026, 12:53 UTC≈1,780 views1 reactionsread 15 August 2026

Anywhere 1.10 for iOS 现已正式上线 体验优化: • 极佳的稳定性与一系列小问题修复 • Sudoku 协议优化 • 支持节点/订阅排序 新功能: • VLESS Encryption 支持(仅限 iOS 26) • 完整的 MITM 工具箱(实验性功能)

❤1

29 Apr 2026, 02:45 UTC≈2,510 views6 reactionsread 15 August 2026
Photo

Anywhere 1.9 for iOS & Android 现已正式上线 - (iOS) 更改了图标颜色,Anywhere 图标更赏心悦目 - (iOS) 大幅优化上传与下载性能,解决吞吐量瓶颈 - (Android) 全新设计的Anywhere 图标,完美适配 Pixel 原生设计 - (Android) 带来与 iOS 版本一致的功能与体验

👍6

21 Apr 2026, 14:00 UTC≈2,070 viewsread 15 August 2026

Anywhere 1.8版本 iOS 下载:App Store Android 下载:Play Store

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

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

“Anywhere Official Channel” (@anywhere_channel), 799 subscribers as measured 18 November 2026. Telegram Register, tgregister.com/channel/anywhere_channel.

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.