Bot
STRELKA VPN
@Strelka_vpn_bot
On this record: Growth · Engagement · Citations · Cite this entry
88,566monthly users
-218 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 | 5505539306 |
|---|---|
| Type | Bot |
| Username | @Strelka_vpn_bot |
| First recorded | 10 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/Strelka_vpn_bot |
Growth
| Measured (UTC) | Monthly users | Change |
|---|---|---|
| 14 Aug 2026, 22:34 | 88,566 | +225 |
| 12 Aug 2026, 14:07 | 88,341 | +21 |
| 11 Aug 2026, 16:31 | 88,320 | -280 |
| 10 Aug 2026, 19:35 | 88,600 | no change |
| 9 Aug 2026, 17:41 | 88,600 | +1,151 |
| 8 Aug 2026, 18:24 | 87,449 | -1,335 |
| 6 Aug 2026, 19:01 | 88,784 | 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 25 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 24 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.
@joerazdaet · 34915 postsAniTik🔥 | Аниме Эдиты | Anime Edits💜
@Anitik_edits · 38,3192 postsmodelerPRO - Нейросети и разработка
@modelerPRO · 1,3102 postsСПБ.ЛОГИСТИК: ГРУЗОПЕРЕВОЗКИ
@spblogistik · 1,6792 postsAvrrorka02 Фул
@Avrrorka020 · 41 postAZA NE MAZA
@azanemaza · 861 postBF Intel BF6 RedSec Battlefield 6
@bfintel · 1,3341 postДмитрий Николаев 💎
@DmNickolaeff · 2,5111 postSTRELKA VPN
@expror · 3041 postfoma321
@foma321 · 2551 postHobby Crypto X
@hobby_cryptoX · 9111 postWHO REALER?
@IC3BXNDO900 · 1,1471 postИскусство во ВСЁМ
@iskusstvo_vo_vsem · 33,6161 post𝙺𝙰𝙻𝙸𝙵𝙾𝚁𝙽𝙸𝚂𝙺𝚈𝚈
@Kaliforniskyy · 1321 postLCHF, KETO, PALEO рецепты
@KFCppDIET · 9151 postМгновения прошлого
@mgnovenia_proshlogo · 211,4971 postRUSSIAN MILITARIST
@militaristrussian67 · 35,4001 postМисайлово Live | Пригород Лесное
@misailovolive · 2,8041 postРЕАЛИТИ ТАКСИСТА
@realiti_taksista · 1,5631 postПлатформа
@steamplatforma · 16,1501 postСтроки
@stroki_tg · 17,4931 posttanta
@tantadraw · 3511 postTasty Cocks
@tastycocks · 3461 postZhmurkiAvto
@zmurkiavto · 3161 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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“STRELKA VPN” (@Strelka_vpn_bot), 88,566 monthly users as measured 14 August 2026. Telegram Register, tgregister.com/channel/Strelka_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.