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

Bot

Midas VPN

@midas_vpn_bot

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

73,014monthly users

+12,857 since we began measuring on 7 August 2026

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

Register entry

Telegram ID8528480105
TypeBot
Username@midas_vpn_bot
First recorded11 August 2026
Last confirmed live14 November 2026
Measurements held53
Confirmed unchanged1 time, most recently 14 November 2026
On Telegramt.me/midas_vpn_bot

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 9 September 2026 and assigned it the closest of 31 fixed categories, at 79% 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

57,78373,01465,398.57 August 2026 — 60,157 monthly users8 August 2026 — 59,590 monthly users11 August 2026 — 60,214 monthly users11 August 2026 — 60,214 monthly users12 August 2026 — 60,271 monthly users13 August 2026 — 60,326 monthly users15 August 2026 — 59,468 monthly users17 August 2026 — 65,074 monthly users18 August 2026 — 65,013 monthly users19 August 2026 — 64,728 monthly users21 August 2026 — 64,809 monthly users23 August 2026 — 65,088 monthly users24 August 2026 — 65,165 monthly users25 August 2026 — 61,270 monthly users26 August 2026 — 61,225 monthly users29 August 2026 — 60,630 monthly users30 August 2026 — 61,324 monthly users1 September 2026 — 61,178 monthly users2 September 2026 — 61,405 monthly users3 September 2026 — 61,787 monthly users5 September 2026 — 62,167 monthly users8 September 2026 — 63,200 monthly users11 September 2026 — 65,336 monthly users13 September 2026 — 67,910 monthly users14 September 2026 — 67,911 monthly users16 September 2026 — 68,089 monthly users19 September 2026 — 63,936 monthly users26 September 2026 — 64,147 monthly users4 October 2026 — 64,417 monthly users9 October 2026 — 58,508 monthly users13 October 2026 — 64,269 monthly users14 October 2026 — 61,868 monthly users15 October 2026 — 64,999 monthly users17 October 2026 — 64,323 monthly users18 October 2026 — 64,264 monthly users19 October 2026 — 57,783 monthly users20 October 2026 — 64,282 monthly users22 October 2026 — 69,044 monthly users24 October 2026 — 66,287 monthly users26 October 2026 — 65,336 monthly users28 October 2026 — 65,076 monthly users29 October 2026 — 64,912 monthly users30 October 2026 — 65,076 monthly users31 October 2026 — 68,511 monthly users1 November 2026 — 68,411 monthly users3 November 2026 — 68,352 monthly users4 November 2026 — 66,109 monthly users6 November 2026 — 72,052 monthly users7 November 2026 — 71,562 monthly users8 November 2026 — 71,660 monthly users10 November 2026 — 71,224 monthly users11 November 2026 — 72,835 monthly users14 November 2026 — 73,014 monthly users7 August 202614 November 2026
53 measurements spanning 99 days, net +12,857. 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 55,498–75,299 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 53
Measured (UTC)Monthly usersChange
14 Nov 2026, 20:4973,014+179
11 Nov 2026, 23:0072,835+1,611
10 Nov 2026, 02:4671,224-436
8 Nov 2026, 15:0571,660+98
7 Nov 2026, 10:4071,562-490
6 Nov 2026, 08:5672,052+5,943
4 Nov 2026, 08:1766,109-2,243
3 Nov 2026, 09:3668,352-59
1 Nov 2026, 03:4868,411-100
31 Oct 2026, 04:1768,511+3,435
30 Oct 2026, 06:0865,076+164
29 Oct 2026, 06:4864,912-164
28 Oct 2026, 02:4865,076-260
26 Oct 2026, 03:3765,336-951
24 Oct 2026, 02:2766,287-2,757
22 Oct 2026, 23:3969,044+4,762
20 Oct 2026, 17:0964,282+6,499
19 Oct 2026, 15:5957,783-6,481
18 Oct 2026, 15:2964,264-59
17 Oct 2026, 13:1464,323first 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 4 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 14 November 2026 — this entry's latest reading, not the date you are reading this.

“Midas VPN” (@midas_vpn_bot), 73,014 monthly users as measured 14 November 2026. Telegram Register, tgregister.com/channel/midas_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.