Telegram RegisterThe public register of Telegram
Telegram profile photo for Магнит VPN

Bot

Магнит VPN

@magnit_vpn_bot

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

21,132monthly users

-1,542 since we began measuring on 8 August 2026

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

Register entry

Telegram ID7661209136
TypeBot
Username@magnit_vpn_bot
First recorded15 August 2026
Last confirmed live18 August 2026
Measurements held10
Confirmed unchanged1 time, most recently 18 August 2026
On Telegramt.me/magnit_vpn_bot

Growth

21,12022,84421,9828 August 2026 — 22,674 monthly users9 August 2026 — 22,427 monthly users10 August 2026 — 22,716 monthly users11 August 2026 — 22,844 monthly users12 August 2026 — 22,838 monthly users15 August 2026 — 22,398 monthly users15 August 2026 — 22,398 monthly users16 August 2026 — 21,632 monthly users17 August 2026 — 21,120 monthly users18 August 2026 — 21,132 monthly users21,1328 August 202618 August 2026
10 measurements spanning 11 days, net -1,542. 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 20,861–23,103 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
18 Aug 2026, 19:3621,132+12
17 Aug 2026, 22:5621,120-512
16 Aug 2026, 20:5621,632-766
15 Aug 2026, 20:1522,398no change
15 Aug 2026, 11:3422,398-440
12 Aug 2026, 20:3322,838-6
11 Aug 2026, 19:1822,844+128
10 Aug 2026, 17:3822,716+289
9 Aug 2026, 17:2122,427-247
8 Aug 2026, 01:3422,674first 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

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

“Магнит VPN” (@magnit_vpn_bot), 21,132 monthly users as measured 18 August 2026. Telegram Register, tgregister.com/channel/magnit_vpn_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.