Channel
vpncity
@nvvpn_city2
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,531subscribers
-15 since we began measuring on 25 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001953787656 |
|---|---|
| Type | Channel |
| Username | @nvvpn_city2 |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 15 September 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/nvvpn_city2 |
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 15 September 2026 and assigned it the closest of 31 fixed categories, at 78% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 03:40 | 2,531 | +2 |
| 15 Sept 2026, 14:20 | 2,529 | no change |
| 13 Sept 2026, 23:41 | 2,529 | -8 |
| 10 Sept 2026, 02:00 | 2,537 | +5 |
| 4 Sept 2026, 14:56 | 2,532 | -4 |
| 1 Sept 2026, 10:28 | 2,536 | -7 |
| 29 Aug 2026, 02:12 | 2,543 | -6 |
| 26 Aug 2026, 09:11 | 2,549 | +3 |
| 25 Aug 2026, 20:01 | 2,546 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind 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.
@turboo_server · 29,613
Telegram ranks this channel #5 of 38 here — alongside 37 others — read 7 September 2026
@vpn_connects · 46,716
Telegram ranks this channel #13 of 39 here — alongside 38 others — read 25 August 2026
@Expreset · 27,614
Telegram ranks this channel #18 of 35 here — alongside 34 others — read 18 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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“vpncity” (@nvvpn_city2), 2,531 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/nvvpn_city2.
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.