💥Операторы дронов 69 бригады прикрытия 35 армии группировки войск "Восток" аннигилируют вражеские тяжёлые коптеры в небе Запорожья. @voin_dv
👍2

Channel
@vektor_35
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
258subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001673256521 |
|---|---|
| Type | Channel |
| Username | @vektor_35 |
| Created | 14 September 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 7 August 2026 |
| Last confirmed live | 7 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/vektor_35 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 08:01 | 258 | no change |
| 7 Aug 2026, 07:56 | 258 | first reading |
16 posts held, back to 15 July 2025 — 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 16 posts for this entry, the most recent from 15 August 2025. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 7 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
29 reactions across 13 posts, in 4 distinct kinds. The most used accounts for 34.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 10 | 34.5% | |
| 🔥 | 9 | 31.0% | |
| ❤ | 8 | 27.6% | |
| 🙏 | 2 | 6.90% |
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 13 of the 16 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 29reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 15 July 2025 to 15 August 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
💥Операторы дронов 69 бригады прикрытия 35 армии группировки войск "Восток" аннигилируют вражеские тяжёлые коптеры в небе Запорожья. @voin_dv
👍2
Каскад, 63 отдельный танковый батальон "Аврора" г. Санкт-Петербург. Сегодня, в ночное время уничтожили на посту бабу ягу. На гуляйпольском направлении 👉🔥 Поразили из автомата с использованием тепловизора, летела низко на высоте 30-50 метров. Рекомендую остальным расчетам повысить бдительность, каждый такой гексокоптер сбитый, это потенциально спасенный личный состав и техника и ВЕСЬ личный состав обязан это понима…
👍2
💥1198 мотострелковый полк группировки войск "Восток" уничтожает живую силу, автомобильную технику, пункты управления БЛА и другие материально-технические средства противника на Южно-Донецком направлении @voin_dv
❤1👍1
💥38 гвардейская мотострелковая бригада 35 армии группировки войск "Восток" провела работу по уничтожению укрытий живой силы и склада ГСМ ВСУ в Полтавке @voin_dv
❤1👍1
Операторы БЛА 35 армии группировки войск "Восток" нанесли удары по живой силе и автомобильной технике противника в Запорожской области @voin_dv
👍2
Ночные Охотники 35 армии группировки войск "Восток" находят свою добычу на Запорожском направлении. Никто из хлопчиков лёгким испугом не отделался. @voin_dv
❤2🔥1
Операторы 38 гвардейской мотострелковой бригады 35 армии группировки войск "Восток" уничтожают автотранспорт противника в Запорожской области. Всего за сутки в зоне ответственности Амурцев было уничтожено: в Гуляйполе - ПВД противника; севернее Гуляйполя – Starlink, автомобиль типа "пикап"; западнее Малиновки – антенна ретранслятора; в Червоном – поражена группа живой силы противника; северо-восточнее Мирного – огне…
👍2
Работа артиллерийских расчётов и операторов БЛА 35 армии по уничтожению средств спутниковой связи, живой силы и опорных пунктов противника в Запорожской области. Всего за сутки в зоне ответственности 35 армии огневыми средствами было поражено: В Полтавке – автотранспорт противника; В Червоном – блиндаж с живой силой, терминал Starlink; В Гуляйполе – ПВД, пункт управления БЛА; восточнее Червоного - сорвана ротация, …
❤1🔥1
🪂 Российские войска продолжают наступление на Запорожском направлении, давление идёт по тылам и на линии боевых действий. Активно работают БпЛА (в основном FPV), пехота малыми группами и огневое выжигание артиллерией позиций противника. Основная цель ВС РФ перерезать логистику разрушить оборону комплексными ударами. Всего на Запорожском направлении зафиксировано 490 ударов за сутки, в том числе 7 авиаударов, 328 F…
❤1🔥1
Операторы БпЛА 38 мотострелковой бригады группировки "Восток" уничтожили живую силу и опорные пункты противника на Положском направлении. @voin_dv
🔥2❤1
Video, posted without a caption
🙏2❤1
Voice message, posted without a caption
Showing the 12 most recent of 16 posts we hold for @vektor_35. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Names
Channels on the register whose handles appear in this channel's 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.
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 7 August 2026 — this entry's latest reading, not the date you are reading this.
“Вектор-35” (@vektor_35), 258 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/vektor_35.
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.