Telegram RegisterThe public register of Telegram
Telegram profile photo for Панда VPN

Bot

Панда VPN

@Mypandavpn_bot

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

72,333monthly users

-5,200 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 ID8644566929
TypeBot
Username@Mypandavpn_bot
First recorded11 August 2026
Last confirmed live7 November 2026
Measurements held48
Confirmed unchanged1 time, most recently 7 November 2026
On Telegramt.me/Mypandavpn_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 47% 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

54,04782,83668,441.57 August 2026 — 77,533 monthly users8 August 2026 — 75,333 monthly users9 August 2026 — 73,594 monthly users11 August 2026 — 71,245 monthly users11 August 2026 — 71,245 monthly users11 August 2026 — 70,202 monthly users14 August 2026 — 70,164 monthly users15 August 2026 — 68,441 monthly users16 August 2026 — 67,383 monthly users17 August 2026 — 66,794 monthly users18 August 2026 — 66,102 monthly users20 August 2026 — 63,291 monthly users21 August 2026 — 62,563 monthly users24 August 2026 — 60,213 monthly users25 August 2026 — 59,091 monthly users27 August 2026 — 55,695 monthly users28 August 2026 — 54,245 monthly users30 August 2026 — 54,047 monthly users31 August 2026 — 55,071 monthly users2 September 2026 — 56,075 monthly users4 September 2026 — 63,076 monthly users8 September 2026 — 69,187 monthly users10 September 2026 — 69,878 monthly users13 September 2026 — 71,435 monthly users14 September 2026 — 70,498 monthly users18 September 2026 — 73,149 monthly users24 September 2026 — 75,914 monthly users3 October 2026 — 82,836 monthly users8 October 2026 — 79,242 monthly users12 October 2026 — 75,807 monthly users14 October 2026 — 77,024 monthly users15 October 2026 — 76,252 monthly users17 October 2026 — 76,196 monthly users19 October 2026 — 76,115 monthly users20 October 2026 — 74,735 monthly users21 October 2026 — 74,246 monthly users22 October 2026 — 73,940 monthly users23 October 2026 — 73,454 monthly users24 October 2026 — 73,360 monthly users26 October 2026 — 73,295 monthly users28 October 2026 — 72,626 monthly users29 October 2026 — 72,764 monthly users30 October 2026 — 73,648 monthly users1 November 2026 — 73,353 monthly users3 November 2026 — 73,094 monthly users4 November 2026 — 73,266 monthly users5 November 2026 — 73,039 monthly users7 November 2026 — 72,333 monthly users72,3337 August 20267 November 2026
48 measurements spanning 92 days, net -5,200. 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 49,729–87,154 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 48
Measured (UTC)Monthly usersChange
7 Nov 2026, 01:3772,333-706
5 Nov 2026, 23:1473,039-227
4 Nov 2026, 01:5773,266+172
3 Nov 2026, 02:0573,094-259
1 Nov 2026, 23:2573,353-295
30 Oct 2026, 20:0673,648+884
29 Oct 2026, 22:0172,764+138
28 Oct 2026, 21:2772,626-669
26 Oct 2026, 20:3973,295-65
24 Oct 2026, 16:1873,360-94
23 Oct 2026, 17:1073,454-486
22 Oct 2026, 20:0673,940-306
21 Oct 2026, 16:0774,246-489
20 Oct 2026, 10:0674,735-1,380
19 Oct 2026, 10:0676,115-81
17 Oct 2026, 06:0076,196-56
15 Oct 2026, 06:4876,252-772
14 Oct 2026, 08:2877,024+1,217
12 Oct 2026, 18:1075,807-3,435
8 Oct 2026, 03:5679,242first 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 2 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.

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

“Панда VPN” (@Mypandavpn_bot), 72,333 monthly users as measured 7 November 2026. Telegram Register, tgregister.com/channel/Mypandavpn_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.