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 17 September 2026 and assigned it the closest of 31 fixed categories, at 67% 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 why it has no browse page of its own yet.
Growth
16 measurements spanning 44 days, net -60. 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 1,458–1,536 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
18 Sept 2026, 20:19
1,467
-2
14 Sept 2026, 15:56
1,469
-8
11 Sept 2026, 06:17
1,477
-9
6 Sept 2026, 13:55
1,486
-3
2 Sept 2026, 12:53
1,489
-7
30 Aug 2026, 20:36
1,496
-4
27 Aug 2026, 19:17
1,500
-2
25 Aug 2026, 04:33
1,502
-5
22 Aug 2026, 11:06
1,507
-5
19 Aug 2026, 00:46
1,512
-2
16 Aug 2026, 04:12
1,514
-5
12 Aug 2026, 17:45
1,519
-2
9 Aug 2026, 19:21
1,521
-5
6 Aug 2026, 23:55
1,526
-1
6 Aug 2026, 07:35
1,527
no change
6 Aug 2026, 05:50
1,527
first reading
Engagement
10 posts held, back to 1 July 2023 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 2 pages of 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 10 posts for this entry, the most recent from 25 November 2025. An engagement rate over an empty window would be a number about nothing.
Reaction mix
708 reactions across 9 posts, in 16 distinct kinds. The most used accounts for 14.5% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
103
14.5%
👍
98
13.8%
👏
88
12.4%
❤
87
12.3%
🥰
82
11.6%
🎉
73
10.3%
🤩
55
7.77%
😱
30
4.24%
🤮
28
3.95%
😨
22
3.11%
🤯
20
2.82%
❤🔥
13
1.84%
👎
3
0.424%
🤝
3
0.424%
🤗
2
0.282%
💯
1
0.141%
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 9 of the 10 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 708 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 1 July 2023 to 25 November 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
⚡️ Подключение снова работает!
Вчера из-за блокировки РКН перестал функционировать протокол VLESS. Нам пришлось изменить метод подключения, и теперь всё работает стабильно, как и раньше.
⚠️ Если у вас не работает наш сервис, то просто подключитесь к локации с названием WL в начале
‼️ VPN может временно не работать
Сейчас из-за массовых сбоев Cloudflare не работает пол интернета (в том числе и наш сервис)
Мы уже работает над восстановлением доступности нашего сервиса
Спасибо за понимание!🤝
⚠️⚡️ Перестал работать наш сервис?
Чтобы всё заработало, нажмите на кнопку «🔄 Обновить» в вашем клиенте.
Также помимо этого мы добавили 7+ новых локаций, которые тоже появятся после нажатия на кнопку «🔄Обновить»
‼️💱 Замена Финских серверов на Нидерланды
Мы заменяем 🇫🇮 финские серверы на новые 🇳🇱 нидерландские. Судя по нашим тестам, это позволит значительно повысить стабильность и скорость соединения для пользователей.
Обновление списка серверов произойдет в течение дня автоматически, вы можете принудительно обновить список нажав «обновить».
Финские серверы работают до конца текущих сессий, новые подключения уже недоступны…
📢🇷🇺 YouTube без рекламы и с высокой скоростью.
Специальный высокоскоростной сервер, предназначенный для ускорения работы любимых сайтов - в том числе и YouTube без рекламы.
🖥 ЛУЧШИЕ СЕРВЕРА НА РЫНКЕ
При выборе серверов для нашего сервиса мы потратили много времени и средств - всего за момент подбора мы купили более 50 различных серверов, чтобы выбрать лучшие.
На данный момент в сервисе доступны:
⚡️⚡️ВЫСОКОСКОРОСТНЫЕ (10гбит/с)
🇳🇱 Нидерланды
🇷🇺 Россия
Обычные сервера (1гбит/с)
🇰🇿 Казахстан
🇹🇷 Турция
🇺🇸 США
🇭🇰 Гонконг - подойдет для поездок в Китай
Мы планируем добавить и другие серв…
Showing the 10 most recent of 10 posts we hold for @nonruvpn. 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.
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 18 September 2026 — this
entry's latest reading, not the date you are reading this.
“nonruvpn - канал” (@nonruvpn), 1,467 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/nonruvpn.
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.