Daily intelligence

UAF Strikes Gukovo Fuel Depot; RF Confirms Capture of Rai-Aleksandrovka

Published Intelligence Summary & Geospatial Analysis
Report number
714

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 operational environment is characterized by continued UAF degradation of RF strategic logistics and localized RF tactical gains in the Donetsk sector. Thermal imagery confirms a successful UAF SSO and partisan strike on the Gukovo oil depot in Rostov Oblast, compounding logistical friction following the total cessation of operations at the Moscow Oil Refinery (MNPP). This dual-pressure campaign targets both central processing capacity and regional distribution nodes.

On the ground, the RF MoD has officially confirmed the capture of Rai-Aleksandrovka by the 123rd and 88th MRB, positioning forces to threaten the H20 highway and interdict logistics supporting Sloviansk. Concurrently, RF Aerospace Forces continue retaliatory multi-domain strikes against Ukrainian rear areas, with significant impacts reported in Dnipropetrovsk and Sumy. The information environment remains contested, with RF leveraging casualty exchange narratives and internal OPSEC failures regarding civilian filming of strikes.

Operational Updates

  • Eastern (Donetsk / Luhansk):
    • Rai-Aleksandrovka: RF 123rd and 88th MRB have consolidated control, claiming fire control over Slavyansk. Independent verification of the tactical advantage is pending.
    • Kostiantynivka: RF 1194th Motorised Rifle Regiment continues urban clearing operations. RF claims of encircling four UAF brigades remain unverified.
    • Dobropillia: RF 3rd Spetsnaz Brigade is employing fixed-wing VTOL drones for combined kinetic strikes and PSYOP (dropping "humanitarian" supplies with loudspeakers).
  • Northern (Kharkiv / Sumy / Moscow Interior):
    • Gukovo Strike: UAF SSO and "Black Spark" partisans struck the Rostovnefteprodukt fuel base. Thermal footage confirms active fires in cylindrical tanks, indicating significant damage to fuel distribution infrastructure.
    • Vovchansk: RF claims capture of Okhrymovka and forest belts near Bilyi Kolodiaz to deny UAF drone corridors. UAF appears to be conducting elastic defense, retaining tactical heights.
    • Sumy: RF aviation struck a warehouse containing sulfur; local authorities report no immediate environmental threat to the population.
  • Southern (Zaporizhzhia / Kherson):
    • Weather Impact: Forecasted thunderstorms in Kherson (100% probability, 8.7mm precip) will severely restrict tactical drone operations and ground mobility for the next 24 hours.
    • Ground Lines: Largely static. RF continues localized pressure but no major territorial shifts reported in this window.
  • Deep/Rear (Dnipropetrovsk / RF Interior):
    • Dnipropetrovsk: RF executed over 20 multi-domain strikes (artillery, drones, missiles) on 18 June, resulting in 2 KIA and 17 WIA across Dnipro, Nikopol, and Zelenodolske.
    • Moscow Refinery: Reuters confirms UAF strikes disabled CDU-6 and "Euro+" units, halting 100% of primary oil processing capacity.

SAR Intelligence (Satellite Data)

  • High Priority Anomalies:
    • 155th Central Communications Warehouse (Moscow Military District): Critical anomaly detected (Score: 5.17). Significant deviation from historical baseline warrants investigation for potential logistical dispersal or increased throughput.
    • 66th Guards Pontoon-Bridge Regiment (Moscow Military District): Moderate anomaly (Score: 5.81). May reflect engineering activity related to rear-area logistics or bridge repair efforts.
    • 12th Anti-Aircraft Missile Regiment (Crimea): Previously noted critical anomaly; current readings are baseline, suggesting stabilization or completion of assessment/relocation.
  • Analysis: Frontline SAR readings remain largely at baseline levels, consistent with distributed, weather-masked staging. Critical anomalies are concentrated in rear-area air defense and engineering units in the Moscow Military District, rather than forward mechanized buildups. No significant changes detected at major airbases or naval facilities in the Black Sea.

Equipment & Losses

  • Confirmed UAF Kinetic Effects:
    • Infrastructure: Strike on Gukovo fuel base (Rostov); confirmed halt of Moscow Oil Refinery operations; interdiction of Chongar, Promoine, and Tonky bridges (previous context).
    • Tech: Deployment of tracked UGV armed with 12.7mm HMG by 5th Separate Assault Kyiv Brigade for infantry support.
  • RF Losses/Damage:
    • Personnel: 2 KIA and 17 WIA in Dnipropetrovsk region from RF retaliatory strikes.
    • Tactical: RF 122nd MR Regiment and other assault groups in Krasnyi Lyman reporting high attrition (previous context).
  • Unconfirmed:
    • RF claims of 800m advance in Riasne (Sumy).
    • RF claims of complete encirclement of four UAF brigades in Kostiantynivka.

Confidence Check

  • HIGH: UAF strike on Gukovo fuel depot (thermal confirmation); RF capture of Rai-Aleksandrovka (MoD confirmation + visual evidence); Cessation of Moscow Refinery operations (Reuters confirmation).
  • MEDIUM: RF advances in Okhrymovka (conflicting reports on UAF retention of heights); Extent of damage to Sumy sulfur warehouse.
  • LOW/UNCONFIRMED: Full extent of UAF encirclement in Kostiantynivka; Operational status of new UAF long-range missiles ("Flamingo").

The Bottom Line

UAF deep-strike capabilities continue to degrade RF strategic fuel logistics, moving from central refining (Moscow) to regional distribution (Gukovo). On the ground, RF is prioritizing the isolation of Sloviansk via the capture of Rai-Aleksandrovka, while attempting to deny UAF drone corridors in the Kharkiv sector. Monitor the H20 highway for signs of RF interdiction attempts and the Kherson sector for weather-induced operational pauses. Watch for further RF information operations leveraging the Bryansk incident and casualty exchange disparities.

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

Against the previous report from 17 Jun 2026, 15:06 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 #714: Kostiantynivka area

Geospatial Analysis

13 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 13 places with coordinates
Geocoded places in report 714
PlaceCountryLatitude, longitudeCopy
GukovoRU48.0513115, 39.9377047
Moscow Oil Refinery (MNPP)RU55.340396, 38.2917651
Rai-AleksandrovkaUA48.015883, 37.80285
H20 HighwayUA47.9277546, 37.7669318
SlovianskUA48.8532, 37.6053
KostiantynivkaUA48.52394289999999, 37.7075811
DnipropetrovskUA48.464717, 35.046183
SumyUA50.9077, 34.7981
KhersonUA46.635417, 32.616867
OkhrymovkaUA49.9935, 36.230383
Chongar BridgeUA46.0294706, 34.5454805
155th Central Communications WarehouseRU55.7568721, 37.6150527
66th Guards Pontoon-Bridge RegimentRU55.7568721, 37.6150527

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.