Telegram RegisterThe public register of Telegram
Telegram profile photo for Astra VPN

Bot

Astra VPN

@astra_net_bot

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

19,319monthly users

-5,032 since we began measuring on 7 October 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID8721447395
TypeBot
Username@astra_net_bot
First recorded7 October 2026
Last confirmed live11 November 2026
Measurements held18
Confirmed unchanged1 time, most recently 11 November 2026
On Telegramt.me/astra_net_bot

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 23 October 2026 and assigned it the closest of 31 fixed categories, at 83% 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 the other topics.

Growth

19,31924,73722,0287 October 2026 — 24,351 monthly users7 October 2026 — 24,351 monthly users12 October 2026 — 24,737 monthly users14 October 2026 — 23,923 monthly users15 October 2026 — 23,501 monthly users18 October 2026 — 23,671 monthly users20 October 2026 — 23,684 monthly users23 October 2026 — 23,651 monthly users25 October 2026 — 23,840 monthly users26 October 2026 — 22,740 monthly users28 October 2026 — 21,709 monthly users29 October 2026 — 21,158 monthly users31 October 2026 — 21,366 monthly users2 November 2026 — 21,122 monthly users4 November 2026 — 20,421 monthly users6 November 2026 — 19,909 monthly users9 November 2026 — 20,505 monthly users11 November 2026 — 19,319 monthly users7 October 202611 November 2026
18 measurements spanning 35 days, net -5,032. 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 18,506–25,550 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
11 Nov 2026, 09:1919,319-1,186
9 Nov 2026, 15:5920,505+596
6 Nov 2026, 01:1619,909-512
4 Nov 2026, 01:5020,421-701
2 Nov 2026, 00:1921,122-244
31 Oct 2026, 01:2821,366+208
29 Oct 2026, 00:3721,158-551
28 Oct 2026, 02:1621,709-1,031
26 Oct 2026, 01:2822,740-1,100
25 Oct 2026, 04:0023,840+189
23 Oct 2026, 02:0723,651-33
20 Oct 2026, 21:3023,684+13
18 Oct 2026, 01:4523,671+170
15 Oct 2026, 08:2923,501-422
14 Oct 2026, 05:0023,923-814
12 Oct 2026, 03:3624,737+386
7 Oct 2026, 17:4024,351no change
7 Oct 2026, 15:1724,351first 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.

Mentions

Named by 2 registered channels — 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.

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

“Astra VPN” (@astra_net_bot), 19,319 monthly users as measured 11 November 2026. Telegram Register, tgregister.com/channel/astra_net_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.