Daily intelligence

Omsk Refinery Halts Operations; UAF Strikes Shadow Fleet and Crimean Energy Grid

Published Intelligence Summary & Geospatial Analysis
Report number
733

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
Newest map data is 65.3 h older than this report.

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 significant operational development of the last 24 hours is the confirmed cessation of operations at the Omsk Oil Refinery (Gazprom Neft) in Russia, following a Ukrainian Armed Forces (UAF) drone strike on July 6. The facility, which accounts for approximately 10% of Russia's total oil processing capacity, halted fuel sales on the St. Petersburg exchange after sustaining damage to its CDU-10 and CDU-11 units. This marks a critical escalation in the degradation of RF strategic fuel logistics.

Concurrently, UAF forces executed a coordinated maritime and energy interdiction campaign. Naval drones struck up to 12 RF "shadow fleet" tankers in the Sea of Azov, while Special Operations Forces (SBS) targeted five electrical substations and the Tasunove gas compressor station in occupied Crimea. These strikes triggered mass blackouts across 18–20 districts in Crimea and forced occupation authorities to halt civilian fuel sales in Sevastopol. On the ground, RF forces continue high-tempo assaults in the Dobropolye and Huliaipole sectors, though NATO assessments indicate RF advance rates have dropped fourfold year-over-year due to manpower constraints.

Operational Updates

  • Eastern Sector (Donetsk): RF forces advanced to the northern outskirts of Belytskoye (Donetsk Oblast) in the Dobropolye direction, occupying tree lines that threaten UAF supply routes to Krasnopopole. In the Kostiantynivka sector, RF milbloggers claim full control of the city, but independent verification remains lacking; ground truth suggests ongoing contested clearing operations rather than a strategic breakthrough. RF also deployed fiber-optic controlled UAVs between Zarechne and Lyman to bypass UAF electronic warfare.
  • Southern Sector (Zaporizhzhia): RF conducted 22 ground assaults across the Olexandrivsk and Huliaipole directions, including 18 attacks in the Huliaipole sector. UAF Southern Group of Forces repelled these assaults while absorbing 12 airstrikes utilizing 41 guided aviation bombs (FABs). No significant territorial changes were reported in the Orikhiv or Prydniprovskyi sub-sectors.
  • Northern Sector (Kharkiv/Sumy): RF launched repeated KAB strikes on the Shevchenkivskyi district of Kharkiv city, resulting in 1 civilian death and 21 injuries. In Kozachya Lopan, the RF 245th Motorized Rifle Regiment is failing to fully clear the settlement, with UAF maintaining pockets of resistance. RF claims of capturing Petro-Ivanivka remain unverified.

Deep Strikes & Air Defense

  • UAF Strategic Strikes:
    • Energy Infrastructure: UAF SBS units struck substations in Chkalove, Zakhidno-Krymska, Saky, Kamysh-Burun, and Mytyayeve, as well as the Tasunove gas compressor station in Crimea, causing widespread power outages.
    • Maritime Interdiction: UAF naval drones struck 8–12 RF shadow fleet tankers in the Sea of Azov, including the MS IVAN CHEREMISINOV. RF sources acknowledged damage to several vessels and criticized the lack of naval escorts.
    • Industrial Targets: The Omsk Oil Refinery halted operations after strikes damaged critical distillation units. UAF also claimed strikes on railway infrastructure in Dnipropetrovsk and Poltava oblasts.
  • RF Aerospace Campaign:
    • Kyiv Aftermath: Search and rescue operations concluded in Kyiv following the July 6 mass strike; the final toll is 19 dead and 61 injured.
    • Frontline Strikes: RF continued high-tempo Shahed and KAB strikes against Kharkiv, Zaporizhzhia, and Dnipropetrovsk oblasts, targeting logistics hubs (Nova Poshta) and residential areas.
    • Air Defense Claims: RF authorities claimed to have intercepted 452 UAVs overnight, including 50 near Moscow. Independent sources report hits on military and defense industry objects in the Moscow region, though specific damage remains unconfirmed.

SAR Intelligence (Satellite Data)

  • High Priority: SAR anomaly detection identified critical activity deviations at the 155th Central Communications Warehouse (Moscow Military District) and AB Pribylovo (Leningrad Oblast), with diff_scores of 5.87 and 7.37 respectively. These scores indicate significant structural or vehicular movement changes requiring immediate visual verification.
  • Analysis: While most monitored bases show baseline activity (scores near 0), the high-diff scores at communications and air base facilities in the Russian rear suggest potential logistical reshuffling or damage assessment activities following recent UAF deep strikes. No significant changes were detected at frontline command posts.

Equipment & Losses

  • RF Losses: UAF General Staff reports cumulative RF losses reached ~1,412,250 personnel (+1,200 in 24h). Specific equipment losses include an RF S-400 launcher in Bryansk Oblast (destroyed by UAF SBS) and multiple shadow fleet tankers in the Sea of Azov.
  • UAF Losses: Confirmed loss of a UAF Mi-8 helicopter (16th Army Aviation Brigade) in Poltava Oblast on June 30, with all 4 crew members killed. The aircraft was engaged while intercepting Shahed drones.

Confidence Check

  • Omsk Refinery Halt: HIGH (Confirmed by multiple independent sources and RF exchange data).
  • Crimea Blackout: HIGH (Corroborated by NASA FIRMS thermal anomalies and local reporting).
  • Shadow Fleet Strikes: MEDIUM (UAF claims 12 hits; RF acknowledges damage to several; exact count unverified).
  • Kostiantynivka Control: LOW (RF claims full control; no independent geolocated confirmation; likely IO exaggeration).
  • Belytskoye Advance: MEDIUM (RF milblogger claims supported by tactical context, but lacks visual proof).

The Bottom Line

The conflict has shifted toward a contest of strategic endurance, with UAF successfully degrading RF fuel and energy logistics at ranges exceeding 2,500 km. The halt of the Omsk refinery and the isolation of Crimea’s energy grid impose severe operational costs on RF forces. In the next 24 hours, monitor:

  1. RF Fuel Logistics: Signs of systemic fuel shortages in RF border regions and military units following the Omsk halt.
  2. Kostiantynivka Frontline: Geolocated evidence to verify or refute RF claims of full city capture.
  3. NATO Summit Outcomes: Concrete announcements regarding the European Patriot production center and the "Drone Deal" initiative.

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 07 Jul 2026, 15:05 UTCLagged by 65.3 h
Map revision comparison

Against the previous report from 06 Jul 2026, 15:09 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

The latest control-map interval ended 65.3 hours before this report. A 24-hour change estimate is unavailable. These map dates may differ from the reporting period and do not establish when territorial changes occurred.

Latest interval
0.0 km²
34 h ending 04 Jul 2026, 21:47 UTC
Daily net
Unavailable
No daily comparison available
Seven-day net
+21 km²
169.1 h comparison

Positive values indicate an increase in Russian-occupied area; negative values indicate a decrease. Yellow marks DeepState's infiltration area (gray zone), which is not included in occupied-area totals.

Report Visuals

5 visuals
Open full size
Nightwatch daily report #733: Kostiantynivka area

Geospatial Analysis

10 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 10 places with coordinates
Geocoded places in report 733
PlaceCountryLatitude, longitudeCopy
Omsk Oil RefineryRussia54.9913545, 73.3645204
Sea of AzovUkraine/Russia0, 0
CrimeaUkraine (Occupied)45.3453029, 34.4997274
BelytskoyeUkraine0, 0
KostiantynivkaUkraine48.52394289999999, 37.7075811
KharkivUkraine50.00201269999999, 36.3073994
HuliaipoleUkraine47.6607145, 36.2732384
Moscow Military District - 155th Central Communications WarehouseRussia55.7568721, 37.6150527
Bryansk OblastRussia0, 0
KyivUkraine0, 0

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.