Одеса / район - чисто, буде відбій
🙏1,110❤90👍60🤬22🫡6

Channel
@war_monitor
On this record: Topic · Growth · Engagement · What this channel posts · View velocity · Reactions · Stars · Posts · Citations · Telegram's recommendations · Domains linked from posts · Cross-platform identity · Referenced elsewhere · Cite this entry
965,270subscribers
+1,526 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 316,228–1,000,000.
| Telegram ID | -1001641260594 |
|---|---|
| Type | Channel |
| Username | @war_monitor |
| Description | Моніторинг ворожої авіації. 📮 Зв'язок — war_monitor@proton.me 👋 Підтримати канал — https://base.monobank.ua/monitor |
| Created | 25 April 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/war_monitor |
International news — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 74% 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 |
|---|---|---|
| 12 Aug 2026, 04:57 | 965,270 | -4 |
| 11 Aug 2026, 03:16 | 965,274 | +659 |
| 10 Aug 2026, 05:42 | 964,615 | +486 |
| 9 Aug 2026, 08:41 | 964,129 | +286 |
| 8 Aug 2026, 06:22 | 963,843 | +171 |
| 7 Aug 2026, 04:03 | 963,672 | -9 |
| 6 Aug 2026, 06:13 | 963,681 | -63 |
| 6 Aug 2026, 00:41 | 963,744 | first reading |
1,318 posts held, back to 2 July 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 77 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 12 August 2026 |
|---|---|
| Posts held | 1,318 (2 July 2026 – 12 August 2026) |
| Views total | 254,552,050 |
| Reactions total | 1,938,278 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 17:35 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.
Lifetime counters from Telegram’s own channel header, read 12 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.
How fast this channel’s own posts pick up views, from re-reading them repeatedly in the hours and days after they were published rather than the single reading most entries on this register get. Coverage is early and only a small minority of channels hold it at all — a gap in this section means the post has not been re-read again yet, not that nothing happened.
| Post | Readings | Latest reading | Curve | 24h reach | Half of last-observed views by |
|---|---|---|---|---|---|
| /423197 Aug 2026, 12:33 UTC | 126 minutes – 26 minutes old | 50,600 views ~814 reactions | no checkpoint reading yet | not yet at 24h | not measurable yet |
| /423187 Aug 2026, 12:30 UTC | 130 minutes – 30 minutes old | 64,800 views ~904 reactions | no checkpoint reading yet | not yet at 24h | not measurable yet |
| /423177 Aug 2026, 12:28 UTC | 132 minutes – 32 minutes old | 71,900 views ~886 reactions | no checkpoint reading yet | not yet at 24h | not measurable yet |
| /423167 Aug 2026, 12:27 UTC | 133 minutes – 33 minutes old | 74,900 views ~937 reactions | no checkpoint reading yet | not yet at 24h | not measurable yet |
| /423157 Aug 2026, 12:25 UTC | 2under a minute – 35 minutes old | 83,000 views ~938 reactions | no checkpoint reading yet | not yet at 24h | 17 minutesprovisional — final view count still climbing |
| /423147 Aug 2026, 12:04 UTC | 318 minutes – 56 minutes old | 119,000 views ~1,384 reactions | no checkpoint reading yet | not yet at 24h | 18 minutesupper bound — already past half at first reading · provisional — final view count still climbing |
| /423137 Aug 2026, 11:59 UTC | 323 minutes – 61 minutes old | 122,000 views ~643 reactions | 60 minutes: 122,000 | not yet at 24h | 23 minutesupper bound — already past half at first reading · provisional — final view count still climbing |
| /423127 Aug 2026, 11:55 UTC | 327 minutes – 65 minutes old | 127,000 views ~718 reactions | 60 minutes: 121,268 interp. | not yet at 24h | 27 minutesupper bound — already past half at first reading · provisional — final view count still climbing |
Curve is every standard checkpoint we hold a reading for (+1h, +3h, +6h, +12h, +24h, +48h, +7d after posting) — measured where a real reading landed close enough to that age, interpolated where it did not but readings on both sides let one be worked out between them. Nothing is ever extrapolated past the last real reading. Latest reading is the newest view and reaction count we hold for the post, side by side, so a gap between how views and reactions moved is visible without following it into the Observations section above. 24h reach is that one checkpoint on its own, labelled the same way. Half of last-observed viewsis the age at which a post’s view count crossed half of the highest figure we have read for it so far — an upper bound when the very first reading was already past half (we cannot see the actual crossing), and biased low while the post is still climbing, since “half of final” is dividing by a number that has not finished growing yet. Both caveats are printed inline wherever they apply, never silently dropped.
311,507 reactions across 192 posts, in 18 distinct kinds. The most used accounts for 51.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🙏 | 159,974 | 51.4% | |
| 🤬 | 113,548 | 36.5% | |
| 🔥 | 14,345 | 4.61% | |
| ❤ | 8,784 | 2.82% | |
| 😭 | 4,871 | 1.56% | |
| 👍 | 3,161 | 1.01% | |
| 😨 | 1,900 | 0.61% | |
| 😢 | 1,837 | 0.59% | |
| 🤯 | 979 | 0.314% | |
| 👎 | 910 | 0.292% | |
| 👀 | 456 | 0.146% | |
| 🙈 | 235 | 0.075% | |
| 🤝 | 181 | 0.058% | |
| 💔 | 80 | 0.026% | |
| 🤔 | 80 | 0.026% | |
| 👏 | 79 | 0.025% | |
| 🫡 | 78 | 0.025% | |
| ⚡ | 9 | 0.003% |
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 1,000 of the 1,000 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 2,048,972reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 11 July 2026 to 12 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 @war_monitor. 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 1,000 most recent posts we hold for this entry (the sample is capped at 1,000), published 11 July 2026 to 12 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.
Одеса / район - чисто, буде відбій
🙏1,110❤90👍60🤬22🫡6
🅿️ 2х КР Бандероль на Чорноморськ
🙏606🤬393🔥15🤯10😨6
🅿️ 3х КР Бандероль зміна на Чорноморськ / Лиманка
🙏548🤬380🔥18🤯11😭8
🅿️ Одеса - КР Бандероль на місто / Порт
🤬543🙏301😭20❤14🔥8
🅿️Пуски малогабаритних КР Бандероль у напрямку Одещини. Увага.
🤬1,350🙏580😭48🤯21👎9
Дорозвідка 2.0
🙏1,100❤117👀71🙈25🤬22
🪃 1х Кружляє в секторі вдсх / Кіпті.
🙏653🤬439🔥22❤15👎15
🪃 1х БпЛА з водосховища у напрямку Києва
🤬854🙏452❤30🤯25👎9
Київщина дорозвідка. Перегляд київщини дронами тривав з ночі.
🙏1,150🤬584👀53🤯53👎18
Київщина: 🔄 2х реактивних БпЛА у передмісті Києва Макарів / Наливайківка.
🙏864🤬545❤28😭27🔥20
Одеса мінус, загроза керованих ракет зберігається.
🙏968🤬295❤24👀23🤔18
❗️ 1х керована Х-59 у напрямку Одеса Порт.
🙏704🤬490❤30😭26🔥17
Showing the 12 most recent of 1,318 posts we hold for @war_monitor. 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.
Citation-graph rank — 7,798 of 1,151,006entries 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.
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 17 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.
Telegram’s own answer, not this register’s.When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 8 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 170 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
9 domainsthis channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.
A Wikidata item names this Telegram handle as belonging to the entity it describes. This is Wikidata’s claim, not a verification made by this register — nobody here confirmed that the account is genuinely operated by the entity named. Wikidata content is CC0; every fact below is dated to when it was read from Wikidata, not to when the association was first made there.
| Label | No label recorded on this Wikidata item |
|---|---|
| X / Twitter | @war_monitor_ua |
This handle named by sources this register does not control and did not measure — each shown exactly as found, attributed by name, dated to when it was read.
Wikipedia
3 Wikipedia articles name this handle in its article text, found by searching for a t.me link inside the article source. A citation is a notability signal, not a verification: nobody here confirmed the cited post is genuine or still says what the article quotes. Article text is CC BY-SA 4.0, Wikipedia contributors; snippets below are short excerpts.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“monitor” (@war_monitor), 965,270 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/war_monitor.
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.