Channel
@vpn_door
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
35subscribers
+0 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001827534210 |
|---|---|
| Type | Channel |
| Username | @vpn_door |
| Created | 8 October 2022 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/vpn_door |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 06:30 | 35 | no change |
| 12 Aug 2026, 06:16 | 35 | first reading |
18 posts held, back to 8 October 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 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 18 posts for this entry, the most recent from 21 January 2023. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 12 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.
80 reactions across 10 posts, in 8 distinct kinds. The most used accounts for 75.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 60 | 75.0% | |
| 💩 | 6 | 7.50% | |
| 👏 | 4 | 5.00% | |
| 🔥 | 4 | 5.00% | |
| 👎 | 2 | 2.50% | |
| 💯 | 2 | 2.50% | |
| 😢 | 1 | 1.25% | |
| 🥰 | 1 | 1.25% |
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 10 of the 18 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 80 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 8 October 2022 to 21 January 2023, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
https://t.me/proxy?server=cloudflare.com.nokia.com.co.uk.do_yo.want_to.clash_with.this.www.microsoft.com.there_is_no.place_like.localhost.www.bing.com.count_with_me.cyou.io.now_sudo.rm.again_to_fight.everyone.i_am.the_internet.irancell-ir-irancell-ir-irancell-ir-irancell-ir.sbs&port=443&secret=7jK5IN_7UWQwKOL2uHjU6sFteS5zaGFwYXJhay5pcg https://t.me/proxy?server=cloudflare.com.nokia.com.co.uk.do_yo.want_to.clash_with…
👍2
https://t.me/proxy?server=185.221.219.42&port=443&secret=ee1603010200010001fc030386e24c3add6d736e2e636f6d https://t.me/proxy?server=89.185.85.175&port=443&secret=eeef7a703e9b46178d99ad8c40a6f03d396d736e2e636f6d https://t.me/proxy?server=5.252.118.245&port=443&secret=eef0eba92dc4be1d9409e37d83c746ee726d736e2e636f6d https://t.me/proxy?server=209.127.228.150&port=443&secret=ee32b920dffb51643028e2f6b878d4eac16d736e2e6…
✅ پروکسی فول سرعت مخصوص کانال 💢 @Music_voisc 💢 https://t.me/proxy?server=79.133.120.84&port=8080&secret=7oyQuv8i1d-DPDDhx5kJwXNhbWF6b25hd3MuY29t 🔴 #پروکسی_پر_سرعت لینک کانال موزیک ویس👇👇 https://t.me/+kcv2lI7XlfFkYjc0
https://t.me/proxy?server=79.133.120.84&port=8080&secret=7oyQuv8i1d-DPDDhx5kJwXNhbWF6b25hd3MuY29t
https://t.me/proxy?server=193.38.55.115&port=8443&secret=ee22ebe47f2fc015484b783657b82ddb69696d616765732e6170706c652e636f6d20&@Freeirnet
👍2
✅ پروکسی فول سرعت مخصوص کانال 💢 @Music_voisc 💢 https://t.me/proxy?server=79.133.120.84&port=8080&secret=7oyQuv8i1d-DPDDhx5kJwXNhbWF6b25hd3MuY29t 🔴 #پروکسی_پر_سرعت
👍2
تست شده روی #همراه_اول ➖ اتصال به پروکسی 1 ➖ اتصال به پروکسی 2 ➖ اتصال به پروکسی 3 ➖ اتصال به پروکسی 4 ➖ اتصال به پروکسی 5 ➖ اتصال به پروکسی 6 ➖ اتصال به پروکسی 7 ➖ اتصال به پروکسی 8 ➖ اتصال به پروکسی 9 ➖ اتصال به پروکسی 10 ➖ اتصال به پروکسی 11 ➖ اتصال به پروکسی 12 ➖ اتصال به پروکسی 13 ➖ اتصال به پروکسی 14 ➖ اتصال به پروکسی 15 ➖ اتصال به پروکسی 16 💢 @vpn_door 💢
👍1
پروکسی های فعال ➴➴➴➴ @vpn_door @vpn_door 1 @vpn_door 2 @vpn_door 3 https://t.me/vpn_door
💢 غم و درد عاشقی ، قلبمو داغون کرده🥀🖤 💢 اون غرور لعنتی ، این دلمو خون کرده🥀🖤 💢 اخه چی شدش که من ، بازم خوردم ازت رکب🥀🖤 💢 @Music_voisc 💢
https://t.me/proxy?server=159.69.16.168&port=443&secret=7jK5IN_7UWQwKOL2uHjU6sFteS5pcmFuY2VsbC5pcg
https://t.me/proxy?server=167.235.156.179&port=443&secret=7jK5IN_7UWQwKOL2uHjU6sFteS5pcmFuY2VsbC5pcg
👍4
#فیلترشکن فیلترشکن✌️ 💢 @Music_voisc 💢
👍10🥰1
Showing the 12 most recent of 18 posts we hold for @vpn_door. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 2 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.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“Vpn Door” (@vpn_door), 35 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/vpn_door.
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.