Channel
@XeovoVPN
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
9,492subscribers
-106 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001327322194 |
|---|---|
| Type | Channel |
| Username | @XeovoVPN |
| Description | Key to your privacy. Website: xeovo.com Guides: xeovo.com/guides Hub: hub.xeovo.com Server status: status.xeovo.com |
| Created | 2 June 2018 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 6 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/XeovoVPN |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 15:28 | 9,492 | -24 |
| 10 Aug 2026, 20:17 | 9,516 | -75 |
| 7 Aug 2026, 20:40 | 9,591 | -7 |
| 6 Aug 2026, 21:00 | 9,598 | no change |
| 6 Aug 2026, 20:56 | 9,598 | first reading |
21 posts held, back to 17 January 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 16 pagesof Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 9 August 2026 |
|---|---|
| Posts held | 21 (17 January 2024 – 9 August 2026) |
| Views total | 10,450 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 15 Aug 2026, 08:33 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 15 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Friendly reminder, the most common reason Stealth Proxies stop working is an outdated subscription in your client. If you don’t update it, the client won’t fetch new servers or remove inactive ones. To fix this, you have two options: 1. Manually update the subscription every time before connecting to servers. 2. Enable automatic subscription updates (for example, every hour or less often). If the subscription upd…
We want to thank everyone who contributed and helped us create proper router tutorials, something that had been lacking for years. In a short time, our awesome community created 28 high-quality tutorials. To our surprise, most router models were reserved within just a couple of hours and the tutorials were completed within a few days. This was very successful, and we will definitely plan something similar for our c…
Chat Control returns tomorrow. Not because a majority wants it, but because the vote was scheduled when MEPs are on vacation and empty seats count as yes. Empty chairs will vote for 450 million people. https://hub.xeovo.com/posts/204-chat-control-comes-back-tomorrow-unless-you-act-today
Xeovo has contributed to the Tor × Funding the Commons matching pool. The campaign helps projects that build tools for privacy, anti-censorship and journalists. https://hub.xeovo.com/posts/198-xeovo-donates-to-tor-x-funding-the-commons
Router experts wanted. Our first community guide bounties are now open. Write and record tutorials for Xeovo and get paid. Available bounties include OpenWrt, MikroTik, pfSense, DD-WRT, Asuswrt-Merlin, Keenetic, XKeen and more. https://hub.xeovo.com/posts/171-we-are-looking-for-router-experts-make-a-tutorial-and-get-paid
More countries are trying to block access to Telegram. But no worries, we are providing free MTProto Proxies for everyone. This is not a basic implementation of MTProto and includes advanced features designed to perform better in heavily censored regions. Find access links and more information in our post. Feel free to share it with your family, friends and colleagues if it helps. https://hub.xeovo.com/posts/149-p…
Transparency report for 2025 is now available. https://hub.xeovo.com/posts/131-transparency-report-for-2025
This is the pilot episode of our new interview series Meet the Developer, where we talk to the people behind anti-censorship tools. Our goal is to shine a light on the developers whose open-source solutions help millions of people stay connected. In this first episode, we sit down with Toby, the lead developer of Hysteria, to discuss the project’s origins, technical challenges and his perspective on internet censor…
We said no more new protocols. We lied. Hysteria 2.0 is out of beta. Our 8th protocol. Same price. No bundles. No extra charges. One subscription. We got the chance to sit down with the Hysteria lead developer. Your questions could make it into the upcoming interview. https://hub.xeovo.com/posts/115-hysteria-20-launch-new-way-to-bypass-censorship
Our support team says hi to everyone! Oh, and there are cat memes. And a guide on writing amazing support tickets. https://hub.xeovo.com/posts/87-how-to-write-a-good-ticket
Don't let Facebook and Instagram use your posts, chats and photos to feed its AI models. EU users can officially opt out starting today. Or better just delete your account. https://hub.xeovo.com/posts/85-dont-feed-metas-ai-models-on-your-content-eu-only
Xeovo 2.0 Our biggest update yet with a complete redesign, new features, new locations and a strong foundation for the future. https://hub.xeovo.com/posts/80-xeovo-20-is-here-new-design-features-and-locations
Showing the 12 most recent of 21 posts we hold for @XeovoVPN. 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.
Citation-graph rank — 983,865 of 1,350,102entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“Xeovo VPN” (@XeovoVPN), 9,492 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/XeovoVPN.
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.