Telegram RegisterThe public register of Telegram
Telegram profile photo for Vice ox

Channel

Vice ox

@oxigenvpn

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

504,583subscribers

-39,696 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 316,228–1,000,000.

Register entry

Telegram ID-1001114190131
TypeChannel
Username@oxigenvpn
Created20 May 2017measured — dated from the channel’s first post
First recorded6 August 2026
Last confirmed live7 September 2026
Measurements held29
Confirmed unchanged1 time, most recently 7 September 2026
On Telegramt.me/oxigenvpn

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 100% 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

504,583544,279524,4316 August 2026 — 544,279 subscribers6 August 2026 — 543,833 subscribers7 August 2026 — 542,720 subscribers8 August 2026 — 541,219 subscribers9 August 2026 — 539,559 subscribers10 August 2026 — 538,208 subscribers11 August 2026 — 536,678 subscribers12 August 2026 — 535,381 subscribers12 August 2026 — 534,024 subscribers14 August 2026 — 532,263 subscribers15 August 2026 — 530,018 subscribers17 August 2026 — 528,396 subscribers18 August 2026 — 526,781 subscribers19 August 2026 — 525,640 subscribers20 August 2026 — 524,397 subscribers21 August 2026 — 523,053 subscribers22 August 2026 — 520,874 subscribers24 August 2026 — 519,387 subscribers25 August 2026 — 518,383 subscribers26 August 2026 — 516,919 subscribers27 August 2026 — 516,126 subscribers28 August 2026 — 515,173 subscribers29 August 2026 — 513,561 subscribers30 August 2026 — 512,337 subscribers31 August 2026 — 511,420 subscribers1 September 2026 — 510,599 subscribers2 September 2026 — 509,101 subscribers4 September 2026 — 507,634 subscribers7 September 2026 — 504,583 subscribers6 August 20267 September 2026
29 measurements spanning 33 days, net -39,696. 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 498,629–550,233 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 29
Measured (UTC)SubscribersChange
7 Sept 2026, 15:42504,583-3,051
4 Sept 2026, 15:22507,634-1,467
2 Sept 2026, 23:55509,101-1,498
1 Sept 2026, 18:55510,599-821
31 Aug 2026, 21:45511,420-917
30 Aug 2026, 23:05512,337-1,224
29 Aug 2026, 20:15513,561-1,612
28 Aug 2026, 16:56515,173-953
27 Aug 2026, 15:13516,126-793
26 Aug 2026, 15:03516,919-1,464
25 Aug 2026, 17:01518,383-1,004
24 Aug 2026, 15:43519,387-1,487
22 Aug 2026, 23:57520,874-2,179
21 Aug 2026, 12:07523,053-1,344
20 Aug 2026, 09:22524,397-1,243
19 Aug 2026, 12:36525,640-1,141
18 Aug 2026, 11:02526,781-1,615
17 Aug 2026, 09:35528,396-1,622
15 Aug 2026, 20:07530,018-2,245
14 Aug 2026, 08:57532,263first reading

Engagement

1 post held, back to 20 May 2017the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 72 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 1 post for this entry, the most recent from 20 May 2017. An engagement rate over an empty window would be a number about nothing.

Recent posts

Showing the 1 most recent of 1 post we hold for @oxigenvpn. 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 5 registered channels — 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.

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

“Vice ox” (@oxigenvpn), 504,583 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/oxigenvpn.

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.