Telegram RegisterThe public register of Telegram
Telegram profile photo for AkresVPN Logs

Channel

AkresVPN Logs

@AkresVPN

On this record: Growth · Engagement · Posts · Citations · Cite this entry

22subscribers

+1 since we began measuring on 12 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1004305403510
TypeChannel
Username@AkresVPN
CreatedBetween 1 June 2026 and 11 August 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live19 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 19 August 2026
On Telegramt.me/AkresVPN

Growth

212221.512 August 2026 — 21 subscribers12 August 2026 — 21 subscribers19 August 2026 — 22 subscribers12 August 202619 August 2026
3 measurements spanning 7 days, net +1. 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 21–22 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Aug 2026, 09:5222+1
12 Aug 2026, 22:1821no change
12 Aug 2026, 03:0121first reading

Engagement

20 posts held, back to 11 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
17.0%
avg views ÷ 22 subscribers
Avg views / post
3.8
20 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
20
of 20 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 12 August 2026
Posts held20 (11 August 202612 August 2026)
Views total75
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 03:01 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

12 Aug 2026, 03:01 UTC1 viewsread 12 August 2026

Конфигов: 19 Стран: 11 🇬🇧 Великобритания: 3 🇩🇪 Германия: 3 🇫🇷 Франция: 3 🇸🇬 Сингапур: 2 🇺🇸 США: 2 🇦🇹 Австрия: 1 🇳🇱 Нидерланды: 1 🇷🇺 Россия: 1 🇷🇴 Румыния: 1 🇫🇮 Финляндия: 1 🇸🇪 Швеция: 1 Хостеров: 9 AEZA GROUP LLC: 6 BL Networks: 4 365 Group LLC: 2 IONOS SE: 2 365 Group: 1 NetCrafters OU: 1 RapidSeedbox Ltd: 1 SPACECORE SOLUTION LTD: 1 UFO Hosting LLC: 1

12 Aug 2026, 02:01 UTC2 viewsread 12 August 2026

Конфигов: 24 Стран: 9 🇬🇧 Великобритания: 4 🇺🇸 США: 4 🇩🇪 Германия: 3 🇳🇱 Нидерланды: 3 🇷🇺 Россия: 3 🇫🇷 Франция: 3 🇸🇬 Сингапур: 2 🇷🇴 Румыния: 1 🇸🇪 Швеция: 1 Хостеров: 12 AEZA GROUP LLC: 6 BL Networks: 4 365 Group LLC: 3 365 Group: 2 IONOS SE: 2 Cloudflare, Inc.: 1 HOSTKEY B.V.: 1 JSC TIMEWEB: 1 LLC IT BASIS: 1 NetCrafters OU: 1 SPACECORE SOLUTION LTD: 1 UFO Hosting LLC: 1

12 Aug 2026, 01:01 UTC2 viewsread 12 August 2026

Конфигов: 21 Стран: 10 🇩🇪 Германия: 3 🇳🇱 Нидерланды: 3 🇷🇺 Россия: 3 🇺🇸 США: 3 🇬🇧 Великобритания: 2 🇸🇬 Сингапур: 2 🇫🇷 Франция: 2 🇦🇹 Австрия: 1 🇷🇴 Румыния: 1 🇸🇪 Швеция: 1 Хостеров: 13 BL Networks: 4 365 Group LLC: 3 AEZA GROUP LLC: 3 IONOS SE: 2 365 Group: 1 Cloudflare, Inc.: 1 HOSTKEY B.V.: 1 JSC TIMEWEB: 1 LLC IT BASIS: 1 NetCrafters OU: 1 RapidSeedbox Ltd: 1 SPACECORE SOLUTION LTD: 1 UFO Hosting LLC: 1

12 Aug 2026, 00:01 UTC2 viewsread 12 August 2026

Конфигов: 22 Стран: 11 🇳🇱 Нидерланды: 3 🇷🇺 Россия: 3 🇸🇬 Сингапур: 3 🇫🇷 Франция: 3 🇬🇧 Великобритания: 2 🇩🇪 Германия: 2 🇺🇸 США: 2 🇦🇹 Австрия: 1 🇷🇴 Румыния: 1 🇫🇮 Финляндия: 1 🇸🇪 Швеция: 1 Хостеров: 12 AEZA GROUP LLC: 5 BL Networks: 4 365 Group LLC: 3 IONOS SE: 2 365 Group: 1 HOSTKEY B.V.: 1 JSC TIMEWEB: 1 LLC IT BASIS: 1 NetCrafters OU: 1 RapidSeedbox Ltd: 1 SPACECORE SOLUTION LTD: 1 UFO Hosting LLC: 1

11 Aug 2026, 23:01 UTC3 viewsread 12 August 2026

Конфигов: 24 Стран: 9 🇬🇧 Великобритания: 4 🇷🇺 Россия: 4 🇩🇪 Германия: 3 🇳🇱 Нидерланды: 3 🇸🇬 Сингапур: 3 🇺🇸 США: 3 🇫🇷 Франция: 2 🇷🇴 Румыния: 1 🇸🇪 Швеция: 1 Хостеров: 12 AEZA GROUP LLC: 5 365 Group LLC: 4 BL Networks: 4 IONOS SE: 2 UFO Hosting LLC: 2 365 Group: 1 Cloudflare, Inc.: 1 HOSTKEY B.V.: 1 JSC TIMEWEB: 1 LLC IT BASIS: 1 NetCrafters OU: 1 SPACECORE SOLUTION LTD: 1

11 Aug 2026, 22:01 UTC3 viewsread 12 August 2026

Конфигов: 45 Стран: 15 🇩🇪 Германия: 11 🇳🇱 Нидерланды: 7 🇷🇺 Россия: 6 🇵🇱 Польша: 3 🇫🇮 Финляндия: 3 🇸🇪 Швеция: 3 🇬🇧 Великобритания: 2 🇺🇸 США: 2 🇫🇷 Франция: 2 🇦🇹 Австрия: 1 🇧🇬 Болгария: 1 🇮🇹 Италия: 1 🇷🇴 Румыния: 1 🇸🇬 Сингапур: 1 🇨🇭 Швейцария: 1 Хостеров: 25 AEZA GROUP LLC: 4 BL Networks: 4 GOLD IP L.L.C-FZ: 4 play2go.cloud - Cheap and reliable hosting: 4 365 Group LLC: 3 WAIcore Ltd: 3 Ace Data Centers II, LLC: 2 IONOS

11 Aug 2026, 21:01 UTC4 viewsread 12 August 2026

Конфигов: 46 Стран: 15 🇩🇪 Германия: 12 🇳🇱 Нидерланды: 6 🇷🇺 Россия: 6 🇵🇱 Польша: 3 🇺🇸 США: 3 🇸🇪 Швеция: 3 🇬🇧 Великобритания: 2 🇸🇬 Сингапур: 2 🇫🇮 Финляндия: 2 🇫🇷 Франция: 2 🇦🇹 Австрия: 1 🇧🇬 Болгария: 1 🇮🇹 Италия: 1 🇷🇴 Румыния: 1 🇨🇭 Швейцария: 1 Хостеров: 26 WAIcore Ltd: 5 BL Networks: 4 GOLD IP L.L.C-FZ: 4 AEZA GROUP LLC: 3 365 Group LLC: 2 Ace Data Centers II, LLC: 2 IONOS SE: 2 JSC TIMEWEB: 2 play2go.cloud - Cheap an

11 Aug 2026, 20:31 UTC4 viewsread 12 August 2026

Конфигов: 65 Стран: 15 🇩🇪 Германия: 14 🇳🇱 Нидерланды: 12 🇷🇺 Россия: 8 🇺🇸 США: 5 🇫🇮 Финляндия: 5 🇵🇱 Польша: 4 🇸🇪 Швеция: 4 🇫🇷 Франция: 3 🇦🇹 Австрия: 2 🇬🇧 Великобритания: 2 🇸🇬 Сингапур: 2 🇧🇬 Болгария: 1 🇮🇹 Италия: 1 🇷🇴 Румыния: 1 🇨🇭 Швейцария: 1 Хостеров: 38 GOLD IP L.L.C-FZ: 5 BL Networks: 4 SERV.HOST GROUP LTD: 4 AEZA GROUP LLC: 3 Kyonix Networks Limited: 3 play2go.cloud - Cheap and reliable hosting: 3 WAIcore Ltd: 3

11 Aug 2026, 20:01 UTC4 viewsread 12 August 2026

Конфигов: 49 Стран: 15 🇳🇱 Нидерланды: 9 🇩🇪 Германия: 8 🇷🇺 Россия: 6 🇵🇱 Польша: 4 🇺🇸 США: 4 🇫🇮 Финляндия: 4 🇫🇷 Франция: 3 🇸🇪 Швеция: 3 🇬🇧 Великобритания: 2 🇦🇹 Австрия: 1 🇧🇬 Болгария: 1 🇮🇹 Италия: 1 🇷🇴 Румыния: 1 🇸🇬 Сингапур: 1 🇨🇭 Швейцария: 1 Хостеров: 32 AEZA GROUP LLC: 4 BL Networks: 4 SERV.HOST GROUP LTD: 4 Kyonix Networks Limited: 3 Ace Data Centers II, LLC: 2 ETERNITY INTERNATIONAL LIMITED: 2 IONOS SE: 2 JSC TIME

11 Aug 2026, 19:01 UTC4 viewsread 12 August 2026

Конфигов: 73 Стран: 18 🇩🇪 Германия: 12 🇳🇱 Нидерланды: 12 🇷🇺 Россия: 7 🇵🇱 Польша: 6 🇺🇸 США: 6 🇫🇮 Финляндия: 6 🇫🇷 Франция: 5 🇸🇪 Швеция: 3 🇧🇾 Беларусь: 2 🇬🇧 Великобритания: 2 🇰🇿 Казахстан: 2 🇦🇪 ОАЭ: 2 🇸🇬 Сингапур: 2 🇹🇷 Турция: 2 🇧🇬 Болгария: 1 🇮🇹 Италия: 1 🇷🇴 Румыния: 1 🇨🇭 Швейцария: 1 Хостеров: 42 H2.NEXUS Frankfurt Network: 6 365 Group LLC: 4 AEZA GROUP LLC: 4 SERV.HOST GROUP LTD: 4 BL Networks: 3 H2NEXUS LTD: 3 JSC T

11 Aug 2026, 18:01 UTC4 viewsread 12 August 2026

Конфигов: 74 Стран: 19 🇳🇱 Нидерланды: 12 🇩🇪 Германия: 10 🇷🇺 Россия: 8 🇵🇱 Польша: 6 🇺🇸 США: 6 🇫🇮 Финляндия: 5 🇫🇷 Франция: 5 🇬🇧 Великобритания: 4 🇸🇪 Швеция: 3 🇧🇾 Беларусь: 2 🇰🇿 Казахстан: 2 🇦🇪 ОАЭ: 2 🇸🇬 Сингапур: 2 🇹🇷 Турция: 2 🇦🇹 Австрия: 1 🇧🇬 Болгария: 1 🇮🇹 Италия: 1 🇷🇴 Румыния: 1 🇨🇭 Швейцария: 1 Хостеров: 43 H2.NEXUS Frankfurt Network: 6 AEZA GROUP LLC: 5 BL Networks: 4 SERV.HOST GROUP LTD: 4 365 Group LLC: 3 3NT SO

11 Aug 2026, 17:29 UTC5 viewsread 12 August 2026

Конфигов: 71 Стран: 19 🇩🇪 Германия: 12 🇳🇱 Нидерланды: 11 🇷🇺 Россия: 8 🇵🇱 Польша: 5 🇺🇸 США: 5 🇫🇷 Франция: 5 🇫🇮 Финляндия: 4 🇬🇧 Великобритания: 3 🇸🇪 Швеция: 3 🇦🇹 Австрия: 2 🇧🇾 Беларусь: 2 🇰🇿 Казахстан: 2 🇦🇪 ОАЭ: 2 🇹🇷 Турция: 2 🇧🇬 Болгария: 1 🇮🇹 Италия: 1 🇷🇴 Румыния: 1 🇸🇬 Сингапур: 1 🇨🇭 Швейцария: 1 Хостеров: 41 H2.NEXUS Frankfurt Network: 6 AEZA GROUP LLC: 4 BL Networks: 4 SERV.HOST GROUP LTD: 4 365 Group LLC: 3 H2NEXU

Showing the 12 most recent of 20 posts we hold for @AkresVPN. 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 — 644,946 of 1,602,822entries 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.

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.

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

“AkresVPN Logs” (@AkresVPN), 22 subscribers as measured 19 August 2026. Telegram Register, tgregister.com/channel/AkresVPN.

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.