Daily intelligence

UAF Deep Strikes Ignite Ust-Luga Port Facility as Russian Forces Exploit Kupyansk Sector

Published Intelligence Summary & Geospatial Analysis
Report number
628

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

Ukrainian Armed Forces (UAF) deep-strike capabilities have achieved a significant kinetic impact on the Russian energy and logistics sector, successfully igniting the Ust-Luga port facility in the Leningrad region. Concurrently, international diplomatic friction continues as Slovakian Prime Minister Robert Fico threatens to veto the 20th EU sanctions package against the Russian Federation. In the Baltic zone, the Finnish Air Force has confirmed that a crashed UAV in their territory was of Ukrainian origin, likely representing navigational spillover from the Leningrad strike campaign.

Operational tempo across the contact line is heavily influenced by deteriorating weather. Forecasted light rain and heavy overcast conditions (100% cloud cover across all primary sectors) will temporarily degrade high-altitude optical ISR and FPV drone operations, likely shifting tactical engagements toward close-quarters infiltration and static artillery exchanges.

Operational Updates

  • Northern / North-Eastern Sector (Kharkiv / Kupyansk / Sumy): The Russian Ministry of Defense claims the capture of Kovsharovka, with tactical maps indicating advances southeast of Kupyansk. Heavy defensive fighting by UAF units is reported near Petropavlovka and Kurilovka. Russian "Sever" Group (11th Army Corps) artillery is actively targeting UAF UAV command posts using Giatsint-S/B systems. Conversely, the Russian "Zapad" Group is reportedly experiencing significant C2 friction and struggles to verify frontline positions. Russian UAVs were detected transiting Bilopillia and Terny toward central Ukraine. Weather in Kharkiv (16.9°C, 4.9 m/s wind, 100% cloud cover) is forecasting light rain (25% probability).
  • Eastern Sector (Donetsk / Luhansk): Russian forces are pressing the Dobropolye salient, targeting Novopavlovka, Belitskoye, and Rodinskoye, with fluid frontline activity noted near Hryshyne. The UAF 59th Motorized Infantry Brigade is maintaining active counter-drone operations. Russian reconnaissance units ("Razvedosy") are increasingly integrating Unmanned Ground Vehicles (UGVs) for logistics across water obstacles to mitigate technical personnel losses. A Russian KAB strike on Kramatorsk resulted in three civilian fatalities. Weather in Pokrovsk (17.3°C, 4.6 m/s wind, 100% cloud cover) is forecasting rain (73% probability).
  • Southern Sector (Zaporizhzhia / Kherson / Kryvyi Rih): In the Huliaipole sector, the UAF 1st Separate Assault Regiment is utilizing direct tank fire to systematically reduce Russian concrete pillboxes. The UAF 7th Air Assault Corps continues to inflict high attrition on Russian infantry using coordinated drone swarms. The Russian 58th Combined Arms Army is conducting assault training in the occupied Zaporizhzhia region, anticipating future ground operations. Low-flying Russian loitering munitions are utilizing railway infrastructure near Kryvyi Rih for navigation. Weather in Zaporizhzhia (18.9°C, 3.8 m/s wind, 100% cloud cover) anticipates 4.3mm of rain (90% probability).

SAR Intelligence (Satellite Data)

  • High Priority: Critical anomalies indicating significant deviations from historical baseline activity were detected at the 10th Armament Base (Moscow Military District, Score: 0.67), the 216th Storage and Repair Base (Moscow Military District, Score: 0.67), and the 346th Separate Spetsnaz Brigade (Southern Military District, Score: 1.21).
  • Analysis: The elevated activity scores at the Moscow Military District logistics hubs and the 346th Spetsnaz Brigade suggest localized mobilization of technical assets or specialized personnel. Routine baseline monitoring (scores near 0.00) at the vast majority of other assessed locations indicates stable operational postures without widespread immediate displacement.

Equipment & Losses

  • Confirmed Infrastructure Damage: Significant, unextinguished fires reported at the Ust-Luga port facility (Leningrad region).
  • Civilian Casualties: Three civilian fatalities (including a minor) confirmed from a Russian KAB strike in Kramatorsk; one civilian fatality confirmed from a missile strike in Mykolaiv.
  • Tactical Claims: Unconfirmed Russian deployment of an aerial "interceptor drone." Russian 14th Spetsnaz Brigade claims the destruction of one UAF AFV near Zarnitsa (unconfirmed).

Confidence Check

  • HIGH: UAF drone strikes impacting Ust-Luga; Slovakian veto threats regarding EU sanctions; civilian casualties in Kramatorsk and Mykolaiv; Finnish confirmation of Ukrainian UAV origin.
  • MEDIUM: Russian capture of Kovsharovka; Russian Zapad Group C2 friction in the Kupyansk sector; Russian artillery destruction of UAF UAV command posts in Kharkiv.
  • LOW: Russian deployment of effective "interceptor drones"; Wagner Istra's 30 million ruble bounty on RDK leadership (assessed as psychological operation).

The Bottom Line

The successful strike on Ust-Luga reinforces the efficacy of the UAF's deep-strike interdiction strategy against Russian maritime logistics. On the ground, the critical operational variable over the next 12 hours will be the incoming rain across the Eastern and Southern fronts. UAF commands should prepare for localized, wet-weather Russian infantry probes designed to capitalize on the temporary grounding of UAF tactical ISR and FPV platforms, particularly in the Kupyansk and Kharkiv sectors where UAF UAV command nodes have been recently targeted.

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

Against the previous report from 28 Mar 2026, 15:01 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

2 visuals
Open full size
Nightwatch daily report #628: Kovsharovka area

Geospatial Analysis

5 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 5 places with coordinates
Geocoded places in report 628
PlaceCountryLatitude, longitudeCopy
Ust-LugaRussia59.6644191, 28.2792159
KovsharovkaUkraine49.6297207, 37.6810464
KramatorskUkraine48.738967, 37.58435
10th Armament BaseRussia55.7568721, 37.6150527
346th Separate Spetsnaz BrigadeRussia47.3352415, 43.4257465

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.