๐๏ธ V2Ray VLESS Server ๐ IP Address : 138.16.140.5 โ๏ธ Response : 83ms ๐บ๏ธ Location : ๐ณ๐ฑ The Netherlands, South Holland, Rotterdam ๐ Timezone : Europe/Amsterdam ๐ผ ORG : RACKTECH CO., LTD ๐ฃ ISP : RACKTECH CO., LTD. vless://[email protected]:443?type=grpc&serviceName=trgrpc&fp=chrome&security=tls#๐ณ๐ฑ[openproxylist.com] vless-NL

Channel
V2Nodes ๐
@v2nodes
On this record: Growth ยท Engagement ยท Reactions ยท Posts ยท Citations ยท Cite this entry
18,928subscribers
+35 since we began measuring on 7 August 2026
Risers and fallers across the register ยท movement among entries of 10,000โ31,623.
Register entry
| Telegram ID | -1001981930313 |
|---|---|
| Type | Channel |
| Username | @v2nodes |
| Created | Between 1 April 2023 and 31 October 2023โ estimated from Telegramโs id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 31 August 2026 |
| Measurements held | 23 |
| Confirmed unchanged | 1 time, most recently 31 August 2026 |
| On Telegram | t.me/v2nodes |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 31 Aug 2026, 10:48 | 18,928 | +2 |
| 30 Aug 2026, 11:24 | 18,926 | -8 |
| 29 Aug 2026, 10:57 | 18,934 | +15 |
| 28 Aug 2026, 10:02 | 18,919 | -1 |
| 27 Aug 2026, 10:23 | 18,920 | +4 |
| 26 Aug 2026, 11:57 | 18,916 | -2 |
| 25 Aug 2026, 15:05 | 18,918 | -4 |
| 24 Aug 2026, 13:36 | 18,922 | -11 |
| 22 Aug 2026, 19:52 | 18,933 | +1 |
| 21 Aug 2026, 10:26 | 18,932 | +3 |
| 20 Aug 2026, 09:22 | 18,929 | -14 |
| 19 Aug 2026, 08:03 | 18,943 | +3 |
| 18 Aug 2026, 08:17 | 18,940 | -15 |
| 17 Aug 2026, 11:33 | 18,955 | +5 |
| 15 Aug 2026, 20:46 | 18,950 | +13 |
| 14 Aug 2026, 12:55 | 18,937 | +5 |
| 12 Aug 2026, 08:18 | 18,932 | +10 |
| 11 Aug 2026, 08:42 | 18,922 | +12 |
| 10 Aug 2026, 05:34 | 18,910 | +6 |
| 9 Aug 2026, 05:51 | 18,904 | first reading |
Engagement
334 posts held, back to 5 August 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 49 pagesof Telegramโs post history, 20 posts per page.
- ERR ยท 30 days
- 2.04%
- avg views รท 18,928 subscribers
- Avg views / post
- 387
- 334 posts measured
- Reaction rate
- 0.309%
- reactions รท views ยท ER floor
- Posts in window
- 334
- of 334 held
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. It is computed over the 96 of 334 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days ยท latest post in window 30 August 2026 |
|---|---|
| Posts held | 334 (5 August 2026 โ 30 August 2026) |
| Views total | 129,243 |
| Reactions total | 170 |
| Forwards / comments | not exposed by the public surface โ not measured, not estimated |
| Readings taken | 30 Aug 2026, 23:38 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.
Reaction mix
170 reactions across 88 posts, in 10 distinct kinds. The most used accounts for 45.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| โค | 78 | 45.9% | |
| ๐ค | 30 | 17.6% | |
| ๐ | 22 | 12.9% | |
| ๐ | 15 | 8.82% | |
| ๐ฅฐ | 9 | 5.29% | |
| ๐ฅ | 7 | 4.12% | |
| โคโ๐ฅ | 4 | 2.35% | |
| ๐ณ | 2 | 1.18% | |
| ๐ | 2 | 1.18% | |
| ๐ | 1 | 0.588% |
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 96 of the 334 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 170reactions in total: the kind of figure the paragraph above means by โa reaction total printed elsewhere on the pageโ.
Measured over the 334 most recent posts we hold, published 5 August 2026 to 30 August 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.
Recent posts
๐๏ธ Outline VPN Server ๐ IP Address : 129.146.116.35 โ๏ธ Response : 100ms ๐บ๏ธ Location : ๐บ๐ธ United States, Arizona, Phoenix ๐ Timezone : America/Phoenix ๐ผ ORG : Oracle Cloud Infrastructure (us-phoenix-1) ๐ฃ ISP : Oracle Corporation ss://MjAyMi1ibGFrZTMtY2hhY2hhMjAtcG9seTEzMDU6bkVMOWdIY2dlNUlOZEpoSUpMMHI5UmRreEJPbjZudm1hZjZ3WXdIK0p4Zz0=@129.146.116.35:50356#๐บ๐ธ[openproxylist.com] ss-US
โค2
๐๏ธ V2Ray VLESS Server ๐ IP Address : 84.235.175.73 โ๏ธ Response : 69ms ๐บ๏ธ Location : ๐ณ๐ฑ Netherlands, North Holland, Amsterdam ๐ Timezone : Europe/Amsterdam ๐ผ ORG : Oracle Cloud Infrastructure (eu-amsterdam-1) ๐ฃ ISP : Oracle Corporation vless://[email protected]:62145?#๐ณ๐ฑ[openproxylist.com] vless-NL
๐๏ธ V2Ray VLESS Server ๐ IP Address : 212.2.35.168 โ๏ธ Response : 97ms ๐บ๏ธ Location : ๐ฎ๐น Italy, Veneto, Venezia ๐ Timezone : Europe/Rome ๐ผ ORG : HZ Na74 ๐ฃ ISP : HZ Hosting Ltd vless://[email protected]:22211?#๐ฎ๐น[openproxylist.com] vless-IT
๐๏ธ Outline VPN Server ๐ IP Address : 168.107.77.111 โ๏ธ Response : 24ms ๐บ๏ธ Location : ๐ธ๐ฌ Singapore, South East, Singapore ๐ Timezone : Asia/Singapore ๐ผ ORG : Oracle Corporation ๐ฃ ISP : Oracle Corporation ss://MjAyMi1ibGFrZTMtY2hhY2hhMjAtcG9seTEzMDU6dHpXYTFHZVV3MkVlWnBNYWZhZEEyU3BYb3dFWUJVUldqSVpuM21ycnpFbz0=@168.107.77.111:56927#๐ธ๐ฌ[openproxylist.com] ss-SG
๐ณ2โค1
๐๏ธ Outline VPN Server ๐ IP Address : 129.151.84.60 โ๏ธ Response : 70ms ๐บ๏ธ Location : ๐ฌ๐ง United Kingdom, Wales, Cardiff ๐ Timezone : Europe/London ๐ผ ORG : Oracle Cloud Infrastructure (uk-cardiff-1) ๐ฃ ISP : Oracle Corporation ss://MjAyMi1ibGFrZTMtY2hhY2hhMjAtcG9seTEzMDU6bkNzbXpmYjJJd2tWWlQ5Q0xmbXZMM3RFT0FIckhYemtYcWNaQU01N3Fxaz0=@129.151.84.60:61312#๐ฌ๐ง[openproxylist.com] ss-GB
๐๏ธ Outline VPN Server ๐ IP Address : 129.151.82.72 โ๏ธ Response : 69ms ๐บ๏ธ Location : ๐ฌ๐ง United Kingdom, Wales, Cardiff ๐ Timezone : Europe/London ๐ผ ORG : Oracle Cloud Infrastructure (uk-cardiff-1) ๐ฃ ISP : Oracle Corporation ss://MjAyMi1ibGFrZTMtY2hhY2hhMjAtcG9seTEzMDU6RjVObzZYdklMT1pjTG1tVjdXZTllL0hZNTRqUC9oV0lPazQ3dEhaSk5Paz0=@129.151.82.72:61312#๐ฌ๐ง[openproxylist.com] ss-GB
๐๏ธ Outline VPN Server ๐ IP Address : 129.146.62.211 โ๏ธ Response : 77ms ๐บ๏ธ Location : ๐บ๐ธ United States, Arizona, Phoenix ๐ Timezone : America/Phoenix ๐ผ ORG : Oracle Cloud Infrastructure (us-phoenix-1) ๐ฃ ISP : Oracle Corporation ss://MjAyMi1ibGFrZTMtY2hhY2hhMjAtcG9seTEzMDU6M1JWWHU1eEFSQ1BRbEQzRnYvY21RdDdvL1hHcVVaTHdyVFR0MEZrQTJ2bz0=@129.146.62.211:50356#๐บ๐ธ[openproxylist.com] ss-US
๐๏ธ V2Ray VLESS Server ๐ IP Address : 74.220.51.162 โ๏ธ Response : 100ms ๐บ๏ธ Location : ๐ฉ๐ช Germany, Hesse, Frankfurt am Main ๐ Timezone : Europe/Berlin ๐ผ ORG : ๐ฃ ISP : Amazon.com, Inc. vless://[email protected]:443?sni=four04-rd37.onrender.com&alpn=http/1.1&type=ws&host=four04-rd37.onrender.com&path=/ws/2ee0d2aa-867e-a77e-9538-2edfc0b242aafp=firefox&security=tls#๐ฉ๐ช[openproxylist.com] vl
๐๏ธ Outline VPN Server ๐ IP Address : 84.235.171.56 โ๏ธ Response : 70ms ๐บ๏ธ Location : ๐ณ๐ฑ Netherlands, North Holland, Amsterdam ๐ Timezone : Europe/Amsterdam ๐ผ ORG : Oracle Cloud Infrastructure (eu-amsterdam-1) ๐ฃ ISP : Oracle Corporation ss://MjAyMi1ibGFrZTMtY2hhY2hhMjAtcG9seTEzMDU6SFJxd29zZlhxbWxsY2hhNHcrSzNMeFlCOHZKK0wxcVJKd0JaZ1ZFMWtSWT0=@84.235.171.56:45819#๐ณ๐ฑ[openproxylist.com] ss-NL
๐๏ธ V2Ray VLESS Server ๐ IP Address : 216.167.27.162 โ๏ธ Response : 94ms ๐บ๏ธ Location : ๐บ๐ธ United States, California, Los Angeles ๐ Timezone : America/Los_Angeles ๐ผ ORG : NTT America, Inc ๐ฃ ISP : NTT America, Inc. vless://[email protected]:27694?security=reality&encryption=none&pbk=H3Dwj3Qq5ixvkqa_DoXGnwawad76HCTNh4mHMIU_01M&headerType=none&fp=chrome&type=tcp&flow=xtls-rprx-vision&sniโฆ
๐๏ธ V2Ray VLESS Server ๐ IP Address : 157.90.29.193 โ๏ธ Response : 100ms ๐บ๏ธ Location : ๐ฉ๐ช Germany, Bavaria, Nuremberg ๐ Timezone : Europe/Berlin ๐ผ ORG : Hetzner ๐ฃ ISP : Hetzner Online GmbH vless://[email protected]:443?encryption=none&security=tls&sni=ssl.fastly.com&fp=chrome&alpn=http/1.1&type=ws&host=Appxdn.global.ssl.fastly.net&path=/#๐ฉ๐ช[openproxylist.com] vless-DE
Showing the 12 most recent of 334 posts we hold for @v2nodes. 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
Citation-graph rank โ 1,122,251 of 1,628,927entries 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.
Mentions
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.
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 31 August 2026 โ this entry's latest reading, not the date you are reading this.
โV2Nodes ๐โ (@v2nodes), 18,928 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/v2nodes.
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.