Telegram RegisterThe public register of Telegram
Telegram profile photo for V2Fly - Notification and Updates, V2Ray the second new

Channel

V2Fly - Notification and Updates, V2Ray the second new

@v2fly

On this record: Topic · Growth · Engagement · Posts · Polls · Citations · Telegram's recommendations · Cite this entry

6,290subscribers

-112 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001448681670
TypeChannel
Username@v2fly
CreatedBetween 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live10 November 2026
Measurements held24
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/v2fly

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 12 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 the other topics.

Growth

6,2906,4056,347.56 August 2026 — 6,402 subscribers6 August 2026 — 6,402 subscribers9 August 2026 — 6,405 subscribers12 August 2026 — 6,403 subscribers16 August 2026 — 6,391 subscribers23 August 2026 — 6,390 subscribers26 August 2026 — 6,388 subscribers1 September 2026 — 6,384 subscribers4 September 2026 — 6,379 subscribers10 September 2026 — 6,370 subscribers14 September 2026 — 6,359 subscribers18 September 2026 — 6,357 subscribers27 September 2026 — 6,338 subscribers5 October 2026 — 6,337 subscribers12 October 2026 — 6,325 subscribers16 October 2026 — 6,321 subscribers19 October 2026 — 6,322 subscribers22 October 2026 — 6,315 subscribers25 October 2026 — 6,313 subscribers28 October 2026 — 6,307 subscribers31 October 2026 — 6,303 subscribers3 November 2026 — 6,295 subscribers6 November 2026 — 6,297 subscribers10 November 2026 — 6,290 subscribers6 August 202610 November 2026
24 measurements spanning 96 days, net -112. 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 6,273–6,422 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 24
Measured (UTC)SubscribersChange
10 Nov 2026, 13:086,290-7
6 Nov 2026, 20:296,297+2
3 Nov 2026, 13:046,295-8
31 Oct 2026, 22:056,303-4
28 Oct 2026, 16:076,307-6
25 Oct 2026, 17:406,313-2
22 Oct 2026, 15:196,315-7
19 Oct 2026, 07:216,322+1
16 Oct 2026, 01:406,321-4
12 Oct 2026, 15:566,325-12
5 Oct 2026, 15:566,337-1
27 Sept 2026, 21:166,338-19
18 Sept 2026, 17:566,357-2
14 Sept 2026, 03:016,359-11
10 Sept 2026, 01:376,370-9
4 Sept 2026, 19:426,379-5
1 Sept 2026, 08:146,384-4
26 Aug 2026, 01:236,388-2
23 Aug 2026, 04:136,390-1
16 Aug 2026, 16:366,391first reading

Engagement

25 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 14 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
18.7%
avg views ÷ 6,290 subscribers
Avg views / post
1,180
3 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
3
of 25 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 1 November 2026
Posts held25 (27 October 2024 – 1 November 2026)
Views total3,535
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Nov 2026, 13:58 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.

Recent posts

Telegram’s own ‘edited’ marker: 0 of 3 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

1 Nov 2026, 13:42 UTC850 viewsread 6 November 2026

A machine generated maintenance release for V2Ray has been released to disable mptcp by default for 8 mid version releases and receive dependencies updates: https://github.com/v2fly/v2ray-core/releases/tag/v5.56.0 DO NOT delay or defer installation of kernel updates or fixes, as this compensation is only enabled for a limited time and cannot address the root cause of the problem.

Signed Shelikhoo [aka Shell] 0x7791BDB0709ABD21

1 Nov 2026, 09:36 UTC935 viewsread 6 November 2026
Poll

Will it be necessary to generate a release with mptcp disabled by default? 需要更新一版mptcp默认关闭的V2么?

  1. Yes是69%
  2. no 否35%

The shares total 104%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

Signed Shelikhoo [aka Shell] 0x7791BDB0709ABD21

20 Oct 2026, 19:02 UTC≈1,750 viewsread 6 November 2026

A machine generated maintenance release for V2Ray have been released to receive dependencies security updates: https://github.com/v2fly/v2ray-core/releases/tag/v5.55.0

Signed Shelikhoo [aka Shell] 0x7791BDB0709ABD21

22 Sept 2026, 09:39 UTC≈5,420 viewsread 6 November 2026

v5.54.2 is released. (unstable version) This update fixes an issue with quic transport where it sends V2Ray specific handshake parameters that differs from quic-go defaults. Thanks Jackson Sippe, et al. for reporting this issue. This update includes a change that requires a protocol update of QUIC transport. Please update the server first to allow connections from both older and latest clients with a transition grace…

Signed Shelikhoo [aka Shell] 0x7791BDB0709ABD21

21 Sept 2026, 21:29 UTC≈3,590 viewsread 6 November 2026

v5.54.1 is released. (unstable version) This update fixes an issue with quic transport where it sends V2Ray specific handshake parameters that differs from quic-go defaults. Thanks Jackson Sippe, et al. for reporting this issue. ⚠️ Important Message ⚠️ This update includes security fix recommended for QUIC transport. ⚠️ 重要消息 ⚠️ 本更新含适用于 QUIC transport 的安全更新。

Signed Shelikhoo [aka Shell] 0x7791BDB0709ABD21

18 May 2026, 00:29 UTC≈6,230 viewsread 6 November 2026

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

16 Feb 2026, 11:32 UTC≈7,900 viewsread 6 November 2026

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

15 Jan 2026, 21:24 UTC≈7,280 viewsread 6 November 2026

Done: https://github.com/v2fly/v2ray-core/releases/tag/v5.44.1

Signed Shelikhoo [aka Shell] 0x7791BDB0709ABD21

14 Jan 2026, 17:55 UTC≈6,030 viewsread 6 November 2026

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

15 Oct 2025, 13:11 UTC≈7,160 viewsread 6 November 2026

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

3 Oct 2025, 18:54 UTC≈6,770 viewsread 6 November 2026

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

5 Jul 2025, 14:38 UTC≈8,610 viewsread 6 November 2026

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

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

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

1 Nov 2026, 09:36 UTCFinal Results89 voters

Will it be necessary to generate a release with mptcp disabled by default? 需要更新一版mptcp默认关闭的V2么?

  1. Yes是69%
  2. no 否35%

The shares total 104%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 25 most recent posts we hold, published 27 October 2024 to 1 November 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Forward network

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.

Mentions

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Github_2dust
@github_2dust · 92,921
Telegram ranks this channel #6 of 71 here — alongside 70 others — read 17 August 2026
Shadowrocket News
@ShadowrocketNews · 47,300
Telegram ranks this channel #9 of 60 here — alongside 59 others — read 27 August 2026
Project X Channel
@projectXtls · 30,549
Telegram ranks this channel #16 of 58 here — alongside 57 others — read 8 September 2026

This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“V2Fly - Notification and Updates, V2Ray the second new” (@v2fly), 6,290 subscribers as measured 10 November 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.