Telegram RegisterThe public register of Telegram
Telegram profile photo for V2ray

Channel

V2ray

@server01012

On this record: Growth · Engagement · Posts · Posts edited after publishing · Citations · Cite this entry

24,180subscribers

-737 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001759808994
TypeChannel
Username@server01012
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live7 September 2026
Measurements held30
Confirmed unchanged1 time, most recently 7 September 2026
On Telegramt.me/server01012

Growth

24,18024,91724,548.56 August 2026 — 24,917 subscribers6 August 2026 — 24,917 subscribers6 August 2026 — 24,913 subscribers7 August 2026 — 24,885 subscribers8 August 2026 — 24,859 subscribers9 August 2026 — 24,829 subscribers10 August 2026 — 24,805 subscribers11 August 2026 — 24,781 subscribers12 August 2026 — 24,755 subscribers13 August 2026 — 24,734 subscribers14 August 2026 — 24,697 subscribers16 August 2026 — 24,639 subscribers17 August 2026 — 24,626 subscribers18 August 2026 — 24,602 subscribers19 August 2026 — 24,581 subscribers20 August 2026 — 24,547 subscribers21 August 2026 — 24,518 subscribers23 August 2026 — 24,491 subscribers24 August 2026 — 24,465 subscribers25 August 2026 — 24,452 subscribers26 August 2026 — 24,435 subscribers27 August 2026 — 24,417 subscribers29 August 2026 — 24,394 subscribers30 August 2026 — 24,364 subscribers30 August 2026 — 24,342 subscribers1 September 2026 — 24,326 subscribers2 September 2026 — 24,297 subscribers3 September 2026 — 24,283 subscribers4 September 2026 — 24,252 subscribers7 September 2026 — 24,180 subscribers6 August 20267 September 2026
30 measurements spanning 33 days, net -737. 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 24,069–25,028 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 30
Measured (UTC)SubscribersChange
7 Sept 2026, 18:5524,180-72
4 Sept 2026, 21:5924,252-31
3 Sept 2026, 09:1824,283-14
2 Sept 2026, 01:4224,297-29
1 Sept 2026, 02:3424,326-16
30 Aug 2026, 23:3624,342-22
30 Aug 2026, 00:4424,364-30
29 Aug 2026, 01:4324,394-23
27 Aug 2026, 22:2724,417-18
26 Aug 2026, 21:1324,435-17
25 Aug 2026, 21:3424,452-13
24 Aug 2026, 19:0424,465-26
23 Aug 2026, 03:1724,491-27
21 Aug 2026, 18:4824,518-29
20 Aug 2026, 15:1324,547-34
19 Aug 2026, 14:2524,581-21
18 Aug 2026, 17:1324,602-24
17 Aug 2026, 16:3724,626-13
16 Aug 2026, 14:3824,639-58
14 Aug 2026, 20:1724,697first reading

Engagement

75 posts held, back to 28 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 59 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
23.4%
avg views ÷ 24,180 subscribers
Avg views / post
5,670
42 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
45
of 75 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 31 August 2026
Posts held75 (28 July 202631 August 2026)
Views total238,000
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Sept 2026, 11:10 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

31 Aug 2026, 20:51 UTC≈2,220 viewsread 3 September 2026
File

🔐کانفیگ NPV Tunnel 📱📶تمامی نت‌ها 📣 @server01012

31 Aug 2026, 12:52 UTC≈2,570 viewsread 3 September 2026
File

🔐کانفیگ NPV Tunnel 📱📶تمامی نت‌ها 📣 @server01012

31 Aug 2026, 08:10 UTC≈2,810 viewsread 3 September 2026
File

🔐کانفیگ NPV Tunnel 📱📶تمامی نت‌ها 📣 @server01012

30 Aug 2026, 20:06 UTC≈3,120 viewsread 3 September 2026

سلام اختصاصی ها کسایی که سرور امریکا لازم داشتن اوکیش کردیم یراتون❤️

30 Aug 2026, 14:30 UTC≈3,370 viewsread 3 September 2026
File

🔐کانفیگ NPV Tunnel 📱📶تمامی نت‌ها 📣 @server01012

30 Aug 2026, 11:24 UTC≈3,340 viewsread 3 September 2026
File

🔐کانفیگ NPV Tunnel 📱📶تمامی نت‌ها 📣 @server01012

30 Aug 2026, 07:33 UTC≈3,350 viewsread 3 September 2026
File

🔐کانفیگ NPV Tunnel 📱📶تمامی نت‌ها 📣 @server01012

30 Aug 2026, 07:07 UTC≈3,330 viewsread 3 September 2026
File

🔐کانفیگ NPV Tunnel 📱📶تمامی نت‌ها 📣 @server01012

28 Aug 2026, 13:39 UTC≈4,270 viewsread 3 September 2026
File

🔐کانفیگ NPV Tunnel 📱📶تمامی نت‌ها 📣 @server01012

28 Aug 2026, 09:15 UTC≈4,390 viewsread 3 September 2026
File

🔐کانفیگ NPV Tunnel 📱📶تمامی نت‌ها 📣 @server01012

27 Aug 2026, 18:01 UTC≈4,620 viewsread 3 September 2026
File

🔐کانفیگ NPV Tunnel 📱📶تمامی نت‌ها 📣 @server01012

27 Aug 2026, 06:04 UTC≈4,900 viewsread 3 September 2026
File

🔐کانفیگ NPV Tunnel 📱📶تمامی نت‌ها 📣 @server01012

Showing the 12 most recent of 75 posts we hold for @server01012. 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.

Posts edited after publishing

@server01012 edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
20 August 2026
Most recent edit
20 August 2026

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 8 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.

Names

Channels on the register whose handles appear in this channel's posts.

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

“V2ray” (@server01012), 24,180 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/server01012.

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.