Харьковская область ПУ БПЛА Склад БК Пикап Танк Т-72 Совместная работа 11АК 1МСБ 1МСП РВСН t.me/anwarfirstgroup
👍67🔥42❤16custom 53236598823421342384custom 53233434377416986362👏1🤣1

Channel
@anwarfirstgroup
On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry
24,128subscribers
-199 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001970644748 |
|---|---|
| Type | Channel |
| Username | @anwarfirstgroup |
| Created | 24 September 2023 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 7 September 2026 |
| Measurements held | 30 |
| Confirmed unchanged | 1 time, most recently 7 September 2026 |
| On Telegram | t.me/anwarfirstgroup |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Sept 2026, 02:57 | 24,128 | -5 |
| 4 Sept 2026, 12:40 | 24,133 | -7 |
| 3 Sept 2026, 01:09 | 24,140 | -12 |
| 1 Sept 2026, 20:14 | 24,152 | -7 |
| 31 Aug 2026, 19:06 | 24,159 | -3 |
| 30 Aug 2026, 17:14 | 24,162 | +14 |
| 29 Aug 2026, 16:45 | 24,148 | +1 |
| 28 Aug 2026, 17:35 | 24,147 | -2 |
| 27 Aug 2026, 17:37 | 24,149 | -8 |
| 26 Aug 2026, 19:15 | 24,157 | -4 |
| 25 Aug 2026, 21:06 | 24,161 | +3 |
| 24 Aug 2026, 23:56 | 24,158 | -7 |
| 23 Aug 2026, 14:37 | 24,165 | -7 |
| 21 Aug 2026, 22:27 | 24,172 | -12 |
| 20 Aug 2026, 14:52 | 24,184 | -5 |
| 19 Aug 2026, 14:22 | 24,189 | -3 |
| 18 Aug 2026, 16:13 | 24,192 | -9 |
| 17 Aug 2026, 17:16 | 24,201 | -4 |
| 16 Aug 2026, 15:14 | 24,205 | -14 |
| 15 Aug 2026, 01:27 | 24,219 | first reading |
27 posts held, back to 3 March 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 58 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 24 August 2026 |
|---|---|
| Posts held | 27 (3 March 2026 – 24 August 2026) |
| Views total | 42,940 |
| Reactions total | 1,359 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 10:48 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Measured directly from 24 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.
6,434 reactions across 27 posts, in 19 distinct kinds. The most used accounts for 48.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 3,095 | 48.1% | |
| ❤ | 1,304 | 20.3% | |
| 👍 | 1,107 | 17.2% | |
| custom 5323659882342134238 | 308 | 4.79% | |
| custom 5323343437741698636 | 184 | 2.86% | |
| 👏 | 144 | 2.24% | |
| 🙏 | 108 | 1.68% | |
| 🥰 | 45 | 0.699% | |
| 😁 | 32 | 0.497% | |
| 👎 | 26 | 0.404% | |
| 🤣 | 25 | 0.389% | |
| 🎉 | 16 | 0.249% | |
| 🕊 | 12 | 0.187% | |
| 🤔 | 9 | 0.14% | |
| 🤬 | 9 | 0.14% | |
| 😢 | 4 | 0.062% | |
| 👌 | 3 | 0.047% | |
| 😍 | 2 | 0.031% | |
| ✍ | 1 | 0.016% |
Custom emoji. 2 of the rows above are 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 counts beside them are 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 27 of the 27 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 6,434 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 27 most recent posts we hold, published 3 March 2026 to 24 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @anwarfirstgroup. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 27 most recent posts we hold for this entry, published 3 March 2026 to 24 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Харьковская область ПУ БПЛА Склад БК Пикап Танк Т-72 Совместная работа 11АК 1МСБ 1МСП РВСН t.me/anwarfirstgroup
👍67🔥42❤16custom 53236598823421342384custom 53233434377416986362👏1🤣1
Харьковская область. Заминировать все пути подъезда - done Закошмарить хохла - дело чести 🐷 t.me/anwarfirstgroup
🔥125❤21👍21😁5👏2
Харьковская область Небольшая нарезка видео (и хохлов) за прошедший месяц. Поддерживаем союзников на переднем крае, а так же кошмарим противника в тылу. Работа с новым носителем Дягтерёва. Всё будет Россия ! t.me/anwarfirstgroup
❤100🔥80👏23👍7custom 53233434377416986364
‼️🇷🇺💥Спецназы «Анвар» и «Запад» с помощью Носителя Дягтерева громят тылы ВСУ ▪️В Харьковской области отряды спецназа с помощью носителя оптоволоконных дронов уничтожены: ➖САУ "Краб", танк Т-72Б, боевые бронемашины и живая сила врага, а также электрическая подстанция. ⚠️Подписаться на RV: MAX | t.me/RVvoenkor
❤77🔥76👍21custom 53233434377416986365
‼️🇷🇺💥 Спецназ "Анвар" уже в Харькове! ▪️Новое изобретение - "Носитель Дягтерева" продолжает кошмарить ВСУ. Отряд спецназ "Анвар" уже в глубоком тылу кошмарит врага в Харькове. ▪️Поражены - боевые бронемашины, логистические фуры, пикапы с РЭБ, живая сила, вышка сотовой связи и здание СБУ в центре Харькова. ⚠️Подписаться на RV: MAX | t.me/RVvoenkor
🔥175👍39👏18❤12custom 53233434377416986369👎3😁2🤣1
‼️🇷🇺🔥«Носитель Дягтерёва» ворвался в тылы врага, массово сжигая технику ▪️Работает спецназ «Анвар» и 11-й Армейский корпус. ▪️Новое изобретение «Носитель Дягтерёва» позволяет залетать в глубокий тыл врага и жечь технику в самом Харькове днем и ночью. Радиогоризонт и РЭБ не помеха. ▪️Поражены САУ, ББМ, Пикапы с живой силой , Грузовой военный транспорт, буксир и военный кран. ⚠️Подписаться на RV: MAX | t.me/RVvoenkor
🔥139❤31👍17👏5🙏3
Год назад, 12.08.2024 противник пытался закрепиться в н.п. Гирьи, но у него это немного не получилось. Решили выложить кадры боевой работы, которые в основном в сеть не выкладывали. Что-то добавили из личного архива. Репортажи о том дне так же можно посмотреть : @sashakots @yaremshooter 18+ t.me/zogrussia1
🔥146🙏28❤19👍12
🇺🇦⚔🇷🇺Враг бросает танки в контрнаступ в Харьковской области ▪️Командование ВСУ бросает войска в районе Великий Бурлук - Меловое, пытаясь прорвать оборону российских войск. ▪️Технику противника встретил огнём спецназ "Анвар" совместно с 11 Армейским Корпусом. ▪️Вчера стало известно, что т на Рубцовском направлении противник контратакует в районе населённых пунктов Редкодуб, Новое, Катериновка и Карповка, бросая в бой…
🔥164👍26❤19🙏10🤔3🤬1
#Эпизод22 Партизаны и подпольщики Отряда Ковпака продолжают свой ратный труд На этот раз уничтожен🔥 релейный шкаф в Киевской области, в результате чего на несколько часов были прерваны железнодорожные перевозки нацистов, нарушена военная логистика. ❗️Партизаны и подпольщики на территориях, подконтрольных киевскому режиму есть! Фронт внутреннего сопротивления бандеровцам есть! Если руководство России начнёт оказыват…
👍67🔥46❤16🤣9👎2🤔1
Харьковская область Окрестности Великий Булурук. Совместная работа 1МСБ 1МСП (КТ) РВСН t.me/anwarfirstgroup
🔥150❤18custom 532365988234213423818👍9🤔2
Харьковская область Минус т72 Совместная работа 65 ББС 1 мсб 1 мсп РВСН t.me/anwarfirstgroup
❤103👍56🔥40🤔1
Отряд «Анвара» показывает, что наши стабильно также урабатывают фуры противника в ближних тылах. Как бы парадоксально не звучало, такой работы много, но не всем разрешают показывать. Такой вот абсурд. БС в TG ✊ | БС в МАХ 🤫
🔥215❤34👍21👏5👎2🤔2😁1
Showing the 12 most recent of 27 posts we hold for @anwarfirstgroup. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
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 4 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 7 September 2026 — this entry's latest reading, not the date you are reading this.
“ANWAR” (@anwarfirstgroup), 24,128 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/anwarfirstgroup.
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.