Channel
@v2fly
On this record: Growth · Engagement · Posts · Citations · Cite this entry
6,403subscribers
+1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001448681670 |
|---|---|
| Type | Channel |
| Username | @v2fly |
| Created | Between 1 April 2019 and 30 September 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/v2fly |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 15:53 | 6,403 | -2 |
| 9 Aug 2026, 12:31 | 6,405 | +3 |
| 6 Aug 2026, 03:20 | 6,402 | no change |
| 6 Aug 2026, 02:51 | 6,402 | first reading |
20 posts held, back to 27 October 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 9 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 18 May 2026. An engagement rate over an empty window would be a number about nothing.
v5.51.0 is released. (unstable version) New Features Google Docs Viewer Transport: Designed to bypass current near total censorship of internet experienced by Iranian users. A shout out to the developer at https://github.com/0xinf0/gdocs-tunnel that published the tunneling method that was used in this transport.
Signed Shelikhoo [aka Shell] 0x7791BDB0709ABD21
We have observed the report that looks like TLS protocol could be impacted by max non-advancing record discriminator, and based on the testing and deductions TLSMirror is not impacted by it. Also, TLSMirror is by design systemically not vulnerable to this kind of attack, and is more tolerant to different kinds of forwarding sites no matter what TLS stack was used by the forwarded site. https://github.com/net4people/b…
Signed Shelikhoo [aka Shell] 0x7791BDB0709ABD21
Done: https://github.com/v2fly/v2ray-core/releases/tag/v5.44.1
Signed Shelikhoo [aka Shell] 0x7791BDB0709ABD21
We have recently released a new version of v2ray with a security update for utls regarding to Chrome120 fingerprint. https://github.com/v2fly/v2ray-core/releases/tag/v5.44.0 There could be another security release tomorrow for golang tool chain update.
Signed Shelikhoo [aka Shell] 0x7791BDB0709ABD21
v5.41.0 is released. (unstable version) This is a maintenance release. This release includes an important fix for utls, update recommended for all users.
Signed Shelikhoo [aka Shell] 0x7791BDB0709ABD21
v5.40.0 is released. (unstable version) New Features Add transient storage lifecycle receiver framework (fix grpc transport goroutine leak)
Signed Shelikhoo [aka Shell] 0x7791BDB0709ABD21
v5.37.0 is released. (unstable version) New Features Add TLSMirror looks like TLS censorship resistant transport protocol as a developer preview transport Update TLS Mirror with TLS1.2 AEAD support, defer_instance_derived_write_time, transport_layer_padding, h2_do_not_wait_for_download_finish proxy dns with NOTIMP error This update includes important fix for developer preview protocol TLSMirror. 本更新含针对于开发者预览版协议 TLSMi…
Signed Shelikhoo [aka Shell] 0x7791BDB0709ABD21
TLSMirror: Looks like TLS Censorship Resistant Transport Protocol is Looking for Developer Feedback https://github.com/net4people/bbs/issues/496
Signed Shelikhoo [aka Shell] 0x7791BDB0709ABD21
v5.36.0 is released. (unstable version) New Features Add TLSMirror looks like TLS censorship resistant transport protocol as a developer preview transport proxy dns with NOTIMP error
Signed Shelikhoo [aka Shell] 0x7791BDB0709ABD21
v5.35.0 is released. (stable version) New Features fix false success from SOCKS server when Dispatch() fails HTTP inbound: Directly forward plain HTTP 1xx response header
Signed Shelikhoo [aka Shell] 0x7791BDB0709ABD21
v5.31.0 is released. (unstable version) This is a maintenance release contains a security update for utls.
Signed Shelikhoo [aka Shell] 0x7791BDB0709ABD21
v5.30.0 is released. (unstable version) New Features Add Dns Proxy Response TTL Control
Signed Shelikhoo [aka Shell] 0x7791BDB0709ABD21
Showing the 12 most recent of 20 posts we hold for @v2fly. 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 — 270,604 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 1 registered channel — 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.
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.
“V2Fly - Notification and Updates, V2Ray the second new” (@v2fly), 6,403 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/v2fly.
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.