Telegram RegisterThe public register of Telegram
Telegram profile photo for Петрович VPN

Bot

Петрович VPN

@petrovich_vpn_bot

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

10,655monthly users

-1,085 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 ID7996354968
TypeBot
Username@petrovich_vpn_bot
First recorded21 August 2026
Last confirmed live30 August 2026
Measurements held14
Confirmed unchanged3 times, most recently 29 August 2026
On Telegramt.me/petrovich_vpn_bot

Growth

10,65511,74011,197.58 August 2026 — 11,740 monthly users10 August 2026 — 11,599 monthly users11 August 2026 — 11,430 monthly users13 August 2026 — 11,345 monthly users14 August 2026 — 11,338 monthly users16 August 2026 — 11,327 monthly users17 August 2026 — 11,185 monthly users19 August 2026 — 11,120 monthly users20 August 2026 — 11,099 monthly users21 August 2026 — 10,903 monthly users21 August 2026 — 10,903 monthly users22 August 2026 — 10,883 monthly users24 August 2026 — 10,813 monthly users27 August 2026 — 10,655 monthly users8 August 202627 August 2026
14 measurements spanning 19 days, net -1,085. 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,492–11,903 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
27 Aug 2026, 11:0410,655-158
24 Aug 2026, 08:3410,813-70
22 Aug 2026, 17:2610,883-20
21 Aug 2026, 21:2210,903no change
21 Aug 2026, 11:2410,903-196
20 Aug 2026, 12:2211,099-21
19 Aug 2026, 12:4511,120-65
17 Aug 2026, 13:3411,185-142
16 Aug 2026, 07:1811,327-11
14 Aug 2026, 16:3911,338-7
13 Aug 2026, 04:1711,345-85
11 Aug 2026, 04:2111,430-169
10 Aug 2026, 04:3511,599-141
8 Aug 2026, 05:0511,740first 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 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.

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

“Петрович VPN” (@petrovich_vpn_bot), 10,655 monthly users as measured 27 August 2026. Telegram Register, tgregister.com/channel/petrovich_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.