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 the other topics.
Observations
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Content that also appears on other registered channels
Posts published here appear in near-verbatim form on 4 other registered channels. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
Matching posts — open both and compare (6 of the pairs behind the counts below)
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 2 of the 2 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 356 comparable posts for this entry, running 2 July 2026 to 8 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).
Recorded under the key clone_source, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
Growth
65 measurements spanning 97 days, net -4,757. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 956,988–974,311 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 65
Measured (UTC)
Subscribers
Change
11 Nov 2026, 11:41
958,987
-935
9 Nov 2026, 20:29
959,922
-222
8 Nov 2026, 08:57
960,144
+159
7 Nov 2026, 03:39
959,985
-267
6 Nov 2026, 04:05
960,252
-450
5 Nov 2026, 06:10
960,702
-539
4 Nov 2026, 06:18
961,241
-388
3 Nov 2026, 05:49
961,629
+731
2 Nov 2026, 05:37
960,898
+1,404
1 Nov 2026, 04:28
959,494
-245
31 Oct 2026, 07:16
959,739
-336
30 Oct 2026, 06:38
960,075
-17
29 Oct 2026, 06:47
960,092
-413
28 Oct 2026, 01:40
960,505
-381
26 Oct 2026, 23:25
960,886
-463
25 Oct 2026, 21:56
961,349
-627
24 Oct 2026, 20:59
961,976
-545
23 Oct 2026, 20:45
962,521
-770
22 Oct 2026, 23:07
963,291
-379
21 Oct 2026, 22:39
963,670
first reading
Engagement
3,457 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 257 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
23.1%
avg views ÷ 958,987 subscribers
Avg views / post
222,000
344 posts measured
Reaction rate
0.836%
reactions ÷ views · ER floor
Posts in window
345
of 3,457 held
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.
What these figures were computed from
Window
Rolling 30 days · latest post in window 10 November 2026
Posts held
3,457 (2 July 2026 – 10 November 2026)
Views total
76,324,600
Reactions total
638,438
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
11 Nov 2026, 13:33 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.
What this channel posts
Photos
≈2,080
Videos
≈774
Links
≈861
Lifetime counters from Telegram’s own channel header, read 11 November 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.
Video runtime
4m 33s
Average length
39s
Measured directly from 7 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.
View velocity
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.
8 most recently posted, with a view-velocity reading
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 views is 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.
Reaction mix
1,198,829 reactions across 998 posts, in 22 distinct kinds. The most used accounts for 46.6% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🙏
558,673
46.6%
🤬
445,440
37.2%
❤
89,673
7.48%
😭
24,233
2.02%
🔥
14,694
1.23%
😢
12,999
1.08%
👍
12,484
1.04%
😁
7,210
0.601%
😨
6,999
0.584%
💯
6,213
0.518%
🤯
5,396
0.45%
👎
4,620
0.385%
👀
4,128
0.344%
🙈
1,934
0.161%
🫡
1,401
0.117%
💔
587
0.049%
🤣
517
0.043%
🤔
505
0.042%
👏
459
0.038%
🤝
384
0.032%
2 further kinds
280
0.023%
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 999 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 1,198,829 reactions 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 20 September 2026 to 10 November 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.
Telegram Stars
Stars received
801
across the posts below
Posts paid on
220
of 999 we hold a reading for · 22%
Most on one post
75
single highest reading
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 20 September 2026 to 10 November 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.
Recent posts
Telegram’s own ‘edited’ marker: 2 of 345 posts held from the last 30 days (0.58%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
Загальна оцінка загроз для України на ніч 09 листопада.
🟩 Загрози з боку стратегічної авіації відсутні.
🟨 Загроза ударних БпЛА на низькому рівні.
Реактивні та ДВЗ-БПЛА атакують територію України з Курщини через Сумщину та з Донеччини через Дніпровщтну.
Курс Західний.
Продовж ночі очікуються додаткові пуски.
🟨 Балістичні загрози на ніч нижче середнього.
Сили оборони активно протидіють ворожим намірам та регулярно з…
Друзі, збираємо кошти на купівлю генератора, планшету, та багатьох розхідників для 3D друку та відновлення тестерів, для двох бригад та майстерні.
🎯 Ціль: 92 000.00 ₴
🔗 Посилання на Банку
https://send.monobank.ua/jar/2xZvMCVCqD
💳 Номер картки Банки
4874100036104373
Вдячні за вашу підтримку та допомогу!
Showing the 12 most recent of 3,457 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.
Forward network
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.
Mentions
Named by 36 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
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.
Channels Telegram recommends alongside this one
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.
Appears in Telegram’s recommendations for other channels
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.
🇺🇦🏴☠️ "ТРАВ" - 🚨 Тривоги / 🚀 Ракети / 🛩 Авіація / 🇺🇦 Війна в Україні 🇺🇦🏴☠️ @wartrav · 18,944 Telegram ranks this channel #1 of 79 here — alongside 78 others — read 23 September 2026
monitorwar @monitoringwar · 26,432 Telegram ranks this channel #1 of 84 here — alongside 83 others — read 12 September 2026
D7 NEWS | Демократична Сокира @D7_channel · 35,201 Telegram ranks this channel #1 of 74 here — alongside 73 others — read 2 September 2026
ППО UA | РАДАР📡 @PpoUaRadar0 · 35,882 Telegram ranks this channel #1 of 79 here — alongside 78 others — read 31 August 2026
Web3Forces News 🇺🇦 @web3forces · 41,859 Telegram ranks this channel #1 of 77 here — alongside 76 others — read 31 August 2026
🇺🇦 Служба Моніторингу України @monitorsmy · 57,117 Telegram ranks this channel #1 of 81 here — alongside 80 others — read 27 August 2026
Моніторинг | Україна @monitor_ukr · 62,932 Telegram ranks this channel #1 of 87 here — alongside 86 others — read 21 August 2026
monitoring @monitorwarr · 85,253 Telegram ranks this channel #1 of 90 here — alongside 89 others — read 18 August 2026
Aeris Rimor @AerisRimor · 163,362 Telegram ranks this channel #1 of 88 here — alongside 87 others — read 14 August 2026
Повітряний простір | Напрямок ракет @ukraine_pyxx · 208,763 Telegram ranks this channel #1 of 59 here — alongside 58 others — read 13 August 2026
Тотальна Зрада @totallzrada · 266,865 Telegram ranks this channel #1 of 78 here — alongside 77 others — read 10 August 2026
🔊⚠️єРадар | Повітряна тривога | Ракетна небезпека @eRadarrua · 410,896 Telegram ranks this channel #1 of 83 here — alongside 82 others — read 10 August 2026
Повітряні Сили ЗС України / Air Force of the Armed Forces of Ukraine @kpszsu · 939,064 Telegram ranks this channel #1 of 87 here — alongside 86 others — read 8 August 2026
Николаевский Ванёк @vanek_nikolaev · 2,578,242 Telegram ranks this channel #1 of 84 here — alongside 83 others — read 7 August 2026
Командування Повітряних Сил @ComAFUA · 20,674 Telegram ranks this channel #2 of 85 here — alongside 84 others — read 25 September 2026
ППО РАДАР 🇺🇦 | Карта тривог | Моніторинг @PpoUaRadar · 27,494 Telegram ranks this channel #2 of 81 here — alongside 80 others — read 9 September 2026
КМВА (Київська міська військова адміністрація) @VA_Kyiv · 54,515 Telegram ranks this channel #2 of 92 here — alongside 91 others — read 24 August 2026
Ракети @ua_rockets · 71,850 Telegram ranks this channel #2 of 81 here — alongside 80 others — read 21 August 2026
єТривога @UkraineAlarmSignal · 84,577 Telegram ranks this channel #2 of 88 here — alongside 87 others — read 18 August 2026
🇺🇦 Київська обласна військова адміністрація @kyivoda · 84,320 Telegram ranks this channel #2 of 93 here — alongside 92 others — read 18 August 2026
ППО радар | Напрямок ракет | Напрямок шахедів | @mon1tor_ua · 264,047 Telegram ranks this channel #2 of 90 here — alongside 89 others — read 14 August 2026
Телебачення Торонто @torontotv · 111,949 Telegram ranks this channel #2 of 93 here — alongside 92 others — read 14 August 2026
Повітряна Тривога @air_alert_ua · 226,758 Telegram ranks this channel #2 of 86 here — alongside 85 others — read 10 August 2026
🚀 РАКЕТНА неБЕЗПЕКА 🚀 @rocket_danger_lviv · 398,678 Telegram ranks this channel #2 of 82 here — alongside 81 others — read 10 August 2026
This channel appears in 1,148 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.
Domains linked from posts
9 domains this 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.
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.
Monitor (веб-ресурс)(uk.wikipedia.org) “…ua logo.jpg
|оф назва = Моніторинг ворожої авіації
|url = {{URL|https://t.me/war_monitor}} {{URL|https://bsky.app/profile/monitor.bsky.social}}
{{URL|https://threads…” read 1 November 2026
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 11 November 2026 — this
entry's latest reading, not the date you are reading this.
“monitor” (@war_monitor), 958,987 subscribers as measured 11 November 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.
