Daily intelligence

UAF Interdicts Kherson Logistics

Published Intelligence Summary & Geospatial Analysis
Report number
609

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

Russian tactical aviation (VKS) is employing synchronized Guided Aerial Bomb (KAB) and Shahed-type UAV saturation tactics over Zaporizhzhia, exploiting clear weather conditions. Simultaneously, the Ukrainian Armed Forces (UAF) have maintained successful deep-strike interdiction, destroying a key ammunition depot in the occupied Kherson sector and maintaining sustained pressure on air defense networks over Belgorod (RF).

Operational Updates

  • Southern Sector (Zaporizhzhia/Kherson): UAF deep reconnaissance facilitated a precision strike destroying a Russian ammunition depot in Solontsi, near occupied Oleshky, disrupting local supply chains. Over Zaporizhzhia, Russian forces launched a multi-vector KAB and Shahed UAV saturation attack to stress UAF air defenses. Weather in Zaporizhzhia (Orikhiv) is 15.2°C, clear (Code 0), with 2.4 m/s winds, optimizing conditions for stand-off aviation.
  • Eastern Sector (Donetsk/Luhansk): The General Staff reports 45 combat engagements with primary Russian offensive concentrations on the Huliaipole and Kostiantynivka axes. Analytical modeling indicates localized Russian advances near Berestky and Fedorivka Druha. The Russian Tsentr Group is actively surging heavy-lift logistical transport of BMP-2 armored vehicles to the sector. UAF units successfully employed the Sirko-S1 Unmanned Ground Vehicle (UGV) for casualty evacuation under fire.
  • Northeastern Sector (Kharkiv/Sumy/Bryansk): Sustained UAF projectile launches have forced continuous Russian air defense engagements over Belgorod city. A deep Russian UAV incursion was tracked transiting Sumy Oblast toward Romny, Terny, and Nedryhailiv. In the Kharkiv sector, Russian Akhmat Spetsnaz forces successfully engaged a UAF AHS Krab howitzer. Weather in Kharkiv (Vovchansk) is 12.8°C, clear, with 0.8 m/s winds.

Equipment & Losses

  • Confirmed Loss (Russian): Ammunition depot in Solontsi (Kherson Oblast) via UAF precision strike.
  • Confirmed Loss (UAF): AHS Krab self-propelled howitzer in the Kharkiv sector via Russian FPV drone strike.
  • Sighting (Russian): Heavy-lift deployment of BMP-2 armored vehicles to the Eastern sector by Tsentr Group.
  • Field Integration (UAF): Operational deployment of the Sirko-S1 UGV for active CASEVAC missions.

Confidence Check

  • HIGH: UAF strike on Solontsi ammunition depot; Russian KAB/UAV saturation of Zaporizhzhia.
  • MEDIUM: Extent of Russian tactical advances near Berestky and Fedorivka Druha; scale of Belgorod air defense interceptions.
  • LOW: Claims of Iranian leadership transition and imminent threats to the Strait of Hormuz (assessed as unconfirmed hybrid information noise).

The Bottom Line

Russian forces are capitalizing on dry, clear weather to execute high-tempo mechanized logistics and tactical air saturation across the contact line.

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 12 Mar 2026, 15:01 UTC
Map revision comparison

Against the previous report from 11 Mar 2026, 21:33 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 #609: Zaporizhzhia area

Geospatial Analysis

6 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 6 places with coordinates
Geocoded places in report 609
PlaceCountryLatitude, longitudeCopy
ZaporizhzhiaUkraine47.83928419999999, 35.13870970000001
SolontsiUkraine46.5693172, 32.6678429
AB OlenyaRussia69.214167, 33.37
BelgorodRussia50.5997134, 36.5982621
49th Combined Arms Army HQRussia47.3352415, 43.4257465
HuliaipoleUkraine47.6607145, 36.2732384

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.