Telegram RegisterThe public register of Telegram
Telegram profile photo for VPN: Xray+VNI Hosting bot

Bot

VPN: Xray+VNI Hosting bot

@VPNI_Hosting_bot

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

21,249monthly users

-2,141 since we began measuring on 7 August 2026

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

Register entry

Telegram ID6524523355
TypeBot
Username@VPNI_Hosting_bot
First recorded16 August 2026
Last confirmed live28 August 2026
Measurements held16
Confirmed unchanged1 time, most recently 28 August 2026
On Telegramt.me/VPNI_Hosting_bot

Growth

19,78023,39021,5857 August 2026 — 23,390 monthly users9 August 2026 — 22,429 monthly users11 August 2026 — 21,260 monthly users13 August 2026 — 20,477 monthly users14 August 2026 — 20,567 monthly users16 August 2026 — 20,328 monthly users16 August 2026 — 20,328 monthly users17 August 2026 — 20,145 monthly users18 August 2026 — 19,780 monthly users19 August 2026 — 20,031 monthly users21 August 2026 — 20,126 monthly users22 August 2026 — 20,251 monthly users24 August 2026 — 20,112 monthly users26 August 2026 — 20,898 monthly users27 August 2026 — 21,124 monthly users28 August 2026 — 21,249 monthly users21,2497 August 202628 August 2026
16 measurements spanning 21 days, net -2,141. 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,239–23,932 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
28 Aug 2026, 11:1221,249+125
27 Aug 2026, 08:0321,124+226
26 Aug 2026, 04:3720,898+786
24 Aug 2026, 06:1620,112-139
22 Aug 2026, 15:0620,251+125
21 Aug 2026, 06:4820,126+95
19 Aug 2026, 12:4520,031+251
18 Aug 2026, 16:1319,780-365
17 Aug 2026, 12:4320,145-183
16 Aug 2026, 17:4420,328no change
16 Aug 2026, 04:3420,328-239
14 Aug 2026, 16:3620,567+90
13 Aug 2026, 10:3820,477-783
11 Aug 2026, 08:3621,260-1,169
9 Aug 2026, 07:5122,429-961
7 Aug 2026, 03:0223,390first 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 6 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.

“VPN: Xray+VNI Hosting bot” (@VPNI_Hosting_bot), 21,249 monthly users as measured 28 August 2026. Telegram Register, tgregister.com/channel/VPNI_Hosting_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.