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

Bot

MORI VPN

@morivpnrobot

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

20,045monthly users

-3,575 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 ID7328868329
TypeBot
Username@morivpnrobot
First recorded15 August 2026
Last confirmed live29 August 2026
Measurements held11
Confirmed unchanged2 times, most recently 29 August 2026
On Telegramt.me/morivpnrobot

Growth

20,02223,62021,8216 August 2026 — 23,620 monthly users8 August 2026 — 23,584 monthly users10 August 2026 — 22,866 monthly users13 August 2026 — 22,009 monthly users15 August 2026 — 22,009 monthly users16 August 2026 — 21,606 monthly users18 August 2026 — 20,999 monthly users22 August 2026 — 20,803 monthly users23 August 2026 — 20,282 monthly users27 August 2026 — 20,022 monthly users28 August 2026 — 20,045 monthly users20,0456 August 202628 August 2026
11 measurements spanning 22 days, net -3,575. 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 19,482–24,160 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
28 Aug 2026, 22:0820,045+23
27 Aug 2026, 00:2220,022-260
23 Aug 2026, 16:2820,282-521
22 Aug 2026, 03:2720,803-196
18 Aug 2026, 16:5520,999-607
16 Aug 2026, 04:0721,606-403
15 Aug 2026, 20:4422,009no change
13 Aug 2026, 09:0822,009-857
10 Aug 2026, 05:2622,866-718
8 Aug 2026, 03:0723,584-36
6 Aug 2026, 19:5123,620first 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 7 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 28 August 2026 — this entry's latest reading, not the date you are reading this.

“MORI VPN” (@morivpnrobot), 20,045 monthly users as measured 28 August 2026. Telegram Register, tgregister.com/channel/morivpnrobot.

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.