Daily intelligence

UAF Expands Deep Strike Campaign to Yaroslavl Refinery Amid Synchronized Russian Multi-Axis UAV Assault

Published Intelligence Summary & Geospatial Analysis
Report number
627

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

UAF deep strikes have expanded their operational radius, successfully targeting the Yaroslavl Oil Refinery (NPT) approximately 250km northeast of Moscow. This sustained pressure on the Russian energy sector has concurrently forced the energy firm Novatek to officially suspend operations at the Ust-Luga complex following previous strikes. In response to these deep-rear vulnerabilities, Russian forces have launched a synchronized, multi-axis UAV campaign, with loitering munitions entering via the northern Chernihiv corridor and simultaneously from the Black Sea toward Odesa, aiming to saturate Ukrainian air defense networks.

Strategically, Ukraine has bolstered its long-term sustainment by finalizing a 10-year defense partnership with Qatar, which is specifically focused on countering modern aerial threats and strengthening air defense. Additionally, a one-year agreement for diesel fuel supplies was secured, significantly mitigating future logistical vulnerabilities for UAF mechanized units.

Operational Updates

  • Northern Sector (Chernihiv / Sumy / Kharkiv): A new aerial threat vector was established as Russian UAVs crossed the Semenivka/Kholmy corridor on a southern heading, likely probing defenses toward central logistics hubs. Weather in Kharkiv (11.7°C, 1.4 m/s wind, overcast) is forecasted to transition to heavy fog (Code 45), which will severely degrade low-altitude drone reconnaissance over the next 6-12 hours.
  • Eastern Sector (Donetsk / Pokrovsk): Russian tactical aviation continues high-intensity Guided Aerial Bomb (KAB) strikes. Russian sources claim a tactical advance resulting in the capture of Brusovka, alongside unconventional infantry assaults in Konstantinovka utilizing electric scooters; both claims remain unconfirmed. Weather in Pokrovsk (15.8°C, 1.6 m/s wind, partly cloudy) will also see fog development, likely shifting combat dynamics to close-quarters infiltration.
  • Southern Sector (Zaporizhzhia / Kherson / Odesa): Multiple UAV waves from the Black Sea are maintaining a direct intercept course for Odesa, stressing southern Air Defense networks. Concurrently, Russian tactical aviation has initiated a new wave of KAB launches against the Zaporizhzhia sector. Conditions in Kherson (17.1°C, 4.0 m/s wind, mainly clear) currently facilitate highly permissive drone operations.

SAR Intelligence (Satellite Data)

  • High Priority: A critical anomaly was detected at an FSB Border Outpost (Score: 2.06 against a 0.75 historical baseline), representing a statistically significant deviation from standard operations.
  • Medium Priority: Minor activity deviations were recorded at AB Krasnodar, the 80th Separate Arctic Motor Rifle Brigade, and the 689th Command Intelligence Center GRU.
  • Analysis: The critical spike at the FSB Border Outpost requires immediate cross-cueing with SIGINT/IMINT to determine if this indicates localized border reinforcement, staging for cross-border raids, or a technical collection anomaly. A score of 0.00 at the vast majority of other monitored locations indicates that baseline operations remain stable with no evidence of sudden abandonment or massive deployment.

Equipment & Losses

  • Confirmed Russian Infrastructure Damage: Yaroslavl Oil Refinery (multiple fires reported); Ust-Luga energy complex (operations suspended by Novatek).
  • Confirmed Friendly Infrastructure: Water supply fully restored on the left bank of Kyiv following temporary grid instability.
  • Tactical Observations: Russian drone operators are confirmed to be integrating new "SD6" modems into FPV platforms to improve resistance against UAF Electronic Warfare.

Confidence Check

  • HIGH: UAF deep strikes on Yaroslavl and Ust-Luga impact; multi-axis UAV waves targeting Odesa and Chernihiv; Qatar defense pact and fuel supply agreements.
  • MEDIUM: Russian internal command friction (reports of extrajudicial killings within the 119th Regiment); specific operational downtime of the Yaroslavl refinery.
  • LOW: Russian claims regarding the capture of Brusovka; Russian use of electric scooters for a 40% control claim in Konstantinovka (assessed as an information operation).

The Bottom Line

The UAF's successful penetration of Russian integrated air defenses to strike Yaroslavl demonstrates a maturing deep-strike capability that directly threatens the logistical backbone of the Russian war effort. In the immediate 12-hour window, UAF air defense elements must prioritize mitigating the synchronized UAV probing attacks designed to identify coverage gaps between the Northern and Southern operational zones. Widespread forecasted fog across the Northern and Eastern fronts will temporarily suppress tactical aviation and ISR, presenting a brief window for UAF logistical repositioning and fortification.

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

Against the previous report from 27 Mar 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 #627: Odesa

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 627
PlaceCountryLatitude, longitudeCopy
Yaroslavl Oil RefineryRussia57.62607440000001, 39.8844708
Ust-LugaRussia59.6644191, 28.2792159
OdesaUkraine46.4845702, 30.7326047
ChernihivUkraine51.4982, 31.28935
FSB Border OutpostRussia61.52401, 105.318756
AB KrasnodarRussia45.036035, 38.97457060000001
PokrovskUkraine48.282193, 37.1847804

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.