Daily intelligence

UAF Deep Strikes Extend to Leningrad Oil Infrastructure Amid High-Intensity Eastern Attrition

Published Intelligence Summary & Geospatial Analysis
Report number
622

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

The most critical operational development is the confirmed expansion of the Ukrainian Armed Forces (UAF) deep-strike campaign, evidenced by a successful uncrewed aerial vehicle (UAV) strike against the Transneft oil terminal in Primorsk, Leningrad Oblast. This event, corroborated by visual evidence of sustained fires, highlights a growing UAF capacity to stress Russian economic and logistical nodes well beyond the immediate theater of operations.

On the frontline, operations remain defined by intense drone-led attrition and small-unit infantry engagements. UAF units are successfully interdicting Russian forces across the eastern and southern sectors while exploiting significant Russian internal security lapses. Notably, a leak within the Russian 44th Corps compromised the coordinates of OTRK Iskander-M missile systems in Voronezh and Kursk, offering UAF forces critical counter-battery intelligence.

Theater weather continues to constrain specific operational capabilities. Overcast conditions in Zaporizhzhia (12.7°C, 97% cloud cover) and Donetsk (11.2°C, 95% cloud cover) severely limit high-altitude optical intelligence, surveillance, and reconnaissance (ISR), forcing a continued reliance on low-altitude tactical drones despite moderate winds (5.1 - 5.4 m/s) affecting light frame stability.

Operational Updates

  • Northern Sector / Russian Rear: UAF UAVs successfully struck the Transneft oil terminal in Primorsk, causing a large-scale fire and demonstrating a significant reach into the Russian rear. Sensitive deployment locations for Russian missile units of the 44th Corps in the Voronezh and Kursk oblasts were leaked to Ukrainian channels, presenting high-value targeting opportunities.
  • Eastern Sector (Donetsk/Pokrovsk): UAF SBU "Alpha" forces neutralized Russian personnel in trench engagements near Donetsk using first-person view (FPV) drones. The 425th "Skelya" Battalion successfully disrupted Russian infiltration attempts using FPV and artillery strikes across the Oleksandrivka, Pokrovsk, and Lyman sectors. Elements of the 132nd Separate Reconnaissance Battalion (7th Air Assault Corps) captured a Russian soldier near Oleksandrivka. Furthermore, UAF captured personnel from the Russian 30th Separate Motorized Rifle Brigade, acquiring valuable HUMINT regarding recruitment standards. A Russian-occupied shelter was targeted and struck in Ternuvate.
  • Southern Sector (Zaporizhzhia/Huliaipole): Elements of the UAF 1st Battalion, 1st Separate Assault Battalion (Kotsiubailo) achieved high-lethality neutralization of approximately 10 Russian personnel in a wooded area on the Huliaipole front. Russian aviation launched guided aerial bombs (KABs) targeting the Zaporizhzhia region.
  • Internal Security: The Security Service of Ukraine (SBU) neutralized a Hungarian military intelligence network in Zakarpattia. The SBU identified Zoltan Andre as the handler utilizing financial incentives to recruit assets for mapping regional military defenses.
  • Central Ukraine: An explosion of undetermined origin was reported in Dnipro; battle damage assessment (BDA) is pending.

SAR Intelligence (Satellite Data)

  • High Priority: An anomalous increase in activity was detected at AB Olenya (Current Score: 1.19, Z-Score: 1.26, Percentile: 90.0%). This represents a critical deviation from historical baselines for this strategic aviation base.
  • Moderate Priority: Elevated activity was detected at a FSB Border Outpost (Score: 1.36). Conversely, activity at the 573rd Separate Reconnaissance Artillery Battalion and 227th Artillery Brigade fell to 0.00, indicating a deviation from baseline behavior.
  • Analysis: The elevated SAR score at AB Olenya strongly indicates an increase in operational tempo, likely associated with aircraft readiness or munitions loading for strategic bomber elements. The sharp drop in activity metrics at the identified artillery brigade locations suggests localized Emission Control (EMCON) or recent forward redeployment, not base abandonment.

Equipment & Losses

  • Confirmed Russian Losses: 10 personnel neutralized by UAF drone operators near Huliaipole; 2 personnel neutralized by SBU "Alpha" near Donetsk; infrastructure damage at the Transneft oil terminal in Primorsk.
  • Confirmed Russian Captures: Personnel from the 30th Separate Motorized Rifle Brigade; one soldier captured by the UAF 7th Air Assault Corps near Oleksandrivka.
  • Unconfirmed UAF Losses: Russian claims of destroying two UAF tanks in the Kupyansk sector; Russian claims of destroying a UAF "Jaga" armored vehicle during a night mission.

Confidence Check

  • HIGH: UAF strike on the Primorsk oil terminal; UAF 1st Assault Battalion multi-casualty strike in Huliaipole; capture of Russian personnel from the 30th MRB; SBU neutralization of the Hungarian intel network in Zakarpattia.
  • MEDIUM: The full operational impact of the leaked 44th Corps missile coordinates in Kursk/Voronezh; origin and specific target of the explosion in Dnipro.
  • LOW: Russian claims of UAF armor losses in Kupyansk; Iranian IRGC claims of a "75th wave" of Middle Eastern strikes amplified by Russian channels.

The Bottom Line

The UAF is effectively compounding its asymmetric advantages, combining highly lethal frontline drone defense with deep, operational-level strikes against Russian energy infrastructure in Leningrad. The Russian response is heavily reliant on glide bomb (KAB) strikes and information operations designed to project Western distraction in the Middle East. Over the next 12-24 hours, UAF air defense networks should anticipate retaliatory Iskander-M and low-altitude loitering munition strikes, particularly as Russian forces exploit the heavy overcast conditions persisting across the eastern and southern axes. The critical SAR anomaly at AB Olenya warrants immediate, sustained monitoring for long-range aviation sorties.

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

Against the previous report from 22 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

5 visuals
Open full size
Nightwatch daily report #622: Oleksandrivka area

Geospatial Analysis

7 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 7 places with coordinates
Geocoded places in report 622
PlaceCountryLatitude, longitudeCopy
PrimorskRussia60.36627000000001, 28.6061221
AB OlenyaRussia69.214167, 33.37
VoronezhRussia51.6683487, 39.19192880000001
KurskRussia51.7482395, 36.1947023
OleksandrivkaUkraine48.7076749, 36.9218933
HuliaipoleUkraine47.6607145, 36.2732384
ZakarpattiaUkraine48.6208, 22.287883

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.