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

Bot

Sota VPN

@sota

Verified by Telegram2 usernames

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

567,267monthly users

+47,577 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 316,228–1,000,000.

Register entry

Telegram ID5932660642
TypeBot
Usernames@sota @sotavpnbot
First recorded7 August 2026
Last confirmed live6 November 2026
Measurements held109
Confirmed unchanged1 time, most recently 6 November 2026
On Telegramt.me/sota

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 69% 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 the other topics.

Growth

448,883632,009540,446567,2677 August 20266 November 2026
109 measurements spanning 91 days, net +47,577. 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 421,414–659,478 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 109
Measured (UTC)Monthly usersChange
6 Nov 2026, 12:06567,267+1,634
5 Nov 2026, 08:48565,633no change
4 Nov 2026, 22:29565,633-268
4 Nov 2026, 10:07565,901no change
4 Nov 2026, 01:31565,901+4,286
3 Nov 2026, 11:59561,615no change
2 Nov 2026, 23:36561,615-496
2 Nov 2026, 12:00562,111no change
2 Nov 2026, 01:20562,111-171
1 Nov 2026, 00:46562,282no change
31 Oct 2026, 14:17562,282+1,484
31 Oct 2026, 03:59560,798no change
30 Oct 2026, 14:06560,798+213
30 Oct 2026, 06:08560,585no change
29 Oct 2026, 16:51560,585+2,692
29 Oct 2026, 05:38557,893no change
28 Oct 2026, 14:46557,893+1,418
28 Oct 2026, 03:37556,475no change
27 Oct 2026, 13:15556,475-406
26 Oct 2026, 13:20556,881first 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 15 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 6 November 2026 — this entry's latest reading, not the date you are reading this.

“Sota VPN” (@sota), 567,267 monthly users as measured 6 November 2026. Telegram Register, tgregister.com/channel/sota.

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.