Daily intelligence

UAF Air Force C2 Disrupted by Anti-Corruption Purge Amid Intensifying Deep Strikes and New Russian 100km Munition Threat

Published Intelligence Summary & Geospatial Analysis
Report number
584

At a glance

Counts of the stored claim records and follow-up, not a summary of the narrative. How to read these labels

Coverage window
Not stored for this report.
Follow-up investigation
None stored for this report.
Claim records by status
This report has no claim records.
Claim records by confidence
This report has no claim records.
SAR measurements
None supplied to this report. No SAR measurements for this period does not mean that monitored sites were unchanged.
Frontline map data
Age of the map data is not available.

Read with these limits in mind

  • This report is machine-generated from open sources and may contain errors.
  • A source’s publication time is not the time of the event it describes.
  • Frontline map data can lag the reporting period; map dates do not establish when territory changed.
  • No SAR measurements for this period does not mean that monitored sites were unchanged.

Intelligence Summary

Machine-generated narrative. Labels inside it are written by the model. How to read these labels

Strategic Overview

Operational tempo over the last 12 hours is characterized by a high-intensity exchange of deep-rear precision strikes and significant internal security actions. The Security Service of Ukraine (SBU) detained the AFU Air Force Logistics Commander in a major anti-corruption operation regarding defense fortifications, introducing short-term friction into UAF airfield hardening efforts.

Concurrently, both forces are compensating for severe "Rasputitsa" (mud) conditions that are stalling mechanized maneuver. Russia is bridging its strike capabilities with a newly announced 100km+ guided munition and maximizing heavy FAB yields against static defenses in the Donbas. In response, Ukrainian deep strikes and Special Operations Forces (SSO) continue to successfully degrade Russian energy infrastructure, rear logistics, and strategic air defense networks in occupied Crimea.

Operational Updates

  • Northern Sector (Kharkiv/Sumy): UAV ingress persists with a confirmed strike in the Kyivskyi district of Kharkiv. Russian KAB strikes are targeting northern Sumy. Low visibility conditions in Vovchansk (1.0°C, fog, 100% cloud cover) continue to severely restrict optical ISR while favoring low-altitude UAV navigation.
  • Eastern Sector (Donetsk/Luhansk): High-intensity positional combat continues. Russian forces deployed a high-yield FAB-3000 munition against UAF defensive nodes in Kostiantynivka. Saturated ground and weather in Pokrovsk (2.9°C, overcast) are preventing off-road mechanized exploitation. Russian sources issued an unconfirmed claim of capturing Krasnoarmiisk (Pokrovsk), which remains uncorroborated by independent or UAF sources.
  • Southern Sector (Zaporizhzhia/Kherson/Odesa): A Russian high-speed ballistic missile struck Mayaky (Odesa Oblast), temporarily disrupting local logistics. In the Stepnohirsk area, UAF GUR Special Unit "Artan" initiated localized offensive armored maneuvers. Ground conditions in Orikhiv (3.9°C, light rain, wind 3.3 m/s) remain highly restrictive to heavy armor.
  • Deep Rear & Counter-Logistics: The UAF 80th Air Assault Brigade destroyed a Russian logistics and UAV warehouse in Kursk Oblast. A Ukrainian deep strike targeted the "Dorogobuzh" plant in Smolensk, resulting in 4-7 reported fatalities and highlighting gaps in Russian mid-range air defense protecting industrial sites.

SAR Intelligence (Satellite Data)

  • High Priority: None currently identified.
  • Analysis: Routine SAR monitoring of 10 locations, including the 49th Combined Arms Army HQ and several airbases (AB Zernograd, AB Khanskaya, AB Borisoglebsk), yielded diff_scores between 0.00 and 0.71. A score near 0 indicates stable, baseline activity with no significant departure or staging anomalies, not an abandoned site. High noise interference (0.75-0.91), likely due to persistent snow and wetness, degraded collection confidence over the Air Defense Radars (Smolensk) and the 721st Training Center GRAU.

Equipment & Losses

  • Confirmed: 1 Russian S-400 "Triumph" and 1 Pantsir-S1 air defense system destroyed by UAF SSO thermal-guided strikes in Sofiivka, Crimea.
  • Confirmed: 1 large Russian logistics warehouse (ammunition/drones) destroyed by the UAF 80th Air Assault Brigade in Kursk.
  • Confirmed: 1 UAF pickup truck destroyed in the Shevchenko area, indicative of persistent tactical FPV threats to "last-mile" logistics.
  • Sighting: Ukrainian intelligence confirms approximately 1,700 citizens of African nations are actively integrated into Russian military formations.
  • Development: Kalashnikov Concern announced a new tactical guided munition with a range exceeding 100km.
  • Development: The Ukrainian MoD initiated a ₴1.6 billion project to deploy 4,000 km of anti-drone netting along critical Ground Lines of Communication (GLOCs).

Confidence Check

  • HIGH: SBU detentions of AFU Air Force logistics leadership; UAF deep strikes on the Smolensk Dorogobuzh plant; ballistic strike on Mayaky; implementation of UAF anti-drone netting.
  • MEDIUM: UAF SSO destruction of S-400/Pantsir systems in Crimea; technical validity of the new Russian 100km+ guided munition.
  • LOW: Russian claims regarding the capture of Krasnoarmiisk (Pokrovsk); uncorroborated atrocity footage circulated by Russian channels in the Zaporizhzhia sector; Russian "Vostok" claims of "massive destruction" of UAF reserves in Dnipropetrovsk.

The Bottom Line

The immediate operational environment remains defined by adverse weather locking mechanized units to paved roads, shifting the burden of advance entirely to standoff munitions and UAVs. The SBU's anti-corruption purge within the Air Force Logistics Command is a critical internal security event that may temporarily disrupt the hardening of Ukrainian airfields against inbound ballistic and UAV threats. Intelligence requirements should prioritize verifying the defensive integrity of the Pokrovsk axis following unconfirmed Russian capture claims and assessing the technical parameters of the new 100km Russian munition.

Legacy provenance

This archived report predates claim-level evidence records. Treat its confidence labels as editorial assessments rather than independently verifiable citations.

Frontline context

Territorial control and recent changes shown by DeepState.

Report 25 Feb 2026, 15:06 UTC
Map revision comparison

Against the previous report from 24 Feb 2026, 15:02 UTC, bright red is newly marked Russian-occupied and green is no longer marked occupied. For the infiltration area, yellow is this report and cyan is the previous report.

Compare on map
Frontline change measurements are unavailable for this briefing.

Report Visuals

5 visuals
Open full size
Nightwatch daily report #584: Orikhiv area

Geospatial Analysis

12 locations identified

Historical reconstruction from source editions available by report time.

Places and data export

Coordinates come from geocoding place names found in the report. They locate the named place, not the event described there. Latitude and longitude are WGS 84 decimal degrees.

Show 12 places with coordinates
Geocoded places in report 584
PlaceCountryLatitude, longitudeCopy
KharkivUA50.00201269999999, 36.3073994
SumyUA50.9077, 34.7981
VovchanskUA50.284234, 36.9329429
KostiantynivkaUA48.52394289999999, 37.7075811
Pokrovsk (Axis)UA48.282193, 37.1847804
MayakyUA46.41444329999999, 30.269107
Stepnohirsk AreaUA47.5869326, 35.358148
OrikhivUA47.5658802, 35.7876745
Kursk (Warehouse)RU51.7482395, 36.1947023
Dorogobuzh PlantRU54.9469401, 33.3679625
SofiivkaUA45.27462149999999, 35.1258454
Shevchenko AreaUA47.84899619999999, 35.2403034

How to read the labels

Labels on this page come from three separate mechanisms. A label from one does not mean the same as a similar word from another.

1. In the narrative

Machine-generated narrative. Labels inside it are written by the model.

Unconfirmed:
Written by the model. Its instruction is to mark claims that rest on a single source.
Confidence: HIGH / MEDIUM / LOW
Written by the model. The report stores no definition of these levels, and they are not computed from the claim records. Do not read them as the record confidence above.

2. On claim records: confidence

Record confidence is a threshold on a number stored with the source observation. It is not a probability that the event happened. The follow-up investigation may lower it and never raises it.

HIGH confidence
The status is Independently corroborated, Geolocated or Imagery corroborated, and the stored confidence of the supporting observation is at least 0.75.
MEDIUM confidence
The stored confidence of the supporting observation is at least 0.5 and the rule for HIGH is not met.
LOW confidence
The stored confidence of the supporting observation is below 0.5.

2. On claim records: status

Machine-selected records from the source ledger, labelled by fixed rules. They are a separate selection and are not a list of the sources behind the narrative above.

Single-source claim
One retained source observation supports the record, from a sender that is not on the list of official bodies.
Official claim
One retained source observation, from a sender whose name matches a keyword list of official bodies. It says who made the claim, not that the claim is verified.
Multiple reports, same origin
Several retained observations that do not meet the rule for independent corroboration. They are treated as one origin.
Independently corroborated
At least two distinct source documents from at least two differently named senders. The rule compares sender names and document fingerprints. It does not establish that the senders had separate access to the event, and a repost under another name can satisfy it.
Geolocated
One retained observation carrying coordinates with a geolocation confidence of at least 0.5. It concerns the location only, not the cause or the outcome.
Imagery corroborated
Imagery supports the observation. It does not by itself establish cause or intent.
Analyst assessment
A Nightwatch assessment rather than a directly observed fact.
Contested
Set by the follow-up investigation: material source accounts remain in conflict.
Corrected
Set by the follow-up investigation: the record was changed after the investigation reached a definitive answer.
Insufficient evidence
Set by the follow-up investigation: the available evidence does not support the record as first labelled.

3. In the follow-up investigation

Machine-run follow-up on one selected claim record. Sources listed include material that was retrieved and not used.

Confirmed
The investigation reached a definitive answer supporting the selected claim. The report was rewritten after it.
Refuted
The investigation reached a definitive answer against the selected claim. The report was rewritten after it.
Materially refined
The investigation reached a definitive answer that changes the selected claim in a material way. The report was rewritten after it.
Inconclusive
The investigation did not reach a definitive answer. The report text was kept; the investigation could only attribute, hedge or lower confidence. Individual findings inside it can still carry their own outcome.

Each finding has its own outcome and a confidence written by the model. That confidence is in the finding as worded, which may itself be a statement that something is unknown.

Kinds of investigation source

External web page
A web page retrieved during the follow-up investigation. Its address is stored and linked.
Source observation behind a claim record
A source observation the claim records were built from. No address is stored for it.
Nightwatch archive item
An item found by searching the Nightwatch archive during the investigation. It may be unrelated to the question. No address is stored for it.