Bot
Мы всегда рядом!
@WeNear_MVD_bot
On this record: Growth · Engagement · Citations · Cite this entry
14,760monthly users
+1,135 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | 8104776959 |
|---|---|
| Type | Bot |
| Username | @WeNear_MVD_bot |
| First recorded | 18 August 2026 |
| Last confirmed live | 19 August 2026 |
| Measurements held | 7 |
| On Telegram | t.me/WeNear_MVD_bot |
Growth
| Measured (UTC) | Monthly users | Change |
|---|---|---|
| 18 Aug 2026, 21:27 | 14,760 | no change |
| 17 Aug 2026, 10:26 | 14,760 | +17 |
| 15 Aug 2026, 18:56 | 14,743 | +350 |
| 14 Aug 2026, 05:57 | 14,393 | +60 |
| 10 Aug 2026, 07:25 | 14,333 | +66 |
| 7 Aug 2026, 05:11 | 14,267 | +642 |
| 6 Aug 2026, 02:01 | 13,625 | 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 68 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.
@police_minsk · 22,2217 postsУГАИ ГУВД Мингорисполкома
@gaiminsk · 37,1303 postsКРЕПОСТЬ
@krepostfortuvd · 14,9913 postsМилиция Беларуси. Мы – НА СТРАЖЕ
@NA_STRAGE · 35,9683 postsМилиция Витебщины
@uvd_vitebsk · 9,4213 postsДокшицы.бай Родныя вытокі 🇧🇾
@dokshitsyby · 1,4372 postsФаниполь Бай
@fanipolby · 9,9882 postsГосавтоинспекция Гомельщины
@gai_gomel · 9,2552 postsГАИ Минщины
@gai_minobl · 8,7962 postsЛокатор
@lokatorvvspvo · 2,7422 posts102.Неман
@Neman102 · 7,6762 postsОАО «Новогрудское строительно-монтажное управление "
@oaonsmu · 522 postsЯ/МЫ ОМОН
@omonby2 · 3,7392 postsМВД Беларуси
@pressmvd · 69,8622 posts❗️Шестой регион❗️
@re6ion · 9692 postsСлавгородBy🇧🇾
@slavgorodby · 2612 postsМинск | Советский район
@sov_minsk · 6,5212 postsСожский Форпост
@uvdgomel · 7,8322 postsГАИ Витебщины
@vitebsk_gai · 15,5642 postsРогачевский центр творчества детей и молодежи
@ctdimrogachev · 9361 postБыхов Сегодня: Новости Беларуси
@novostibyhova · 2,7411 postНовости Кировска
@novostikirovska · 1,6911 postУЗ "1-я городская клиническая больница" г. Минска
@uz1gkb · 1831 postГоворит и показывает Бобруйск
@zefirfm · 10,0191 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 18 August 2026 — this entry's latest reading, not the date you are reading this.
“Мы всегда рядом!” (@WeNear_MVD_bot), 14,760 monthly users as measured 18 August 2026. Telegram Register, tgregister.com/channel/WeNear_MVD_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.