Telegram RegisterThe public register of Telegram
Telegram profile photo for V2Nodes ๐Ÿš€

Channel

V2Nodes ๐Ÿš€

@v2nodes

On this record: Topic ยท Growth ยท Engagement ยท Reactions ยท Posts ยท Citations ยท Cite this entry

18,526subscribers

-367 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
TypeChannel
Username@v2nodes
CreatedBetween 1 April 2023 and 31 October 2023 โ€” estimated from Telegramโ€™s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live26 September 2026
Measurements held34
Confirmed unchanged1 time, most recently 26 September 2026
On Telegramt.me/v2nodes

Topic

Technology โ€” a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channelโ€™s own recent posts on 10 September 2026 and assigned it the closest of 31 fixed categories, at 43% confidence. This is a modelโ€™s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured โ€” it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

18,52618,95518,740.57 August 2026 โ€” 18,893 subscribers7 August 2026 โ€” 18,893 subscribers8 August 2026 โ€” 18,897 subscribers9 August 2026 โ€” 18,904 subscribers10 August 2026 โ€” 18,910 subscribers11 August 2026 โ€” 18,922 subscribers12 August 2026 โ€” 18,932 subscribers14 August 2026 โ€” 18,937 subscribers15 August 2026 โ€” 18,950 subscribers17 August 2026 โ€” 18,955 subscribers18 August 2026 โ€” 18,940 subscribers19 August 2026 โ€” 18,943 subscribers20 August 2026 โ€” 18,929 subscribers21 August 2026 โ€” 18,932 subscribers22 August 2026 โ€” 18,933 subscribers24 August 2026 โ€” 18,922 subscribers25 August 2026 โ€” 18,918 subscribers26 August 2026 โ€” 18,916 subscribers27 August 2026 โ€” 18,920 subscribers28 August 2026 โ€” 18,919 subscribers29 August 2026 โ€” 18,934 subscribers30 August 2026 โ€” 18,926 subscribers31 August 2026 โ€” 18,928 subscribers1 September 2026 โ€” 18,931 subscribers2 September 2026 โ€” 18,932 subscribers3 September 2026 โ€” 18,860 subscribers5 September 2026 โ€” 18,727 subscribers9 September 2026 โ€” 18,691 subscribers11 September 2026 โ€” 18,677 subscribers13 September 2026 โ€” 18,673 subscribers15 September 2026 โ€” 18,669 subscribers17 September 2026 โ€” 18,655 subscribers19 September 2026 โ€” 18,612 subscribers26 September 2026 โ€” 18,526 subscribers7 August 202626 September 2026
34 measurements spanning 50 days, net -367. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between โ€” snapshots are recorded only when a count changes, so gaps mean โ€œno change observedโ€, never โ€œinterpolatedโ€. The vertical axis spans 18,462โ€“19,019 and does not start at zero.
Measurement log โ€” every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)SubscribersChange
26 Sept 2026, 16:1918,526-86
19 Sept 2026, 14:5818,612-43
17 Sept 2026, 06:2118,655-14
15 Sept 2026, 03:4018,669-4
13 Sept 2026, 09:5718,673-4
11 Sept 2026, 15:4018,677-14
9 Sept 2026, 02:5918,691-36
5 Sept 2026, 21:3818,727-133
3 Sept 2026, 18:1618,860-72
2 Sept 2026, 10:1318,932+1
1 Sept 2026, 12:1518,931+3
31 Aug 2026, 10:4818,928+2
30 Aug 2026, 11:2418,926-8
29 Aug 2026, 10:5718,934+15
28 Aug 2026, 10:0218,919-1
27 Aug 2026, 10:2318,920+4
26 Aug 2026, 11:5718,916-2
25 Aug 2026, 15:0518,918-4
24 Aug 2026, 13:3618,922-11
22 Aug 2026, 19:5218,933first reading

Engagement

353 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 54 pages of Telegramโ€™s post history, 20 posts per page.

ERR ยท 30 days
3.23%
avg views รท 18,526 subscribers
Avg views / post
598
40 posts measured
Reaction rate
0.158%
reactions รท views ยท ER floor
Posts in window
40
of 353 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 9 of 40 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days ยท latest post in window 3 September 2026
Posts held353 (5 August 2026 โ€“ 3 September 2026)
Views total23,918
Reactions total10
Forwards / commentsnot exposed by the public surface โ€” not measured, not estimated
Readings taken3 Sept 2026, 02:00 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

174 reactions across 92 posts, in 10 distinct kinds. The most used accounts for 47.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
โค8247.1%
๐Ÿค”3017.2%
๐Ÿ‘Ž2212.6%
๐Ÿ‘158.62%
๐Ÿฅฐ95.17%
๐Ÿ”ฅ74.02%
โคโ€๐Ÿ”ฅ42.30%
๐Ÿณ21.15%
๐Ÿ˜21.15%
๐Ÿ‘10.575%

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 100 of the 353 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 174 reactions in total: the kind of figure the paragraph above means by โ€œa reaction total printed elsewhere on the pageโ€.

Measured over the 353 most recent posts we hold, published 5 August 2026 to 3 September 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

3 Sept 2026, 00:09 UTC63 viewsread 3 September 2026

๐Ÿ†•๏ธ V2Ray VLESS Server ๐ŸŒ IP Address : 144.21.43.131 โœˆ๏ธ Response : 72ms ๐Ÿ—บ๏ธ 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

3 Sept 2026, 00:09 UTC64 viewsread 3 September 2026

๐Ÿ†•๏ธ V2Ray VLESS Server ๐ŸŒ IP Address : 23.170.40.21 โœˆ๏ธ Response : 100ms ๐Ÿ—บ๏ธ Location : ๐Ÿ‡บ๐Ÿ‡ธ United States, California, Los Angeles ๐Ÿ•˜ Timezone : America/Los_Angeles ๐Ÿ’ผ ORG : Cloud Source, Inc ๐Ÿฃ ISP : Cloud Source, Inc. vless://[email protected]:443?sni=dusebafke.mvp-rk.site&alpn=http/1.1&flow=xtls-rprx-vision-udp443&fp=chrome&security=tls#๐Ÿ‡บ๐Ÿ‡ธ[openproxylist.com] vless-US

3 Sept 2026, 00:09 UTC55 viewsread 3 September 2026

๐Ÿ†•๏ธ Trojan VPN Server ๐ŸŒ IP Address : 45.85.88.194 โœˆ๏ธ Response : 100ms ๐Ÿ—บ๏ธ Location : ๐Ÿ‡ฌ๐Ÿ‡ง United Kingdom, England, Newcastle upon Tyne ๐Ÿ•˜ Timezone : Europe/London ๐Ÿ’ผ ORG : FyfeWeb Ltd ๐Ÿฃ ISP : FyfeWeb Ltd trojan://[email protected]:2174?allowInsecure=0&alpn=http/1.1#๐Ÿ‡ฌ๐Ÿ‡ง[openproxylist.com] trojan-GB

2 Sept 2026, 12:09 UTC495 viewsread 3 September 2026

๐Ÿ†•๏ธ Outline VPN Server ๐ŸŒ IP Address : 129.146.56.236 โœˆ๏ธ Response : 91ms ๐Ÿ—บ๏ธ Location : ๐Ÿ‡บ๐Ÿ‡ธ United States, Arizona, Phoenix ๐Ÿ•˜ Timezone : America/Phoenix ๐Ÿ’ผ ORG : Oracle Cloud Infrastructure (us-phoenix-1) ๐Ÿฃ ISP : Oracle Corporation ss://MjAyMi1ibGFrZTMtY2hhY2hhMjAtcG9seTEzMDU6ZVBQQkp5dGhreUZJQ2dVMCtCbVNGU05KQ0xXSUgvbjhWSWVCdU0yMkRUVT0=@129.146.56.236:50356#๐Ÿ‡บ๐Ÿ‡ธ[openproxylist.com] ss-US

2 Sept 2026, 04:14 UTC684 viewsread 3 September 2026

๐Ÿ†•๏ธ V2Ray VLESS Server ๐ŸŒ IP Address : 65.109.187.54 โœˆ๏ธ Response : 101ms ๐Ÿ—บ๏ธ Location : ๐Ÿ‡ซ๐Ÿ‡ฎ Finland, Uusimaa, Helsinki ๐Ÿ•˜ Timezone : Europe/Helsinki ๐Ÿ’ผ ORG : Hetzner Online GmbH ๐Ÿฃ ISP : Hetzner Online GmbH vless://[email protected]:443?encryption=none&type=ws&host=c12.com&path=/&security=tls&fp=chrome&sni=ssl.fastly.com&alpn=h2#๐Ÿ‡ซ๐Ÿ‡ฎ[openproxylist.com] vless-FI

2 Sept 2026, 04:12 UTC566 viewsread 3 September 2026

๐Ÿ†•๏ธ V2Ray VLESS Server ๐ŸŒ IP Address : 49.12.244.56 โœˆ๏ธ Response : 93ms ๐Ÿ—บ๏ธ Location : ๐Ÿ‡ฉ๐Ÿ‡ช Germany, Saxony, Falkenstein ๐Ÿ•˜ Timezone : Europe/Berlin ๐Ÿ’ผ ORG : Hetzner Online GmbH ๐Ÿฃ ISP : Hetzner Online GmbH vless://[email protected]:101?security=reality&alpn=h3,h2&encryption=none&pbk=VxFkVk2SKEQrRnBnhzvl29UpHlS2i5t6Is__HGPmuRU&headerType=none&fp=chrome&type=tcp&sni=amp-api-edge.apps.apple.comโ€ฆ

2 Sept 2026, 04:10 UTC462 viewsread 3 September 2026

๐Ÿ†•๏ธ V2Ray VLESS Server ๐ŸŒ IP Address : 192.145.31.5 โœˆ๏ธ Response : 80ms ๐Ÿ—บ๏ธ Location : ๐Ÿ‡ณ๐Ÿ‡ฑ Netherlands, Provincie Flevoland, Dronten ๐Ÿ•˜ Timezone : Europe/Amsterdam ๐Ÿ’ผ ORG : Baykov Ilya Sergeevich ๐Ÿฃ ISP : Baykov Ilya Sergeevich vless://[email protected]:8443?fp=chrome&security=tls#๐Ÿ‡ณ๐Ÿ‡ฑ[openproxylist.com] vless-NL

2 Sept 2026, 00:09 UTC528 viewsread 3 September 2026

๐Ÿ†•๏ธ V2Ray VLESS Server ๐ŸŒ IP Address : 158.247.123.215 โœˆ๏ธ Response : 100ms ๐Ÿ—บ๏ธ Location : ๐Ÿ‡จ๐Ÿ‡ด Colombia, Bogota D.C., Bogotรก ๐Ÿ•˜ Timezone : America/Bogota ๐Ÿ’ผ ORG : Oracle Cloud Infrastructure (sa-bogota-1) ๐Ÿฃ ISP : Oracle Corporation vless://[email protected]:62145?#๐Ÿ‡จ๐Ÿ‡ด[openproxylist.com] vless-CO

1 Sept 2026, 20:11 UTC628 viewsread 3 September 2026

๐Ÿ†•๏ธ V2Ray VLESS Server ๐ŸŒ IP Address : 72.56.75.54 โœˆ๏ธ Response : 96ms ๐Ÿ—บ๏ธ Location : ๐Ÿ‡ณ๐Ÿ‡ฑ The Netherlands, North Holland, Amsterdam ๐Ÿ•˜ Timezone : Europe/Amsterdam ๐Ÿ’ผ ORG : Timeweb, LLP ๐Ÿฃ ISP : Timeweb, LLP vless://[email protected]:443?security=reality&encryption=none&pbk=iTCQz0n0AolvGxU2ZASJIsSVoKOR9PAFbnZVQDnSnF8&host=--v2rayNplus--v2rayNplus--v2rayNplus--&headerType=none&fp=chrome&spโ€ฆ

1 Sept 2026, 12:14 UTC760 views1 reactionsread 3 September 2026

๐Ÿ†•๏ธ V2Ray VLESS Server ๐ŸŒ IP Address : 65.109.187.51 โœˆ๏ธ Response : 101ms ๐Ÿ—บ๏ธ Location : ๐Ÿ‡ซ๐Ÿ‡ฎ Finland, Uusimaa, Helsinki ๐Ÿ•˜ Timezone : Europe/Helsinki ๐Ÿ’ผ ORG : Hetzner Online GmbH ๐Ÿฃ ISP : Hetzner Online GmbH vless://[email protected]:5001?encryption=none&flow=xtls-rprx-vision&security=reality&sni=fi.aeternavpn.space&fp=qq&pbk=HNjZe5pYUhcuE8sASYVVrVSMW_jFfekgLnrnO4xXIyQ&sid=a1b2c3d4&type=tcp&hโ€ฆ

โค1

1 Sept 2026, 04:11 UTC819 views1 reactionsread 3 September 2026

๐Ÿ†•๏ธ V2Ray VLESS Server ๐ŸŒ IP Address : 5.83.129.124 โœˆ๏ธ Response : 100ms ๐Ÿ—บ๏ธ Location : ๐Ÿ‡ฉ๐Ÿ‡ช Germany, Hesse, Frankfurt am Main ๐Ÿ•˜ Timezone : Europe/Berlin ๐Ÿ’ผ ORG : TakeHost.Biz ๐Ÿฃ ISP : TAKEHOST OU vless://[email protected]:443?sni=50gport3.potatosubge20.org&alpn=http/1.1&flow=xtls-rprx-vision-udp443&fp=firefox&security=tls#๐Ÿ‡ฉ๐Ÿ‡ช[openproxylist.com] vless-DE

โค1

1 Sept 2026, 04:10 UTC688 viewsread 3 September 2026

๐Ÿ†•๏ธ Trojan VPN Server ๐ŸŒ IP Address : 112.120.123.8 โœˆ๏ธ Response : 23ms ๐Ÿ—บ๏ธ Location : ๐Ÿ‡ญ๐Ÿ‡ฐ Hong Kong, Central and Western, Central ๐Ÿ•˜ Timezone : Asia/Hong_Kong ๐Ÿ’ผ ORG : Hong Kong Telecommunications (HKT) Limited ๐Ÿฃ ISP : Hong Kong Telecommunications (HKT) Limited Mass Internet trojan://[email protected]:50222?allowInsecure=1&sni=taobao.com#๐Ÿ‡ญ๐Ÿ‡ฐ[openproxylist.com] trojan-HK

Showing the 12 most recent of 353 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.

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 26 September 2026 โ€” this entry's latest reading, not the date you are reading this.

โ€œV2Nodes ๐Ÿš€โ€ (@v2nodes), 18,526 subscribers as measured 26 September 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.