Telegram RegisterThe public register of Telegram

Channel

Project V Channel(Unofficial)

@v2ray

On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry

9,625subscribers

-32 since we began measuring on 5 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001335698158
TypeChannel
Username@v2ray
CreatedBetween 1 March 2018 and 6 August 2020— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/v2ray

Growth

9,6259,6579,6415 August 2026 — 9,657 subscribers6 August 2026 — 9,657 subscribers6 August 2026 — 9,655 subscribers9 August 2026 — 9,650 subscribers13 August 2026 — 9,625 subscribers5 August 202613 August 2026
5 measurements spanning 7 days, net -32. 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 9,620–9,662 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 00:389,625-25
9 Aug 2026, 19:119,650-5
6 Aug 2026, 21:189,655-2
6 Aug 2026, 02:509,657no change
5 Aug 2026, 23:009,657first reading

Engagement

20 posts held, back to 6 August 2020 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 15 pagesof 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 31 January 2022. An engagement rate over an empty window would be a number about nothing.

Recent posts

1 May 2021, 16:09 UTC≈1,650,000 viewsread 12 August 2026

v4.38.3 is released. (Stable Release) This release includes security functionality improvement for some users. Feature * FakeDNS: Added fakedns+others sniffer. Thanks yuhan6665 . * TLS: A SECURITY improvement that allow the remote peer's TLS certificate to be pinned to a known value. * Observatory: A component that measure the connectivity of selected outbounds. * Routing : leastPing balancing strategy is added. T…

19 Apr 2021, 06:10 UTC≈1,130,000 viewsread 12 August 2026

v4.38.0 is released. (Unstable Release) This release includes security functionality improvement for some users. Feature * FakeDNS: Added fakedns+others sniffer. Thanks yuhan6665 . * TLS: A SECURITY improvement that allow the remote peer's TLS certificate to be pinned to a known value. * Observatory: A component that measure the connectivity of selected outbounds. * Routing : leastPing balancing strategy is added.…

16 Mar 2021, 12:09 UTC≈868,000 viewsread 12 August 2026

v4.36.1 released. — Features * Transport: add gRPC / gun transport. This transport's connections can be relayed over Nginx and other supported CDNs, have an ALPN of h2 and a built-in mux. (#757 #783) -> Docs: Transport; gRPC transport * Proxy: add loopback proxy. This proxy allows you to send connections back to router to be routed again. It is a drop-in replacement for modified outbound address and dokodemo-door s…

8 Mar 2021, 08:09 UTC≈644,000 viewsread 12 August 2026

v4.35.1 Released https://github.com/v2fly/v2ray-core/releases/tag/v4.35.1 New Features * FakeDNS, an imaginary DNS server to preserve the domain information even if the software do not support proxy settings * HybridDomainMatcher: a faster and more memory-efficient routing rule matcher. * Outbound transport level proxySettings: comprehensive chained proxy support * Support Apple Silicon: add pre-built binary for Ap…

7 Jan 2021, 21:09 UTC≈752,000 viewsread 12 August 2026

v4.34.0 Released https://github.com/v2fly/v2ray-core/releases/tag/v4.34.0 Breaking Changes * Support for the legacy Shadowsocks protocol with stream ciphers has been removed (#566). If you are still using the unsecure stream ciphers, migrate to Shadowsocks AEAD (ChaCha20Poly1305 and AES-GCM) immediately. * Binaries of the following architectures are no longer a part of the release: s390x, ppc64, ppc64le, mips soft…

23 Nov 2020, 18:09 UTC≈377,000 viewsread 12 August 2026

New API Service: ReflectionService This service enables the clients to retrieve gRPC service's API list and signatures without prior access to its proto files. In this way, tools like grpcurl could easily interact with the API service: # h2c $ grpcurl -plaintext localhost:10086 list grpc.reflection.v1alpha.ServerReflection v2ray.core.app.proxyman.command.HandlerService v2ray.core.app.stats.command.StatsService # h…

23 Nov 2020, 18:09 UTC≈502,000 viewsread 12 August 2026

v4.33.0 Released https://github.com/v2fly/v2ray-core/releases/tag/v4.33.0 Breaking Changes * Remove XTLS Features * Add support for Debian package * API: Reflection Service Support * Update to IETF QUIC draft-32 (draft-29 is still supported) Chores * Transfer VSign and related project to V2Fly and share under the same * Update security policy with renewed GPG public key * Use Go 1.15.5 * Refine Code Notice T…

21 Nov 2020, 17:09 UTC≈418,000 viewsread 12 August 2026

感谢 @kidonng 的工作 现在你可以在 macOS 中使用 brew install v2ray 来安装 V2Ray

9 Nov 2020, 11:10 UTC≈277,000 viewsread 12 August 2026

#performance 最新的 v4.32.1 版本中，VLESS XTLS Direct Mode 引入了 ReadV 增强，减少一层内存 Copy，性能已与 VLESS 无加密裸奔持平（接近于纯流量转发），为传统 VMess WS TLS 方案的五倍、VLESS TCP TLS 的三倍（且测试机器 CPU 均有 AES 指令集，否则差距更大，如硬路由器上），强烈建议测试体验。这或许是当前性能最强的安全代理方式，但并不是上限，因为下一步优化方向是 V2Ray 框架本身的性能。 https://www.v2fly.org/config/protocols/vless.html www.v2fly.orgVLESS | V2Fly.orgProject V 是一个工具集合，它可以帮助你打造专属的基础通信网络

9 Nov 2020, 11:10 UTC≈242,000 viewsread 12 August 2026

v4.32.1 Released https://github.com/v2fly/v2ray-core/releases/tag/v4.32.1 Important improvement * VLESS XTLS Direct Mode ReadV Experiment It's strongly recommended to test this change, as it reaches the best performance of current V2Ray platform. Remember to use V2Ray v4.32.1+ on at least client side. For more information, please visit https://www.v2fly.org/config/protocols/vless.html#xtls-%E9%BB%91%E7%A7%91%E6%8…

Showing the 12 most recent of 20 posts we hold for @v2ray. 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 — 852,998 of 1,183,361entries 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.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

V2Fly - Notification and Updates, V2Ray the second new
@v2fly · 6,4031 post

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.

Mentions

Named by 3 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.

Lidocaine
@Lidocaine · 89,8501 postSearch Telegram Update
@SearchTelegramChannel · 281 postiran vasita |ایردراپ|
@signalandvasita · 391 post

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 13 August 2026 — this entry's latest reading, not the date you are reading this.

“Project V Channel(Unofficial)” (@v2ray), 9,625 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/v2ray.

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.