Channel
@nn_prox
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Citations · Cite this entry
76,308subscribers
+12,156 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001232837377 |
|---|---|
| Type | Channel |
| Username | @nn_prox |
| Description | NoNameVPN: @nnvpn_iobot Качественно. Бюджетно. Стабильно. |
| Created | 23 December 2018 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 33 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/nn_prox |
Other / unclassifiable — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 11:16 | 76,308 | +929 |
| 15 Sept 2026, 07:19 | 75,379 | +455 |
| 13 Sept 2026, 15:59 | 74,924 | +539 |
| 12 Sept 2026, 00:21 | 74,385 | +1,063 |
| 9 Sept 2026, 12:56 | 73,322 | +1,261 |
| 6 Sept 2026, 05:42 | 72,061 | +663 |
| 4 Sept 2026, 02:57 | 71,398 | +376 |
| 2 Sept 2026, 16:55 | 71,022 | +248 |
| 1 Sept 2026, 18:35 | 70,774 | +284 |
| 31 Aug 2026, 20:24 | 70,490 | +203 |
| 30 Aug 2026, 20:44 | 70,287 | +229 |
| 29 Aug 2026, 18:55 | 70,058 | +173 |
| 28 Aug 2026, 22:07 | 69,885 | +300 |
| 27 Aug 2026, 20:24 | 69,585 | +109 |
| 26 Aug 2026, 23:23 | 69,476 | +187 |
| 26 Aug 2026, 02:44 | 69,289 | +198 |
| 25 Aug 2026, 06:11 | 69,091 | +103 |
| 24 Aug 2026, 08:47 | 68,988 | -185 |
| 22 Aug 2026, 17:08 | 69,173 | +99 |
| 21 Aug 2026, 07:15 | 69,074 | first reading |
5 posts held, back to 23 December 2018 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 98 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 21 September 2026 |
|---|---|
| Posts held | 5 (23 December 2018 – 21 September 2026) |
| Views total | 77,300 |
| Reactions total | 431 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 23 Sept 2026, 01:45 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.
Lifetime counters from Telegram’s own channel header, read 23 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
6,128 reactions across 4 posts, in 3 distinct kinds. The most used accounts for 58.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5235777833489410617 | 3,561 | 58.1% | |
| 👍 | 1,558 | 25.4% | |
| custom 5255846751079779856 | 1,009 | 16.5% |
Custom emoji. 2 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 4 of the 5 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 6,128 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 5 most recent posts we hold, published 23 December 2018 to 21 September 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @nn_prox. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 5 most recent posts we hold for this entry, published 23 December 2018 to 21 September 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Масштабное обновление Proxy! Обновили конфигурации и добавили больше серверов, чтобы связь стала ещё стабильнее. Для тех, кто регулярно пользуется нашим VPN, подготовили большой бонус. При этом сохранили локацию, доступную абсолютно всем. Подробности — в нашем боте.
👍300custom 523577783348941061770custom 525584675107977985661
➡️ Блокируют интернет? Хотим напомнить, что у нас есть быстрый и стабильный VPN с безлимитным трафиком по одной из самых выгодных цен — от 3 ₽ в сутки. А ещё вы можете пользоваться им до 30 дней бесплатно! 🚀 Попробуй — @nnm_ibot
custom 52357778334894106171,120👍634custom 5255846751079779856179
❕ В связи с масштабными блокировками Telegram мы перенесли ключи от Proxy в нашего бота. Актуальные Proxy (и бесплатный) можно получить здесь: ➡️ @nnm_ibot
custom 52357778334894106171,620custom 5255846751079779856617👍269
Подпишитесь на этот канал, чтобы у вас всегда был рабочий Proxy для Telegram и вы всегда оставались на связи. Здесь мы будем публиковать только актуальные рабочие и резервные Proxy. Можете делиться каналом с друзьями — это абсолютно бесплатно.
custom 5235777833489410617751👍355custom 5255846751079779856152
Channel created
Showing the 5 most recent of 5 posts we hold for @nn_prox. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
@nn_prox edited 2 posts 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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“FreeAccess” (@nn_prox), 76,308 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/nn_prox.
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.