Bot
Lumix VPN
@Lumix_vpn_bot
On this record: Growth · Engagement · Citations · Cite this entry
53,195monthly users
+27,937 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 | 8612405857 |
|---|---|
| Type | Bot |
| Username | @Lumix_vpn_bot |
| First recorded | 12 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 16 August 2026 |
| On Telegram | t.me/Lumix_vpn_bot |
Growth
| Measured (UTC) | Monthly users | Change |
|---|---|---|
| 16 Aug 2026, 05:37 | 53,195 | +5,600 |
| 13 Aug 2026, 11:47 | 47,595 | +1,150 |
| 12 Aug 2026, 18:39 | 46,445 | no change |
| 12 Aug 2026, 13:33 | 46,445 | +3,353 |
| 11 Aug 2026, 10:15 | 43,092 | +3,889 |
| 9 Aug 2026, 08:51 | 39,203 | +3,648 |
| 8 Aug 2026, 08:55 | 35,555 | +6,190 |
| 6 Aug 2026, 09:41 | 29,365 | +4,107 |
| 6 Aug 2026, 01:49 | 25,258 | 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 258 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.
@lumixvpn · 63,36270 postsSupercell | Шпилки
@supercell_shpilki · 4,92921 postsValorant | Шпилки
@valorant_shpilki · 2,44019 postsОткрытки с добрым утром
@cardsgreet · 40,50016 postsFortnite | Шпилки
@fortnite_shpilki · 1,52716 postsШпилки
@shpilki_news · 25,35316 postsMobile Legends | Шпилки
@mlbb_shpilki · 67615 postsTío Roshi
@TIOROSHI4 · 54,86914 postsСМЕШНЫЕ ВИДЕО
@prikoly_memy_yumorn · 428,61413 postsПОКРОВСК КРАСНОАРМЕЙСК СЛАВЯНСК КУПЯНСК
@voinasg · 16,86313 postsRoblox | Шпилки
@roblox_shpilki · 4,26712 postsВОЙНА НА УКРАИНЕ СВО УКРАИНА
@novostydhd · 57,91111 posts4chan +
@ru4chan18 · 105,23911 postsМистер Бизнес
@biznesuhaaaa · 44,83010 postsАНЕКДОТЫ
@smeshnye_videos_prikoly_memy · 102,63510 postsДРАКИ
@ulichnye_nokauty_video_boi · 78,79310 postsСРОЧНЫЕ СВЕЖИЕ НОВОСТИ
@zhest_dtp58 · 56,00710 postsБезумный Паша (Ильин)
@pashaabakan · 7,7899 postsЧП САНКТ-ПЕТЕРБУРГ НОВОСТИ
@piter_dtp78 · 125,3439 postsСЕКСОПОЛИС
@police_of_love · 16,4399 postsСМЕШНЫЕ ИСТОРИИ
@poshlyeb_stydnyer_krinzhovyew · 36,4919 postsОТКРЫТКИ | ПОЗДРАВЛЕНИЯ
@pozdravlenie_kartinki_otkrytka · 94,5219 postsTWITCH
@tvich_novosti_blogery_strimery · 32,6119 postsЧП КАЗАНЬ ТАТАРСТАН НОВОСТИ
@zhest_dtp16 · 37,2639 posts
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 August 2026 — this entry's latest reading, not the date you are reading this.
“Lumix VPN” (@Lumix_vpn_bot), 53,195 monthly users as measured 16 August 2026. Telegram Register, tgregister.com/channel/Lumix_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.