Telegram RegisterThe public register of Telegram
Telegram profile photo for Fish VPN BOT

Bot

Fish VPN BOT

@fish_vpn_bot

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

29,286monthly users

+7,874 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 ID8046707750
TypeBot
Username@fish_vpn_bot
First recorded16 August 2026
Last confirmed live16 November 2026
Measurements held50
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/fish_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 10 September 2026 and assigned it the closest of 31 fixed categories, at 93% 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

21,04929,28625,167.57 August 2026 — 21,412 monthly users8 August 2026 — 21,357 monthly users10 August 2026 — 21,211 monthly users12 August 2026 — 21,231 monthly users13 August 2026 — 21,216 monthly users16 August 2026 — 21,216 monthly users16 August 2026 — 21,318 monthly users18 August 2026 — 21,241 monthly users19 August 2026 — 21,237 monthly users20 August 2026 — 21,258 monthly users22 August 2026 — 21,283 monthly users24 August 2026 — 21,110 monthly users26 August 2026 — 21,049 monthly users28 August 2026 — 21,060 monthly users29 August 2026 — 21,070 monthly users31 August 2026 — 21,783 monthly users1 September 2026 — 21,735 monthly users2 September 2026 — 22,025 monthly users3 September 2026 — 22,481 monthly users5 September 2026 — 22,757 monthly users8 September 2026 — 23,395 monthly users11 September 2026 — 23,795 monthly users13 September 2026 — 24,048 monthly users14 September 2026 — 24,136 monthly users16 September 2026 — 24,200 monthly users18 September 2026 — 24,224 monthly users25 September 2026 — 24,888 monthly users3 October 2026 — 24,962 monthly users8 October 2026 — 24,526 monthly users12 October 2026 — 24,270 monthly users14 October 2026 — 23,864 monthly users16 October 2026 — 24,275 monthly users17 October 2026 — 24,295 monthly users20 October 2026 — 24,237 monthly users21 October 2026 — 24,180 monthly users22 October 2026 — 24,127 monthly users23 October 2026 — 24,170 monthly users24 October 2026 — 24,104 monthly users26 October 2026 — 24,088 monthly users28 October 2026 — 23,823 monthly users30 October 2026 — 23,791 monthly users1 November 2026 — 23,727 monthly users2 November 2026 — 23,705 monthly users4 November 2026 — 24,844 monthly users5 November 2026 — 24,847 monthly users7 November 2026 — 26,608 monthly users8 November 2026 — 27,391 monthly users10 November 2026 — 27,856 monthly users12 November 2026 — 28,564 monthly users16 November 2026 — 29,286 monthly users7 August 202616 November 2026
50 measurements spanning 101 days, net +7,874. 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,813–30,522 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 50
Measured (UTC)Monthly usersChange
16 Nov 2026, 09:2129,286+722
12 Nov 2026, 23:0628,564+708
10 Nov 2026, 13:4627,856+465
8 Nov 2026, 23:0727,391+783
7 Nov 2026, 16:5626,608+1,761
5 Nov 2026, 13:3624,847+3
4 Nov 2026, 14:4824,844+1,139
2 Nov 2026, 16:1923,705-22
1 Nov 2026, 19:0023,727-64
30 Oct 2026, 18:4023,791-32
28 Oct 2026, 16:3823,823-265
26 Oct 2026, 20:0024,088-16
24 Oct 2026, 19:1724,104-66
23 Oct 2026, 22:1124,170+43
22 Oct 2026, 20:0824,127-53
21 Oct 2026, 13:1824,180-57
20 Oct 2026, 08:3924,237-58
17 Oct 2026, 12:5524,295+20
16 Oct 2026, 11:0524,275+411
14 Oct 2026, 11:5623,864first 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 3 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 16 November 2026 — this entry's latest reading, not the date you are reading this.

“Fish VPN BOT” (@fish_vpn_bot), 29,286 monthly users as measured 16 November 2026. Telegram Register, tgregister.com/channel/fish_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.