Telegram RegisterThe public register of Telegram
Telegram profile photo for Pharos Pro For Android Announcements

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
TypeChannel
Username@Pharos_Pro_Announcements
CreatedBetween 1 March 2018 and 4 March 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live7 November 2026
Measurements held25
Confirmed unchanged1 time, most recently 7 November 2026
On Telegramt.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

2,8112,9162,863.56 August 2026 — 2,916 subscribers6 August 2026 — 2,915 subscribers9 August 2026 — 2,913 subscribers12 August 2026 — 2,909 subscribers15 August 2026 — 2,904 subscribers18 August 2026 — 2,899 subscribers22 August 2026 — 2,895 subscribers25 August 2026 — 2,893 subscribers28 August 2026 — 2,891 subscribers31 August 2026 — 2,885 subscribers3 September 2026 — 2,879 subscribers9 September 2026 — 2,874 subscribers13 September 2026 — 2,872 subscribers17 September 2026 — 2,871 subscribers26 September 2026 — 2,861 subscribers5 October 2026 — 2,854 subscribers13 October 2026 — 2,843 subscribers17 October 2026 — 2,839 subscribers20 October 2026 — 2,836 subscribers23 October 2026 — 2,832 subscribers26 October 2026 — 2,827 subscribers29 October 2026 — 2,825 subscribers1 November 2026 — 2,820 subscribers4 November 2026 — 2,817 subscribers7 November 2026 — 2,811 subscribers6 August 20267 November 2026
25 measurements spanning 93 days, net -105. 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 2,795–2,932 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 25
Measured (UTC)SubscribersChange
7 Nov 2026, 17:452,811-6
4 Nov 2026, 21:462,817-3
1 Nov 2026, 16:512,820-5
29 Oct 2026, 22:562,825-2
26 Oct 2026, 19:302,827-5
23 Oct 2026, 13:152,832-4
20 Oct 2026, 06:172,836-3
17 Oct 2026, 09:312,839-4
13 Oct 2026, 23:302,843-11
5 Oct 2026, 03:192,854-7
26 Sept 2026, 08:582,861-10
17 Sept 2026, 09:392,871-1
13 Sept 2026, 10:192,872-2
9 Sept 2026, 03:162,874-5
3 Sept 2026, 19:362,879-6
31 Aug 2026, 05:232,885-6
28 Aug 2026, 14:272,891-2
25 Aug 2026, 17:322,893-2
22 Aug 2026, 16:272,895-4
18 Aug 2026, 23:322,899first 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

30 Oct 2023, 15:35 UTC≈10,100 viewsread 7 August 2026
File

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

25 Oct 2023, 20:56 UTC≈9,520 viewsread 7 August 2026
File

- Routen 0.1.0: - 支持IPv6,需要在设置中打开选项 - 请确认自己的网络支持ipv6 - 默认重定向 http://www.google.cn 至 https://www.google.com

18 Oct 2023, 15:29 UTC≈9,450 viewsread 7 August 2026
File

- 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

13 Oct 2023, 19:12 UTC≈7,220 viewsread 7 August 2026
File

- 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响应慢的问题 - 去除不必要的性能花销

8 Oct 2023, 19:47 UTC≈6,600 viewsread 7 August 2026
File

Routen - 0.0.5 - 修复hy2崩溃的问题 - 修复上一版本dns异常的问题

6 Apr 2021, 18:09 UTC≈24,000 viewsread 7 August 2026
File

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