Bot

nVPN bot

@nackevpn_bot

On this record: Growth · Engagement · Cite this entry

11,489monthly users

+464 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	7444979213
Type	Bot
Username	@nackevpn_bot
First recorded	21 August 2026
Last confirmed live	30 August 2026
Measurements held	8
Confirmed unchanged	2 times, most recently 30 August 2026
On Telegram	t.me/nackevpn_bot

Growth

8 measurements spanning 22 days, net +464. 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 10,949–11,607 and does not start at zero.

Measurement log — every monthly users count we have recorded
Measured (UTC)	Monthly users	Change
29 Aug 2026, 05:12	11,489	+36
25 Aug 2026, 06:45	11,453	-78
21 Aug 2026, 17:04	11,531	no change
21 Aug 2026, 11:17	11,531	+280
18 Aug 2026, 12:03	11,251	+118
14 Aug 2026, 13:36	11,133	-71
11 Aug 2026, 10:59	11,204	+179
6 Aug 2026, 22:03	11,025	first reading

Engagement

No post feed to measure. Telegram publishes a readable post stream for channels, not for bots, so views, reactions and engagement rates do not exist for this entry — they are not missing, pending or withheld. The register records what this handle is and what it resolves to.

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

“nVPN bot” (@nackevpn_bot), 11,489 monthly users as measured 29 August 2026. Telegram Register, tgregister.com/channel/nackevpn_bot.

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.