14 May 2026, 07:29 UTCviews —
ZabugorSecure VPN 💠 | Новости pinned a photo
Channel
ZabugorSecure VPN 💠 | Новости
@zabugorsecure
On this record: Growth · Engagement · Posts · Citations · Cite this entry
8subscribers
+1 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003803040063 |
|---|---|
| Type | Channel |
| Username | @zabugorsecure |
| Created | 11 May 2026 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 17 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 17 August 2026 |
| On Telegram | t.me/zabugorsecure |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Aug 2026, 18:14 | 8 | +1 |
| 12 Aug 2026, 19:16 | 7 | no change |
| 9 Aug 2026, 00:46 | 7 | first reading |
Engagement
5 posts held, back to 11 May 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 5 posts for this entry, the most recent from 14 May 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
13 May 2026, 06:32 UTC80 viewsread 12 August 2026
Photo
🔒 ZabugorSecure: устойчивость к блокировкам подтверждена Пока одни сервисы паникуют, мы продолжаем работать. Сегодня я повторно прогнал наш сервер через независимую CLI-утилиту DPI Checkers. 📊 Скрины результатов прилагаю. ✅ Что проверяли: · 🟢 Whitelist (белые списки РКН) – 19 из 21 ресурса работают штатно. Ошибки только у rkn.gov.ru и gov.ru (таймауты, скорее всего проблемы на их стороне, не связанные с блокировко…
11 May 2026, 11:13 UTC68 viewsread 12 August 2026
📲 Как подключиться к ZabugorSecure VPN: пошаговая инструкция 🎁 Бесплатный тестовый период — 3 дня! При первом подключении вы получаете 3 дня бесплатного доступа ко всем серверам без ограничений по скорости и трафику. Оцените качество до того, как оплачивать подписку. 1. Получите ссылку-подписку Перейдите в бота @vpn_zabugor_bot и нажмите кнопку «🚀 Получить доступ» или «✅ Подключить» в главном меню. Бот автоматическ…
11 May 2026, 11:10 UTC45 viewsread 12 August 2026
Photo
🌍 Добро пожаловать в официальный канал ZabugorSecure VPN! Мы помогаем получить быстрый и безопасный доступ к информации без ограничений. Что здесь будет: ✅ Новости сервиса и обновления протоколов ✅ Информация о доступных серверах и локациях ✅ Инструкции и советы по использованию 🤖 Перейти в бота для получения доступа: @vpn_zabugor_bot 👨💻 По вопросам пишите в лс канала! На связи 🤙🏻 Оставайтесь с нами — будет поле…
11 May 2026, 11:03 UTCviews —
Channel created
Showing the 5 most recent of 5 posts we hold for @zabugorsecure. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Citation-graph rank
Citation-graph rank — 609,664 of 1,584,733entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Mentions
Named by 1 registered channel — 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 17 August 2026 — this entry's latest reading, not the date you are reading this.
“ZabugorSecure VPN 💠 | Новости” (@zabugorsecure), 8 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/zabugorsecure.
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.