Channel
@OpenVPN_WireGuard
On this record: Growth · Engagement · Reactions · Posts · Cite this entry
458subscribers
-21 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002561099717 |
|---|---|
| Type | Channel |
| Username | @OpenVPN_WireGuard |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/OpenVPN_WireGuard |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 06:08 | 458 | -4 |
| 23 Aug 2026, 19:42 | 462 | -10 |
| 15 Aug 2026, 13:59 | 472 | -5 |
| 8 Aug 2026, 07:47 | 477 | -2 |
| 8 Aug 2026, 04:34 | 479 | no change |
| 7 Aug 2026, 18:18 | 479 | first reading |
20 posts held, back to 2 June 2026 — 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 pageof 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 5 July 2026. An engagement rate over an empty window would be a number about nothing.
143 reactions across 20 posts, in 10 distinct kinds. The most used accounts for 53.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 76 | 53.1% | |
| 🔥 | 17 | 11.9% | |
| 🙏 | 16 | 11.2% | |
| ❤🔥 | 14 | 9.79% | |
| 🤩 | 6 | 4.20% | |
| ⚡ | 4 | 2.80% | |
| 👍 | 4 | 2.80% | |
| 🕊 | 3 | 2.10% | |
| 🗿 | 2 | 1.40% | |
| 👌 | 1 | 0.699% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 20 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 143reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 2 June 2026 to 5 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
🌐 Protocol: 𝗪𝗶𝗿𝗲𝗚𝘂𝗮𝗿𝗱 📍 Server: Germany 🇩🇪 — stable & low latency ⚠️ Note: Free config — may stop working anytime; updated daily 🔔 Tip: Turn on notifications to get the latest configs! 🔒 Disclaimer: Use responsibly & legally https://t.me/OpenVPN_WireGuard
👍3❤1🗿1
Host Names: us1.sstpcon.com us2.sstpcon.com us3.sstpcon.com us4.sstpcon.com us5.sstpcon.com us6.sstpcon.com uk1.sstpcon.com uk4.sstpcon.com uk6.sstpcon.com uk8.sstpcon.com nl1.sstpcon.com nl2.sstpcon.com de1.sstpcon.com lt1.sstpcon.com lu1.sstpcon.com ca1.sstpcon.com pl1.sstpcon.com pl2.sstpcon.com pl3.sstpcon.com fr1.sstpcon.com sg1.sstpcon.com au1.sstpcon.com ru1.sstpcon.com 🌐 Protocol: SSTP Username: jcdcoozg Pas…
❤4
Host Names: us1.sstpcon.com us2.sstpcon.com us3.sstpcon.com us4.sstpcon.com us5.sstpcon.com us6.sstpcon.com uk1.sstpcon.com uk4.sstpcon.com uk6.sstpcon.com uk8.sstpcon.com nl1.sstpcon.com nl2.sstpcon.com de1.sstpcon.com lt1.sstpcon.com lu1.sstpcon.com ca1.sstpcon.com pl1.sstpcon.com pl2.sstpcon.com pl3.sstpcon.com fr1.sstpcon.com sg1.sstpcon.com au1.sstpcon.com ru1.sstpcon.com 🌐 Protocol: SSTP Username: mfuypiat Pas…
❤4🕊2🔥1🤩1
🌐 Protocol: 𝗪𝗶𝗿𝗲𝗚𝘂𝗮𝗿𝗱 📍 Server: USA 🇺🇸 — stable & low latency ⚠️ Note: Free config — may stop working anytime; updated daily 🔔 Tip: Turn on notifications to get the latest configs! 🔒 Disclaimer: Use responsibly & legally
❤4👍1🔥1
Host Names: us1.sstpcon.com us2.sstpcon.com us3.sstpcon.com us4.sstpcon.com us5.sstpcon.com us6.sstpcon.com uk1.sstpcon.com uk4.sstpcon.com uk6.sstpcon.com uk8.sstpcon.com nl1.sstpcon.com nl2.sstpcon.com de1.sstpcon.com lt1.sstpcon.com lu1.sstpcon.com ca1.sstpcon.com pl1.sstpcon.com pl2.sstpcon.com pl3.sstpcon.com fr1.sstpcon.com sg1.sstpcon.com au1.sstpcon.com ru1.sstpcon.com 🌐 Protocol: SSTP Username: lwihgfjs Pas…
❤7❤🔥1🔥1🤩1
us1.sstpcon.com us2.sstpcon.com us3.sstpcon.com us4.sstpcon.com us5.sstpcon.com us6.sstpcon.com uk1.sstpcon.com uk4.sstpcon.com uk6.sstpcon.com uk8.sstpcon.com nl1.sstpcon.com nl2.sstpcon.com de1.sstpcon.com lt1.sstpcon.com lu1.sstpcon.com ca1.sstpcon.com pl1.sstpcon.com pl2.sstpcon.com pl3.sstpcon.com fr1.sstpcon.com sg1.sstpcon.com au1.sstpcon.com ru1.sstpcon.com 🌐 Protocol: SSTP Username: fjkaaaag Password: nowhr…
❤🔥6❤3⚡1
us1.sstpcon.com us2.sstpcon.com us3.sstpcon.com us4.sstpcon.com us5.sstpcon.com us6.sstpcon.com uk1.sstpcon.com uk4.sstpcon.com uk6.sstpcon.com uk8.sstpcon.com nl1.sstpcon.com nl2.sstpcon.com de1.sstpcon.com lt1.sstpcon.com lu1.sstpcon.com ca1.sstpcon.com pl1.sstpcon.com pl2.sstpcon.com pl3.sstpcon.com fr1.sstpcon.com sg1.sstpcon.com au1.sstpcon.com ru1.sstpcon.com 🌐 Protocol: SSTP Username: skbrdqix Password: bpaas…
❤9
🌐 Protocol: Napsternet 📍 Server: USA 🇺🇸 — stable & low latency ⚠️ Note: Free config — may stop working anytime; updated daily 🔔 Tip: Turn on notifications to get the latest configs! 🔒 Disclaimer: Use responsibly & legally https://t.me/OpenVPN_WireGuard
❤🔥5❤2🔥2🤩1
🌐 Protocol: Napsternet 📍 Server: USA 🇺🇸 — stable & low latency ⚠️ Note: Free config — may stop working anytime; updated daily 🔔 Tip: Turn on notifications to get the latest configs! 🔒 Disclaimer: Use responsibly & legally https://t.me/OpenVPN_WireGuard
❤4
File, posted without a caption
❤2🔥1🕊1
us1.sstpcon.com us2.sstpcon.com us3.sstpcon.com us4.sstpcon.com us5.sstpcon.com us6.sstpcon.com uk1.sstpcon.com uk4.sstpcon.com uk6.sstpcon.com uk8.sstpcon.com nl1.sstpcon.com nl2.sstpcon.com de1.sstpcon.com lt1.sstpcon.com lu1.sstpcon.com ca1.sstpcon.com pl1.sstpcon.com pl2.sstpcon.com pl3.sstpcon.com fr1.sstpcon.com sg1.sstpcon.com au1.sstpcon.com ru1.sstpcon.com 🌐 Protocol: SSTP Username: ovwjzrih Password: f13va…
❤2🔥2🙏1
🌐 Protocol: Napsternet 📍 Server: USA 🇺🇸 — stable & low latency ⚠️ Note: Free config — may stop working anytime; updated daily 🔔 Tip: Turn on notifications to get the latest configs! 🔒 Disclaimer: Use responsibly & legally https://t.me/OpenVPN_WireGuard
❤2🔥1
Showing the 12 most recent of 20 posts we hold for @OpenVPN_WireGuard. 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.
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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“OpenVPN & WireGuard” (@OpenVPN_WireGuard), 458 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/OpenVPN_WireGuard.
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.