Channel
@zmeyDDD
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
1,337subscribers
-5 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001607166799 |
|---|---|
| Type | Channel |
| Username | @zmeyDDD |
| Created | Between 1 November 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 3 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 3 September 2026 |
| On Telegram | t.me/zmeyDDD |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Sept 2026, 15:58 | 1,337 | -1 |
| 28 Aug 2026, 12:34 | 1,338 | -1 |
| 25 Aug 2026, 15:46 | 1,339 | -1 |
| 22 Aug 2026, 16:36 | 1,340 | +1 |
| 19 Aug 2026, 01:16 | 1,339 | -3 |
| 9 Aug 2026, 05:01 | 1,342 | no change |
| 8 Aug 2026, 11:34 | 1,342 | first reading |
18 posts held, back to 31 October 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 page of 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 18 posts for this entry, the most recent from 14 November 2024. An engagement rate over an empty window would be a number about nothing.
Measured directly from 18 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
3 reactions across 3 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 3 | 100.0% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 4 of the 18 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 3 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 31 October 2024 to 14 November 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Свежие кадры прополки противника FPV-дронами «Князь Вандал Новгородский» в Кореневском районе Курского приграничья. Под раздачу попали Т-64БВ, бронемашина Kirpi, БМП M2A2 Bradley, миномет и живая сила ВСУ. Второе видео - удар FPV на оптоволокне по танку M1A1SA Abrams в Курской области. Новости всё про фронт.
❤1
Signed Дмитрий
Погоня FPV-дрона на оптоволокне догоняет за вражескую БМП-2, которая завершилась её уничтожением. Также был поражен вражеский Т-80БВ. Покровское направление. Новости всё про фронт.
Signed Дмитрий
🇷🇺🔥 В районе н.п. Дружба (ДНР) российскими артиллеристами уничтожен пункт управления БпЛА ВСУ. Новости всё про фронт.
Signed Дмитрий
🇷🇺🔥 Уничтожение техники и живой силы укронацистов в Курской области. Новости всё про фронт.
Signed Дмитрий
Российские войска давят противника на Северском направлении Наши бойцы с боем продвигаются в районе Спорного и Выемки. Позиции врага обрабатываются артиллерией и FPV-дронами, после чего в дело вступают штурмовые подразделения, завершающие зачистку. Новости всё про фронт.
Signed Дмитрий
🔥 В Курской области сожгли еще один немецкий Leopard 2 Ударами FPV-дронов и артиллерии сожжен очередной немецкий танк. Экипаж не успел эвакуироваться и сгорел вместе с техникой. Новости всё про фронт.
Signed Дмитрий
В Суджанском районе Курской области украинские боевики очень пожалели, что столкнулись с российскими десантниками. Быстро, четко и уверенно бойцы ВС РФ размотали мерзавцев и успешно овладели вражеским опорником. Новости всё про фронт.
Signed Дмитрий
Российская армия продолжает наносить удары по ВСУ в Сумской области В районе населённого пункта Иволжанское было обнаружено и уничтожено место сбора сил врага. По цели прилетели ракета и реактивные снаряды РСЗО. Новости всё про фронт.
Signed Дмитрий
🇷🇺🚀 Совместная работа миномётного и FPV-расчётов группировки "Север". В Русском приграничье был вскрыт ПВД пятачков. Таким соседями сразу же захотели "передать привет" миномётчики, а затем и операторы FPV. Новости всё про фронт.
Signed Дмитрий
🇷🇺🔥 Уничтожение штурмовой группы хряковояк в Часов Яре. Сначала противник потерял БМП. Затем, понеся потери, пятачки укрылись в полуразрушенном доме, куда немедленно хорошо прилетело. Новости всё про фронт.
❤1
Signed Дмитрий
18+ Украинский боевик отдал побратиму автомат, чтобы тот застрелился К лежащему раненому ВСУшнику подошел побратим, и вместо того, чтобы попробовать спасти его, отдал ему автомат, чтобы тот покончил с жизнью. Оружие боевик забрал обратно, труп так и остался гнить в сырой земле. Новости всё про фронт.
Signed Дмитрий
🇷🇺Ликвидация сразу двух пятачков с помощью сброса на одном из участков фронта. Новости всё про фронт.
Signed Дмитрий
Showing the 12 most recent of 18 posts we hold for @zmeyDDD. 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.
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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 3 September 2026 — this entry's latest reading, not the date you are reading this.
“Новости всё про фронт.” (@zmeyDDD), 1,337 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/zmeyDDD.
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.