Telegram RegisterThe public register of Telegram
Telegram profile photo for 3 Apes VPN

Bot

3 Apes VPN

@Apes3VPNbot

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

12,447monthly users

-439 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 ID8314348498
TypeBot
Username@Apes3VPNbot
First recorded20 August 2026
Last confirmed live25 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 25 August 2026
On Telegramt.me/Apes3VPNbot

Growth

12,20512,88612,545.57 August 2026 — 12,886 monthly users8 August 2026 — 12,551 monthly users11 August 2026 — 12,391 monthly users15 August 2026 — 12,205 monthly users18 August 2026 — 12,285 monthly users20 August 2026 — 12,285 monthly users21 August 2026 — 12,463 monthly users25 August 2026 — 12,447 monthly users12,4477 August 202625 August 2026
8 measurements spanning 19 days, net -439. 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 12,103–12,988 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
25 Aug 2026, 21:0412,447-16
21 Aug 2026, 23:5512,463+178
20 Aug 2026, 20:1312,285no change
18 Aug 2026, 14:2312,285+80
15 Aug 2026, 19:3512,205-186
11 Aug 2026, 18:0312,391-160
8 Aug 2026, 19:4012,551-335
7 Aug 2026, 04:3212,886first 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

“3 Apes VPN” (@Apes3VPNbot), 12,447 monthly users as measured 25 August 2026. Telegram Register, tgregister.com/channel/Apes3VPNbot.

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.