ГрВ «Восток» заявила об освобождении Нового Поля в 7 км от зоны контроля. Очередной флаговтык для отчёта
🤬2😱1

Channel
@spets_SVOdkiZ
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
498subscribers
+180 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001909368410 |
|---|---|
| Type | Channel |
| Username | @spets_SVOdkiZ |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/spets_SVOdkiZ |
International news — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 21 September 2026 and assigned it the closest of 31 fixed categories, at 50% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 04:18 | 498 | -8 |
| 10 Sept 2026, 05:58 | 506 | -5 |
| 1 Sept 2026, 02:59 | 511 | +157 |
| 25 Aug 2026, 07:25 | 354 | -8 |
| 19 Aug 2026, 04:11 | 362 | +45 |
| 11 Aug 2026, 23:23 | 317 | -1 |
| 11 Aug 2026, 12:49 | 318 | first reading |
19 posts held, back to 9 August 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 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 19 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
106 reactions across 17 posts, in 8 distinct kinds. The most used accounts for 26.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤬 | 28 | 26.4% | |
| 🔥 | 25 | 23.6% | |
| custom 5427007820664964976 | 18 | 17.0% | |
| 👍 | 14 | 13.2% | |
| ❤ | 13 | 12.3% | |
| 😢 | 6 | 5.66% | |
| 👏 | 1 | 0.943% | |
| 😱 | 1 | 0.943% |
Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it is Telegram’s.
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 17 of the 19 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 106 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 9 August 2026 to 11 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
ГрВ «Восток» заявила об освобождении Нового Поля в 7 км от зоны контроля. Очередной флаговтык для отчёта
🤬2😱1
Интересное мнение коллеги
🤩Почему заход в Чернобыльскую зону и Киев для ВС РФ считается не плохим планом?📍 🟥1) Заход в Чернобыль будет быстрым, так как там меньше всего укреплений, что позволит продвигаться значительно быстрее. 🤩Но это является для нас угрозой. ВСУ не будут сидеть в радиации и отступят на выгодные позиции вынудив нас либо сидеть самим в радиации либо использовать Беларусь в качестве ХАБА для переброски войск и содержания та…
❤3
🇷🇺🔥🇺🇦ВВС ВСУ потеряли истребитель МиГ-29 в Одесской области
🔥5
Не понимаю тех, кто ставит такую реакцию "🤬" на пост выше. Вы что тут вообще делаете? Канал целиком и полностью поддерживает СВО. Что-то не нравится - идите в либеральный канал, ну поплачьте.
🤬7custom 54270078206649649764👍2🔥2
⚡️"Яблоко" сняли с выборов в Госдуму. Регистрация кандидатов от этой партии. была отменена
🤬11👍6
⚡️В эти минуты решается судьба либеральной партии «Яблоко» 🍏. Партию могут снять с парламентских выборов.
👍6🔥4🤬3custom 54270078206649649761
Лиманское направление 🔵🇺🇦Украинские войска оккупировали Липовое. 🟣За Зелёную Долину продолжаются бои, но в ближайшее время это село может перейти под контроль ВСУ. Площадь продвижения: 4,52 км²
🤬5
⚡️▫️▫️▫️ Добропольское направление 🚩Подразделения ГрВ "Центр" продолжили продвижение в глубину обороны ВСУ и освободили н.п. Красноподолье, что находится западнее Черниговки (Красноярского) и вышли к окраинам посёлка Доброполье (не путать с городом). 🔴🇷🇺Также ВС РФ продвинулись северо-западнее Шевченко, сжимая кольцо вокруг Матяшево и подходя к Новому Гришино. Освобождено: 4,2 км²
custom 54270078206649649763❤1🔥1
Межевское направление 🔴🇷🇺Российские войска расширили контроль южнее Новоподгородного, противник держит оборону в Новониколаевке, Муравке и Беляковке. Освобождено: 8,38 км² Днепропетровская область
❤2custom 54270078206649649762
Дружковское направление 🔴🇷🇺ВС РФ закрепились в Петровке. Половина села под контролем "Центра". Освобождено: 3,37 км²
🔥5custom 54270078206649649763❤1
🇺🇦⚡️🇷🇺 Сегодня утром Нижнекамск подвергся атаке украинских дронов. 🔴В результате погибли 12 человек, ещё 39 получили ранения. 🔴Пострадавшим оказывают помощь в центральной городской больнице, куда направили дополнительные бригады медиков из Набережных Челнов и Республиканского центра медицины катастроф. 🔴В Татарстане объявили траур по погибшим. 🔴Нижнекамский нефтехимический комплекс, крупнейший в Европе и входящий…
😢3
Showing the 12 most recent of 19 posts we hold for @spets_SVOdkiZ. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 2 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.
Named by
Channels on the register whose posts name this channel's handle.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“СпецСВОдки Z” (@spets_SVOdkiZ), 498 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/spets_SVOdkiZ.
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.