- Routen 0.1.1 - 支持链接之后,通过访问 http://routen.ca 下载并安装ca证书

Channel
Pharos Pro For Android Announcements
@Pharos_Pro_Announcements
On this record: Topic · Growth · Engagement · Posts · Cite this entry
2,811subscribers
-105 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001205050984 |
|---|---|
| Type | Channel |
| Username | @Pharos_Pro_Announcements |
| Created | Between 1 March 2018 and 4 March 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/Pharos_Pro_Announcements |
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 15 September 2026 and assigned it the closest of 31 fixed categories, at 79% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Nov 2026, 17:45 | 2,811 | -6 |
| 4 Nov 2026, 21:46 | 2,817 | -3 |
| 1 Nov 2026, 16:51 | 2,820 | -5 |
| 29 Oct 2026, 22:56 | 2,825 | -2 |
| 26 Oct 2026, 19:30 | 2,827 | -5 |
| 23 Oct 2026, 13:15 | 2,832 | -4 |
| 20 Oct 2026, 06:17 | 2,836 | -3 |
| 17 Oct 2026, 09:31 | 2,839 | -4 |
| 13 Oct 2026, 23:30 | 2,843 | -11 |
| 5 Oct 2026, 03:19 | 2,854 | -7 |
| 26 Sept 2026, 08:58 | 2,861 | -10 |
| 17 Sept 2026, 09:39 | 2,871 | -1 |
| 13 Sept 2026, 10:19 | 2,872 | -2 |
| 9 Sept 2026, 03:16 | 2,874 | -5 |
| 3 Sept 2026, 19:36 | 2,879 | -6 |
| 31 Aug 2026, 05:23 | 2,885 | -6 |
| 28 Aug 2026, 14:27 | 2,891 | -2 |
| 25 Aug 2026, 17:32 | 2,893 | -2 |
| 22 Aug 2026, 16:27 | 2,895 | -4 |
| 18 Aug 2026, 23:32 | 2,899 | first reading |
Engagement
20 posts held, back to 4 March 2021 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages 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 20 posts for this entry, the most recent from 30 October 2023. An engagement rate over an empty window would be a number about nothing.
Recent posts
- Routen 0.1.0: - 支持IPv6,需要在设置中打开选项 - 请确认自己的网络支持ipv6 - 默认重定向 http://www.google.cn 至 https://www.google.com
- Routen 0.0.9: - 修复部分订阅无限闪退的问题 - 简化mieru link格式 - 示例:mieru://server:port?username=john&password=secret&network=tcp#Google - 格式讨论详情参见: - https://github.com/enfein/mieru/discussions/60#discussioncomment-7302288
Routen - 0.0.7 - 修复部分订阅闪退的问题
- Routen 0.0.6 更新: - 支持导入节点link,支持协议如下: - ss://xxx - ssr://xxx - mieru://xxx - trojan://xxx - vmess://xxx - vless://xxx - tuic://xxx - hysteria://xxx - hysteria2://xxx - 请使用换行符隔开每一个节点link - 修复某些情况下dns响应慢的问题 - 去除不必要的性能花销
Routen - 0.0.5 - 修复hy2崩溃的问题 - 修复上一版本dns异常的问题
- 0.0.3 - 支持 hysteria 2 (hysteria2://xxxx)
- 0.0.2 - 修复开关状态显示不正确的问题
#Remove code dlg.
# Fixed vless crash in subscribe
# Supported vless over ws
# Supported vless with xtls note: vless link—> https://github.com/XTLS/Xray-core/issues/91
Showing the 12 most recent of 20 posts we hold for @Pharos_Pro_Announcements. 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.
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 7 November 2026 — this entry's latest reading, not the date you are reading this.
“Pharos Pro For Android Announcements” (@Pharos_Pro_Announcements), 2,811 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/Pharos_Pro_Announcements.
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.