Channel
@osint_alarm
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
2,736subscribers
+97 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002834338577 |
|---|---|
| Type | Channel |
| Username | @osint_alarm |
| Created | Between 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/osint_alarm |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 11:36 | 2,736 | +63 |
| 10 Aug 2026, 03:50 | 2,673 | +30 |
| 7 Aug 2026, 09:10 | 2,643 | +4 |
| 7 Aug 2026, 02:17 | 2,639 | first reading |
13 posts held, back to 5 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 2 pagesof 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 7 August 2026 |
|---|---|
| Posts held | 13 (5 August 2026 – 7 August 2026) |
| Views total | 24,299 |
| Reactions total | 194 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 16:19 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 6 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.
194 reactions across 12 posts, in 19 distinct kinds. The most used accounts for 45.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 89 | 45.9% | |
| 🔥 | 22 | 11.3% | |
| 🤔 | 20 | 10.3% | |
| ❤ | 17 | 8.76% | |
| 😍 | 7 | 3.61% | |
| 🍌 | 6 | 3.09% | |
| 👎 | 5 | 2.58% | |
| 😢 | 5 | 2.58% | |
| 🍾 | 4 | 2.06% | |
| 🤣 | 4 | 2.06% | |
| 🤬 | 4 | 2.06% | |
| ✍ | 2 | 1.03% | |
| 😁 | 2 | 1.03% | |
| 😭 | 2 | 1.03% | |
| 🌭 | 1 | 0.515% | |
| 👏 | 1 | 0.515% | |
| 🤩 | 1 | 0.515% | |
| 🥰 | 1 | 0.515% | |
| 🫡 | 1 | 0.515% |
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 12 of the 13 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 194reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 5 August 2026 to 7 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.
Ракетный удар по складу у г.Киев, Киевской области в ночь на 1 августа 2026г. Был уничтожен логистический центр "Эталон" 🟢, общей площадью около 22 000 м2, а также произошёл промах 🟣. Геолокация: 50.38292, 30.33725 P.S. спасибо подписчику за фото
❤4👍4
Повторный ракетный удар по предприятию в г.Киев, в ночь на 30 июля 2026г. Вследствие атаки на завод "Маяк" были поражены: 🔴 Ранее атакованный цех. Повреждён. 🟡 Цех. Повреждён. 🟣 Попадание в рынок. Геолокация: 50.48755, 30.49140
👍14🌭1🤬1😍1
Удар БпЛА по локомотиву в н.п.Вишневое, Днепропетровской области 6 августа 2026г. Вследствие атаки была уничтожена секция 2ТЭ10У-0482 🩵, пострадал транспорт который перевозили, а также произошёл промах 🟣, который видно и на видео, и на Сентениле. Изнанка заявила применение Искандера, но ни на видео, ни на спутниковом снимке результата его применения не заметно. Геолокация: 48.44071, 33.91500
👍11😁2🤬1
Ракетный удар, предположительно, по предприятию в г.Киев, 26 июля 2026г. Был атакован бывший цех 🟠 "Киевского завода химикатов "Радикал"", а также произошёл промах 🟣. С 90-х годов данная часть завода сдаётся в аренду различным частникам, когда-то тут располагалась типография «Бліц-Флекс», но информация давно не актуальна, потому вероятно, что цех арендует несколько фирм в т.ч. под производственные помещения. Геолок…
👍15👎1
Повторный удар по предприятию в г.Киев, 19 июля 2026. Вследствие атаки на предприятие "Киевприбор" был повреждён ранее атакованный цех 🔴. Также всплыли фото одного из зданий 🟡, которое сильно пострадало от пожара. В какую из атак оно было поражено, установить не удалось. Геолокация: 50.45584, 30.43369
👍12🔥6🍾1👎1😍1
Удар БпЛА по вагону в г.Лозовая, Харьковской области 6 августа 2026г. Был уничтожен вагон у ЖД вокзала. Учитывая схожие случаи с атакой вагонов, крайне вероятно, что оператор или программа перепутали его силуэт с условным ВЛ8М. Геолокация: 48.89158, 36.31687
🔥8🤔3👍1👎1👏1🤩1🥰1😍1
Удар БпЛА по энергоинфраструктуре в н.п.Борзна, Черниговской области в начале июля 2026г. Судя по артефактам, в июне был достроен "саркофаг" для трансформатора 🟢 на территории ПС 110\35 кВ "Борзна", а при атаке произошёл недолёт 🟣. Под вопросом был ли второй заход дрона, но уже на саркофаг, но скорее нет чем да. Координаты: 51.26681, 32.42231
👍5😭2❤1👎1
Удар БпЛА по объекту неустановленного назначения в г.Шостка, Сумской области 17 июня 2026г. Возможно была поражена стоянка 🟣, по Сентенилю значимых признаков разрушений не обнаружено. Геолокация точки съёмки: 51.85837, 33.49854
🔥8👍1🤬1😍1
Удар БпЛА по газовой инфраструктуре у н.п.Новая Семёновка, Харьковской области, предположительно, 20 июля 2026г. Было повреждено здание на территории газопромышленного управления "Шебелинкагаздобыча". Геолокация: 49.43037, 36.09787
❤10🍾3😍3🤬1
Последние два дня ломают копья на счёт того, чей это барражирующий боеприпас пытаясь по виду определить, но как нам кажется, самое важное это не вид, а то в какую строну он летел и где его атаковали. А атаковали его у н.п.Весёлая Лопань, Белгородской области в 17км от границы и летел, соответственно, он в глубь территории России, что однозначно говорит о его принадлежности к украинскому вооружению. Геолокация: 50.49…
🤔17👍7🍌6✍2❤2
Удар БпЛА, предположительно, по складу в н.п.Кучиновка, Черниговской области, предположительно, 11 июля 2026г. Был повреждён ангар 🟢 и произошло два промаха 🟣. Геолокация: 51.72094, 31.89385
😢5👍3🤣3🫡1
Прилёты, уламки та вибухи (OSINT HUB) pinned a photo
Showing the 12 most recent of 13 posts we hold for @osint_alarm. 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.
Citation-graph rank — 24,346 of 1,481,217entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“Прилёты, уламки та вибухи (OSINT HUB)” (@osint_alarm), 2,736 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/osint_alarm.
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.