Daily intelligence

UAF Deep Strikes Degrade Sloviansk Refinery Amid RF Fuel Market Emergency; RF Escalates Targeting of Ukrainian Rail and Naval Nodes

Published Intelligence Summary & Geospatial Analysis
Report number
724

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) expanded their deep-strike interdiction campaign, successfully targeting the Sloviansk Oil Refinery in Krasnodar Krai and exacerbating systemic Russian Federation (RF) fuel constraints. RF authorities enacted emergency stabilization measures, reducing mandatory domestic gasoline exchange sales to 10% while considering a total ban on diesel exports. Minor fuel shortages have subsequently been reported in the Belgorod and Moscow regions.

In response, RF forces initiated precision strikes targeting UAF asymmetric and logistical capabilities. Multi-wave ballistic strikes hit the "AB Technologies" plant in Kyiv, while tactical aviation and drone strikes focused on UAF rail logistics in Kharkiv and special operations infrastructure in Mykolaiv Oblast. Concurrently, the RF is accelerating domestic political consolidation, proposing frontline military correspondents and combat personnel for leadership positions within the United Russia party.

Operational Updates

  • Northern/Northeastern Sector (Kharkiv/Sumy): RF OWA-UAVs struck a residential building and a commercial gas station in the Shevchenkivskyi district, Kharkiv (no casualties, three vehicles damaged). RF forces targeted the "Zvezda" and "Impuls" chemical plants in Shostka and fuel depots in Akhtyrka, Sumy Oblast, degrading local industrial capacity. UAF OWA-UAVs destroyed three RF locomotives on the Malinovka-Lozova rail line. Weather in Kharkiv (23.6°C, wind 3.7 m/s, 26% cloud cover, 0.0 mm precip) provides optimal conditions for sustained ISR and OWA-UAV sorties.
  • Central/Eastern Sector (Kyiv/Donetsk): RF forces launched a coordinated ballistic missile strike ("Zircon", "Iskander-M") against Kyiv, impacting the "AB Technologies" defense plant and transport infrastructure in Brovary. Elements of the UAF 42nd OMBr successfully destroyed an RF Giatsint-S self-propelled artillery system in the Novopavlivka direction via precision counter-battery fire. Weather in Pokrovsk (25.2°C, wind 4.4 m/s, 52% cloud cover, 0.0 mm precip) remains permissive for tactical aviation.
  • Southern Sector (Zaporizhzhia/Mykolaiv/Krasnodar): UAF long-range drones struck the Sloviansk Oil Refinery in Krasnodar Krai, causing massive fires at the reservoir park and primary processing units. RF forces claim the capture of Pysantsy and Novoselivka on the Zaporizhzhia/Dnipropetrovsk border, attempting to bypass UAF fortifications. RF "Geran-2" OWA-UAVs struck the UAF "South" Special Operations Center near Prybugske (Mykolaiv). Weather in Zaporizhzhia (28.2°C, wind 5.0 m/s, 8% cloud cover) supports high-tempo FPV saturation.

SAR Intelligence (Satellite Data)

  • High Priority: Critical anomaly deviations were detected at the 196th Separate Fuel Automobile Battalion (Score: 5.67, Z: 1.41), 8th Separate Bridge Railway Battalion (Score: 0.63, Z: 2.68), 55th Arsenal GRAU (Score: 0.60, Z: 4.24), and the 702nd Logistics Center (Score: 0.37, Z: 4.84). Additionally, a training ground in Crimea (45.7522, 34.6606) registered a severe anomaly (Score: 6.98).
  • Analysis: Elevated SAR anomaly scores at major RF fuel, railway, and logistics nodes strongly correlate with emergency sustainment operations and rerouting following successful UAF deep strikes on energy and transport infrastructure. Baseline activity at numerous other nodes remains stable (scores near 0.0), indicating no significant positional shifts at those specific garrisons.

Equipment & Losses

  • RF Logistics: Three locomotives destroyed on the Malinovka-Lozova line; two locomotives destroyed in Zaporizhzhia. Severe damage confirmed at Sloviansk Oil Refinery.
  • RF Artillery: One Giatsint-S 152mm SPG destroyed near Novopavlivka.
  • UAF Defense Industrial Base: Unquantified damage to "AB Technologies" facility in Kyiv (produces "Flamingo" missiles) and chemical plants in Shostka.
  • RF Manpower: Systemic medical breakdown reported in the 83rd Motorized Rifle Regiment (Kamenka) convalescent facilities, indicating potential severe manpower rehabilitation bottlenecks.

Confidence Check

  • HIGH: UAF strikes on Sloviansk refinery; RF ballistic strikes on Kyiv (AB Technologies); UAF Giatsint-S destruction; RF fuel market policy adjustments.
  • MEDIUM: RF tactical advances in Pysantsy/Novoselivka; UAF strikes on RF locomotives; deployment of RF jet-powered UAVs in the Northern sector.
  • LOW: UNCONFIRMED RF claims of UAF GUR leadership casualties and USV destruction in Prybugske; UNCONFIRMED claims of total destruction of the Slavyansk refinery processing columns; UNCONFIRMED claims of physical sabotage of Alabuga SEZ by "Black Spark."

The Bottom Line

The UAF deep-strike campaign is successfully inducing structural deficits within the RF domestic fuel market, forcing Moscow to implement emergency economic controls. In retaliation, RF forces are prioritizing the degradation of UAF mobility and asymmetric strike capabilities by targeting rail logistics and naval special operations nodes. Watch for localized UAF logistical friction in the Sumy sector due to strikes on chemical and fuel distribution hubs, and monitor the RF's ability to maintain high-tempo mechanized assaults amidst spreading fuel distribution disruptions and internal security amidst spreading fuel distribution failures.

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 Jun 2026, 15:03 UTC
Map revision comparison

Against the previous report from 27 Jun 2026, 15:03 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

4 visuals
Open full size
Nightwatch daily report #724: Novoselivka area

Geospatial Analysis

17 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 17 places with coordinates
Geocoded places in report 724
PlaceCountryLatitude, longitudeCopy
Sloviansk Oil RefineryRussia45.6415289, 39.7055977
KyivUkraine50.0529506, 30.7667133
AB Technologies PlantUkraine50.0529506, 30.7667133
KharkivUkraine50.00201269999999, 36.3073994
ShostkaUkraine51.8757044, 33.4966152
AkhtyrkaUkraine50.3150962, 34.9005644
Malinovka-Lozova Rail LineUkraine48.00894073386306, 37.53316428635225
BrovaryUkraine50.511083, 30.7909
NovopavlivkaUkraine47.558712, 37.4402512
PysantsyUkraine47.8388, 35.139567
NovoselivkaUkraine47.61654000000001, 35.9986399
PrybugskeUkraine46.975033, 31.994583
196th Separate Fuel Automobile BattalionRussia61.52401, 105.318756
8th Separate Bridge Railway BattalionRussia61.52401, 105.318756
55th Arsenal GRAURussia61.52401, 105.318756
702nd Logistics CenterRussia61.52401, 105.318756
83rd Motorized Rifle RegimentRussia45.6415289, 39.7055977

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.