Daily intelligence

UAF Strikes TAIF-NK Refinery in Tatarstan; RF Escalates Aerospace Pressure on Odesa and Zaporizhzhia

Published Intelligence Summary & Geospatial Analysis
Report number
746

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 21.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 confirmation via satellite imagery of structural damage to the TAIF-NK oil refinery in Nizhnekamsk, Republic of Tatarstan, following a Ukrainian Armed Forces (UAF) deep-strike campaign. This strike extends the envelope of UAF interdiction against Russian Federation (RF) energy infrastructure, compounding existing domestic fuel shortages and logistical friction. Concurrently, RF forces escalated aerospace saturation strikes against Ukrainian urban centers, inflicting confirmed casualties in Odesa and Zaporizhzhia while attempting to degrade maritime logistics through renewed attacks on port infrastructure.

Ground operations remain characterized by high-tempo attritional assaults in the Pokrovsk and Sloviansk directions, with no verified territorial changes despite RF claims of advances in Maryino (Sumy Oblast) and Kostiantynivka. The RF reliance on non-profile units, including Aerospace Forces (VKS) personnel, for ground infantry roles in Sumy highlights ongoing manpower constraints. UAF defensive operations successfully repelled 70 combat clashes over the past 24 hours, maintaining stable frontline positions while executing effective counter-infiltration measures.

Operational Updates

  • Eastern Sector (Donetsk): RF maintained intense pressure with 22 assaults in the Pokrovsk direction and 20 in the Sloviansk direction per UAF General Staff data. RF milbloggers claimed advances in Rodynske and the capture of Myrne, but these lack geospatial verification. In Kostiantynivka, UAF reported up to 145 RF personnel accumulated in the city, with the 425th Assault Regiment "Skelya" confirming the capture of two soldiers during a counterattack, refuting earlier RF disinformation regarding a staged surrender.
  • Northern Sector (Kharkiv/Sumy): RF conducted three assaults in the South-Sloboda direction and targeted gas stations in Kharkiv Oblast. RF sources claimed an advance in Maryino (Sumy Oblast) using VKS personnel as assault infantry, assessed as low confidence due to lack of visual confirmation. UAF Air Force tracked multi-vector UAV threats towards Kharkiv and Sumy, with local authorities reporting persistent shelling in border settlements.
  • Southern Sector (Zaporizhzhia/Odesa/Kherson): RF struck a civilian enterprise in Odesa Oblast, causing a massive fire, damaging a gas main, and resulting in 3 dead and 4 injured. In Zaporizhzhia, KAB strikes on residential areas resulted in 43 civilian casualties, including 7 children. UAF Air Force tracked incoming jet-powered UAVs and Onyx missiles towards Odesa and Chornomorsk, indicating continued targeting of maritime logistics.
  • Central Rear (Kyiv): UAF Air Force tracked a UAV heading towards Berezan (Kyiv Oblast) from the northeast. No significant strikes or damage were reported in Kyiv city during this cycle, contrasting with the heavy aerospace activity in southern and eastern regions.

Deep Strikes & Air Defense

  • UAF Deep Strikes:
    • Tatarstan: Satellite imagery confirms significant structural damage and burn marks at the TAIF-NK oil refinery in Nizhnekamsk, though anti-drone nets obscure full assessment of key processing units. This follows a broader campaign targeting RF energy nodes.
    • Moscow Oblast: Overnight drone strikes caused fires at an oil depot in Podolsk, a warehouse in Domodedovo, and a site near TsNIITochMash in Klimovsk. RF authorities claimed 10 casualties and intercepted numerous UAVs, though debris impacts confirm penetration.
    • Maritime: UAF FP-2 kamikaze drones reportedly struck seven Russian vessels (three oil tankers, four dry cargo) in the Black Sea and Sea of Azov, further degrading RF maritime logistics capacity.
  • RF Aerospace Campaign:
    • Odesa/Zaporizhzhia: Sustained strikes using KABs, missiles, and UAVs. RF claimed strikes on port fuel reserves and a bulk carrier off Odesa, though visual evidence remains limited.
    • Kharkiv: Continued targeting of gas stations and residential infrastructure with KABs and loitering munitions.
  • Air Defense: UAF Air Force actively tracked and engaged multi-vector threats, including Onyx missiles and jet-powered UAVs. Weather conditions (clear to overcast, light winds) remained favorable for both UAF and RF unmanned operations.

SAR Intelligence (Satellite Data)

  • High Priority:
    • TAIF-NK Refinery (Nizhnekamsk): Optical/SAR confirmation of structural damage and burn marks corroborates UAF strike reports. Anti-drone nets limit detailed unit-level assessment.
    • Bushehr Military Site (Iran): A critical anomaly (Score 16.81) was detected at a military site in Bushehr Province, Iran. While outside the immediate theater, this indicates significant activity requiring monitoring for potential regional spillover or supply chain implications.
  • Analysis: The damage to TAIF-NK validates the effectiveness of UAF long-range drone campaigns against hardened energy targets. The high anomaly score in Iran is noted but requires further contextual intelligence to determine relevance to the Russo-Ukrainian conflict. No significant changes were detected at frontline RF logistics hubs, suggesting stable baseline activity there despite rear-area disruptions.

Equipment & Losses

  • RF Losses:
    • Maritime: 7 vessels (3 tankers, 4 dry cargo) reportedly struck by UAF FP-2 drones in Black Sea/Azov (Unconfirmed: requires AIS verification).
    • Infrastructure: TAIF-NK refinery (Nizhnekamsk) damaged; Podolsk oil depot and Domodedovo warehouse fires confirmed.
    • Personnel: UAF 225th Separate Assault Brigade captured 64 RF soldiers in Velyka Novosilka direction; UAF 6th OSBrP "Ranger" captured 6 RF soldiers in Sadky (Sumy Oblast).
  • UAF Losses/Damage:
    • Civilian Casualties: 3 dead, 4 injured in Odesa Oblast strike; 43 casualties (7 children) in Zaporizhzhia KAB strikes.
    • Infrastructure: Gas main damaged in Odesa Oblast; residential building destroyed in Zaporizhzhia.

Confidence Check

  • TAIF-NK Refinery Damage: HIGH (Confirmed by satellite imagery and open-source analysis).
  • Odesa/Zaporizhzhia Casualties: HIGH (Confirmed by local oblast administrations and emergency services).
  • Maritime Vessel Strikes: MEDIUM (Claimed by UAF sources; requires independent AIS/satellite verification for BDA).
  • RF Advances in Maryino/Kostiantynivka: LOW (RF claims only; contradicted by UAF reports and lacking geospatial evidence).
  • Moscow Oblast Strike BDA: MEDIUM (Fires confirmed by visual evidence; exact target identification and casualty counts vary between sources).

The Bottom Line

The conflict trajectory continues to feature asymmetric UAF deep strikes degrading RF strategic energy and logistics nodes (Tatarstan, Moscow Oblast), while RF forces rely on massed aerospace attacks against Ukrainian civilian and industrial infrastructure to offset frontline stagnation. In the next 24 hours, monitor:

  1. TAIF-NK Operational Status: Assessment of the impact of the Nizhnekamsk refinery damage on regional fuel supplies and RF logistics.
  2. Odesa Port Throughput: Verification of damage to port infrastructure and gas mains following the latest strikes, and its effect on grain/military cargo flows.
  3. RF Manpower Composition: Further evidence of RF deploying non-combat units (e.g., VKS personnel) as infantry in Sumy and Kharkiv, indicating acute manpower shortages.

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

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

The latest control-map interval ended 21.3 hours before this report. The daily change covers 26.5 h. These map dates may differ from the reporting period and do not establish when territorial changes occurred.

Latest interval
+2.4 km²
27 h ending 19 Jul 2026, 17:48 UTC
Daily net
+2.4 km²
26.5 h comparison
Seven-day net
-23 km²
172.9 h comparison
Largest changes in the latest measured interval
Near Chasiv Yar
1.6 km² changed · RF-held gained 1.6 / lost 0.0 km²
Near Chasiv Yar
0.8 km² changed · RF-held gained 0.8 / lost 0.0 km²

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 #746: Pokrovsk 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 746
PlaceCountryLatitude, longitudeCopy
NizhnekamskRU55.613196, 51.8469974
PokrovskUA48.282193, 37.1847804
SlovianskUA48.8532, 37.6053
OdesaUA46.4845702, 30.7326047
ZaporizhzhiaUA47.83928419999999, 35.13870970000001
MaryinoRU0, 0
KharkivUA50.00201269999999, 36.3073994
PodolskRU55.4312453, 37.5457647
DomodedovoRU55.44302339999999, 37.747817
BushehrIR28.9144913, 50.8279019

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.