Channel
@dwvpn
On this record: Growth · Engagement · Posts · Cite this entry
145subscribers
+7 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001110060083 |
|---|---|
| Type | Channel |
| Username | @dwvpn |
| Created | Between 1 February 2017 and 30 June 2019— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 24 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 24 August 2026 |
| On Telegram | t.me/dwvpn |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 24 Aug 2026, 16:48 | 145 | +6 |
| 17 Aug 2026, 10:16 | 139 | +1 |
| 8 Aug 2026, 23:01 | 138 | no change |
| 7 Aug 2026, 20:58 | 138 | first reading |
20 posts held, back to 2 November 2022 — 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 2 March 2025. An engagement rate over an empty window would be a number about nothing.
The owner of this channel has been inactive for the last 17 months. If they remain inactive for the next 10 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
The owner of this channel has been inactive for the last 17 months. If they remain inactive for the next 18 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
The owner of this channel has been inactive for the last 17 months. If they remain inactive for the next 30 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
The owner of this channel has been inactive for the last 11 months. If they remain inactive for the next 28 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
New servers have been added. IN2 (Delhi, India) and PK1 (Karachi, Pakistan). Download the new configs please. ————— Были добавлены новые серверы. IN2 (Дели, Индия) и PK1 (Карачи, Пакистан). Добавьте новые конфигурации, пожалуйста. ————— فعلنا الخوادم الجدد: IN2(دلهي، الهند) و PK1(كراتشي، باكستان). خذ ملفات التكوين جدد رجاء ————— OpenVPN: https://dash.deepwebvpn.net/en/download?goto=openvpn/single/SingleRSA_IN2.…
Signed DeepWebVPN
DE3 (Frankfurt, Germany) has migrated to another datacenter in Frankfurt am Main. The default OpenVPN and SoftEther configs of DE3 (domain name based) were not changed, the configs based on IP were changed. Update it please. ————— DE3 (Франкфурт, Германия) переехал в другой датацентр Франкфурта-на-Майне. OpenVPN и SoftEther конфиги DE3 по умолчанию (на базе доменного имени) не изменились, конфиги на основе адресаци…
Signed DeepWebVPN
FR3 (France) has migrated from Lille to Nice. The default OpenVPN and SoftEther configs of FR3 (domain name based) were not changed, the configs based on IP were changed. Update it please. ————— FR3 (Франция) переехал из Лилля в Ниццу. OpenVPN и SoftEther конфиги FR3 по умолчанию (на базе доменного имени) не изменились, конфиги на основе адресации по IP изменились. Обновите их если требуется. ————— OpenVPN: https…
Signed DeepWebVPN
US1 (USA) has migrated from Vint Hill (Virginia) to Piscataway (New Jersey). Also RU4 (St. Petersburg, Russia) has changed datacenter in St. Petersburg. The default OpenVPN and SoftEther configs of US1 and RU4 (domain name based) were not changed, the configs based on IP were changed. Update the configs please. ————— US1 (США) переехал из Винт-Хилла (Вирджиния) в Пискатавэй (Нью-Джерси). Также RU4 (Санкт-Петербург,…
Signed DeepWebVPN
CH2 (Geneva, Switzerland) has migrated to another datacenter in Geneva. The default OpenVPN and SoftEther configs of CH2 (domain name based) were not changed, the configs based on IP were changed. Update it please. ————— CH2 (Женева, Швейцария) переехал в другой датацентр Женевы. OpenVPN и SoftEther конфиги CH2 по умолчанию (на базе доменного имени) не изменились, конфиги на основе адресации по IP изменились. Обнов…
Signed DeepWebVPN
LV1 (Riga, Latvia) has migrated to another datacenter in Riga. Also US2 (New York, USA) has migrated to another DC in New York. The default OpenVPN and SoftEther configs of LV1 and US2 (domain name based) were not changed, the configs based on IP were changed. Update it please. ————— LV1 (Рига, Латвия) переехал в другой датацентр Риги. Также US2 (Нью-Йорк, США) сменил ДЦ в Нью-Йорке. OpenVPN и SoftEther конфиги LV1…
Signed DeepWebVPN
New servers have been added. AT2 (Graz, Austria) and RS1 (Belgrade, Serbia). Download the new configs please. ————— Были добавлены новые серверы. AT2 (Грац, Австрия) и RS1 (Белград, Сербия). Добавьте новые конфигурации, пожалуйста. ————— OpenVPN: https://dash.deepwebvpn.net/en/download?goto=openvpn/single/SingleRSA_AT2.ovpn https://dash.deepwebvpn.net/en/download?goto=openvpn/single/SingleECC_AT2.ovpn https://das…
Signed DeepWebVPN
NS1 (DNS server for Western Europe) has migrated from France to Madrid, Spain. The new IP of NS1 is shown on the subscription page (https://dash.deepwebvpn.net/en/subscriptions/configs). Update it please if you use VPN chains from Western Europe. Sorry for the inconvenience caused. ————— NS1 (западноевропейский DNS-сервер) переехал из Франции в Мадрид, Испания. Новый IP-адрес NS1 доступен на странице подписки (http…
Signed DeepWebVPN
Showing the 12 most recent of 20 posts we hold for @dwvpn. 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 24 August 2026 — this entry's latest reading, not the date you are reading this.
“DeepWebVPN” (@dwvpn), 145 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/dwvpn.
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.