Bot
GlushVPN | Обход Белого Списка
@glushvpn_bot
On this record: Growth · Engagement · Citations · Cite this entry
69,494monthly users
-6,840 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | 8372847047 |
|---|---|
| Type | Bot |
| Username | @glushvpn_bot |
| First recorded | 11 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 2 times, most recently 13 August 2026 |
| On Telegram | t.me/glushvpn_bot |
Growth
| Measured (UTC) | Monthly users | Change |
|---|---|---|
| 12 Aug 2026, 06:55 | 69,494 | -1,142 |
| 11 Aug 2026, 07:18 | 70,636 | -1,028 |
| 11 Aug 2026, 03:20 | 71,664 | no change |
| 10 Aug 2026, 05:26 | 71,664 | -1,134 |
| 9 Aug 2026, 06:11 | 72,798 | -2,179 |
| 7 Aug 2026, 08:32 | 74,977 | -1,357 |
| 6 Aug 2026, 10:55 | 76,334 | first 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 28 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. The 23 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
@glushvpns · 170,75138 posts🛡️Обход белых списков | ByeWhiteLists
@ByeWhiteLists · 2,2416 postsЖенская мудрость|Психология
@girlmylov · 11,4323 postsGlush vpn | Обход белого списка
@gIushvpn · 172 postsКТП
@ktp_1 · 4,2342 postsКулинария • Простые Рецепты
@Kulinariya_izi_retsept · 4,3052 postsМЯСО 🥩
@mesko14 · 5,2952 postsБобер Курва
@stukkoo · 4,1832 postsКото♡Пес
@suklpo · 4,2592 postsЗАЛИП
@tik_zalip_tok · 5,2382 postsBatysyr
@batysyr2 · 81 postБлогосфера
@blogosfer · 3,5371 postXepLiverse | Genshin | Honkai | Zenless | Ero
@genshin_honkai_zenless_ero · 3731 postБАБСКОЕ ЛОГОВО
@mixinstaa · 1,9051 postoh, maaliish
@ohmalish · 2,3731 postОбои | языки и темы
@parnye_oboi_parniye · 3001 postFULL Пездач
@pezdachfull · 1,3221 postПодслушано 69
@podslushano697 · 6971 postроблокс | бесплатные робуксы
@qwertrqm · 381 postТВОИ СТОРИСЫ
@storislux · 2,1561 post🫥svs BIO🫥
@svs_perehodnik · 151 postTOP RU PRANKs
@toprupranks · 1,5521 postVPN Обход
@VPN_9696 · 171 post
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“GlushVPN | Обход Белого Списка” (@glushvpn_bot), 69,494 monthly users as measured 12 August 2026. Telegram Register, tgregister.com/channel/glushvpn_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.