29 Jul 2026, 12:49 UTC43 viewsread 10 August 2026
Авторский блог по ИБ Карманный хакер 6/48 — 1400 (👀350) 6/72 — 1600 (👀400) 6/7д. — 1900 (👀550) 6/30д. — 2800 (👀800) ➿➿➿➿➿➿➿➿➿➿ ❤️ По вопросам: @ReivuManager
Channel
Reivu Media
@ReivuMedia
On this record: Growth · Engagement · Posts · Cite this entry
37subscribers
+2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002067174954 |
|---|---|
| Type | Channel |
| Username | @ReivuMedia |
| Created | 29 January 2024 — measured — dated from the channel’s first post |
| First recorded | 10 August 2026 |
| Last confirmed live | 28 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 28 August 2026 |
| On Telegram | t.me/ReivuMedia |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 21 Aug 2026, 20:58 | 37 | +1 |
| 15 Aug 2026, 17:33 | 36 | +1 |
| 10 Aug 2026, 23:45 | 35 | no change |
| 7 Aug 2026, 15:03 | 35 | first reading |
Engagement
7 posts held, back to 29 January 2024 — 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 7 posts for this entry, the most recent from 29 July 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
27 Mar 2025, 14:54 UTC≈1,990 viewsread 10 August 2026
🛍 При покупке сразу во всех IT каналах: 4/48 — 6000р (👀 4900) 4/72 — 6700р (👀 5700) ➿➿➿➿➿➿➿➿➿➿ ❤️ По вопросам: @ReivuManager
27 Mar 2025, 14:54 UTC≈2,000 viewsread 10 August 2026
Gamedev GameDev Base 4/48 - 400 (👀200) 4/72 - 500 (👀250) ➿➿➿➿➿➿➿➿➿➿ ❤️ По вопросам: @ReivuManager
27 Mar 2025, 14:54 UTC≈1,950 viewsread 10 August 2026
Python Программистика 4/48 - 1000р (👀 500) 4/72 - 1100р (👀 550) ➿➿➿➿➿➿➿➿➿➿ Программистика (Библиотека) 4/48 - 100р (👀 100) 4/72 - 110р (👀 110) ➿➿➿➿➿➿➿➿➿➿ При покупке во всех 2/48 - 1000р (👀 600) ❤️ По вопросам: @ReivuManager
27 Mar 2025, 14:53 UTC≈1,790 viewsread 10 August 2026
Hacking & infosec Hacking & InfoSec Base 4/48 - 1700р (👀850) 4/72 - 1900р (👀950) ➿➿➿➿➿➿➿➿➿➿ CyberGuard 4/48 - 600р (👀300) 4/72 - 700р (👀350) ➿➿➿➿➿➿➿➿➿➿ ИБ Вакансии 4/48 - 600р (👀300) 4/72 - 700р (👀350) ➿➿➿➿➿➿➿➿➿➿ linux administration 4/48 - 1700р (👀850) 4/72 - 1900р (👀950) ➿➿➿➿➿➿➿➿➿➿ При покупке во всех 2/48 - 4100р (👀 2300) ❤️ По вопросам: @ReivuManager
27 Mar 2025, 14:53 UTC≈1,600 viewsread 10 August 2026
Общее IT //code 4/48 - 420р (👀350) 4/72 - 480р (👀400) ➿➿➿➿➿➿➿➿➿➿ Dev Boost 4/48 - 750р (👀500) 4/72 - 825р (👀550) ➿➿➿➿➿➿➿➿➿➿ IT Books 4/48 - 675р (👀450) 4/72 - 800р (👀550) ➿➿➿➿➿➿➿➿➿➿ ИТ Архтивчик 4/48 - 500р (👀500) 4/72 - 550р (👀550) ➿➿➿➿➿➿➿➿➿➿ При покупке во всех 2/48 - 2100р (👀 1800) ❤️ По вопросам: @ReivuManager
29 Jan 2024, 14:33 UTCviews —
Channel created
Showing the 7 most recent of 7 posts we hold for @ReivuMedia. 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.
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 21 August 2026 — this entry's latest reading, not the date you are reading this.
“Reivu Media” (@ReivuMedia), 37 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/ReivuMedia.
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.