Telegram RegisterThe public register of Telegram
Telegram profile photo for UX加速器通知频道

Channel

UX加速器通知频道

@uxvpnTG

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

53subscribers

+0 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001154542036
TypeChannel
Username@uxvpnTG
CreatedBetween 1 October 2018 and 25 October 2020 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live8 October 2026
Measurements held4
Confirmed unchanged1 time, most recently 8 October 2026
On Telegramt.me/uxvpnTG

Topic

Other / unclassifiable — 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 29 September 2026 and assigned it the closest of 31 fixed categories, at 58% 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 why it has no browse page of its own yet.

Growth

525352.56 August 2026 — 53 subscribers10 August 2026 — 53 subscribers22 August 2026 — 52 subscribers8 October 2026 — 53 subscribers6 August 20268 October 2026
4 measurements spanning 63 days. 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 52–53 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Oct 2026, 19:4053+1
22 Aug 2026, 15:0552-1
10 Aug 2026, 09:3153no change
6 Aug 2026, 20:3753first reading

Engagement

19 posts held, back to 25 October 2020 — 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 19 posts for this entry, the most recent from 30 November 2020. An engagement rate over an empty window would be a number about nothing.

Recent posts

30 Nov 2020, 07:40 UTC382 viewsread 10 August 2026

官网服务器供应商机房调整磁盘阵列 暂时无法访问,恢复另行通知

22 Nov 2020, 09:58 UTC354 viewsread 10 August 2026

目前SSR-V2ray可用节点-其他地区以及V2ray的AGA稍后添加

21 Nov 2020, 00:32 UTC292 viewsread 10 August 2026
File

目前恢复的部分节点,剩下的稍后添加和恢复,通宵一晚遭不住了,先去恰个早餐(有效用户请提交工单,赠送30天有效时长--白嫖用户请别提交工单增加我工作量,删号警告)

20 Nov 2020, 17:40 UTC240 viewsread 10 August 2026

白天其他地区节点恢复-全部有效用户统一增加一个月有效时长,白天添加完节点给你们一起添加,感谢大家支持

5 Nov 2020, 06:34 UTC345 viewsread 10 August 2026

下午更换官网服务器,可能出现短暂无法访问

Showing the 12 most recent of 19 posts we hold for @uxvpnTG. 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 8 October 2026 — this entry's latest reading, not the date you are reading this.

“UX加速器通知频道” (@uxvpnTG), 53 subscribers as measured 8 October 2026. Telegram Register, tgregister.com/channel/uxvpnTG.

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.