Telegram RegisterThe public register of Telegram
Telegram profile photo for hitvpnbot✊

Bot

hitvpnbot✊

@hitvpnbot

Not marked by Telegram, checked 25 August 2026

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

1,970,964monthly users

-257,367 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among the largest entries.

Register entry

Telegram ID5226559104
TypeBot
Username@hitvpnbot
First recorded6 August 2026
Last confirmed live8 September 2026
Measurements held30
Confirmed unchanged1 time, most recently 8 September 2026
On Telegramt.me/hitvpnbot

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 72% 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 why it has no browse page of its own yet.

Growth

1,967,7032,228,3312,098,0176 August 2026 — 2,228,331 monthly users6 August 2026 — 2,203,530 monthly users6 August 2026 — 2,203,530 monthly users7 August 2026 — 2,178,093 monthly users8 August 2026 — 2,153,666 monthly users9 August 2026 — 2,124,708 monthly users10 August 2026 — 2,079,782 monthly users11 August 2026 — 2,059,691 monthly users12 August 2026 — 2,035,422 monthly users13 August 2026 — 2,022,917 monthly users15 August 2026 — 2,001,964 monthly users16 August 2026 — 1,992,336 monthly users17 August 2026 — 1,981,053 monthly users18 August 2026 — 1,967,703 monthly users19 August 2026 — 2,041,009 monthly users20 August 2026 — 2,057,128 monthly users21 August 2026 — 2,059,863 monthly users23 August 2026 — 2,056,104 monthly users25 August 2026 — 2,049,270 monthly users26 August 2026 — 2,051,055 monthly users27 August 2026 — 2,056,571 monthly users28 August 2026 — 2,054,623 monthly users29 August 2026 — 2,061,550 monthly users30 August 2026 — 2,061,829 monthly users31 August 2026 — 2,051,977 monthly users1 September 2026 — 2,042,845 monthly users2 September 2026 — 2,027,204 monthly users3 September 2026 — 2,020,410 monthly users5 September 2026 — 2,008,966 monthly users8 September 2026 — 1,970,964 monthly users1,970,9646 August 20268 September 2026
30 measurements spanning 34 days, net -257,367. 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 1,928,609–2,267,425 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 30
Measured (UTC)Monthly usersChange
8 Sept 2026, 16:211,970,964-38,002
5 Sept 2026, 08:212,008,966-11,444
3 Sept 2026, 09:062,020,410-6,794
2 Sept 2026, 01:542,027,204-15,641
1 Sept 2026, 03:352,042,845-9,132
31 Aug 2026, 02:242,051,977-9,852
30 Aug 2026, 05:542,061,829+279
29 Aug 2026, 02:252,061,550+6,927
28 Aug 2026, 04:042,054,623-1,948
27 Aug 2026, 02:152,056,571+5,516
26 Aug 2026, 01:272,051,055+1,785
25 Aug 2026, 02:242,049,270-6,834
23 Aug 2026, 14:082,056,104-3,759
21 Aug 2026, 22:062,059,863+2,735
20 Aug 2026, 19:042,057,128+16,119
19 Aug 2026, 18:262,041,009+73,306
18 Aug 2026, 21:541,967,703-13,350
17 Aug 2026, 23:131,981,053-11,283
16 Aug 2026, 21:331,992,336-9,628
15 Aug 2026, 10:262,001,964first 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

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 404 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

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

“hitvpnbot✊” (@hitvpnbot), 1,970,964 monthly users as measured 8 September 2026. Telegram Register, tgregister.com/channel/hitvpnbot.

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.