Daily intelligence

UAF Deep Strikes Sustain Pressure on Krasnodar Coastal Nodes; RF AD Realigns to Adler Amid London Diplomatic Coordination

Published Intelligence Summary & Geospatial Analysis
Report number
702

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-strike operations continue to degrade RF energy and logistics infrastructure in Krasnodar Krai, with sustained thermal signatures at the Ust-Labinsk refinery and expanded UAV threat alerts declared across Tuapse, Novorossiysk, and Gelendzhik. Concurrently, RF air defense assets are reportedly reallocating to Adler coastal sectors to protect resort and port infrastructure, indicating a tactical shift toward rear-area force protection.

On the contact line, RF maintains attritional pressure along the Pokrovsk and Kostiantynivka axes, utilizing FAB/KAB delivery under heavy cloud cover in Zaporizhzhia and Kherson to mask terminal approaches. UAF forward elements, including SBU Group "Alfa" and Azov units, are conducting localized counter-infiltration and civilian evacuations under direct fire.

Diplomatically, President Zelensky's engagement in London with UK and E3 leadership aims to formalize security agreements and synchronize long-term military aid pipelines. RF information operations continue to push unverified narratives regarding PFM-1 dispersal over St. Petersburg and advocate for operational pauses, reflecting emerging cognitive friction within pro-Russian channels.

Operational Updates

  • Northern/Central Sector: UAV ingress detected over Sumy and Chernihiv oblasts, tracking westward. Air raid alerts in Zaporizhzhia city were lifted following successful AD intercepts, though regional missile threats persist. Heavy overcast (100% cloud) over Orikhiv and Kherson (99% cloud) continues to degrade EO/IR tracking, necessitating reliance on radar and acoustic cueing.
  • Eastern Sector: Sustained RF ground assaults and FAB-500 strikes target forward defensive positions near Pokrovsk and Konstantinovka. SBU Special Operations Group "Alfa" is clearing infiltrated elements in vegetated terrain near Pokrovsk. Unconfirmed RF claims report destruction of a UAF 152mm D-20 howitzer near Rudovskie Dachi; no territorial shifts validated.
  • Southern Sector: UAF tactical UAS employed to enforce movement curfews in occupied territories, striking transit violators. RF FAB strikes impact frontline settlements, prompting Azov forces to conduct high-risk civilian evacuations. Maritime UAV vectors tracked toward Snihurivka and Black Sea ports (Chornomorsk/Pivdenne), indicating continued pressure on coastal logistics nodes.
  • Deep/Strategic & C2: Visual confirmation of sustained fires at Ust-Labinsk refinery (Krasnodar) and UAS strikes on a gas station in Prokhorovka (Belgorod Oblast), destroying three heavy trucks. RF AD assets reportedly deployed to Adler to bolster coastal defense. SBU initiated war crime investigation regarding RF strikes on nuclear fuel storage near Chernobyl.

SAR Intelligence (Satellite Data)

  • Baseline Activity: 1,292 valid SAR updates processed. Zero locations require immediate high-priority attention. Six locations exhibit moderate activity. A score near 0 indicates no significant change and does not imply a facility is empty or preparing for an attack.
  • Moderate Activity Locations: Notable deviation scores recorded at 15th Navy Arsenal (Score: 6.18), Border Guard Outpost (Brest Oblast) (Score: 5.23), Department of the State Security Committee (KGB) for the Vitebsk Oblast (Score: 4.23), and 33rd Separate Guards Special Purpose Detachment (Score: 4.13).
  • Analysis: Elevated SAR deviation scores at internal security and logistics nodes indicate localized vehicle movement or equipment staging. No concentrated force buildup or rapid redeployment signatures detected along primary contact lines. Persistent overcast in southern sectors continues to limit optical ISR utility, enforcing reliance on radar and acoustic sensor fusion for early warning.

Equipment & Losses

  • Confirmed UAF Gains: Sustained degradation of Ust-Labinsk refinery; kinetic strike on Prokhorovka gas station (Belgorod) neutralized three RF heavy trucks. UAF Air Force crew milestone: >200 confirmed fixed-wing UAV kills.
  • RF Capabilities: Continued deployment of FAB-500/UMPK glide bombs; FPV employment in Mykolaiv and Zaporizhzhia rear areas. Visual confirmation of DPRK Hwasong-11 (KN-23) SRBM production facility inspection.
  • Civilian/Infrastructure Damage: RF strikes impact frontline settlements requiring civilian evacuation. Unconfirmed: RF claim of 152mm D-20 howitzer loss near Rudovskie Dachi; RF narrative alleging PFM-1 mine dispersal over St. Petersburg.

Confidence Check

  • HIGH: Ust-Labinsk refinery fire persistence; Zaporizhzhia air raid alert clearance; UAV threat alerts in Tuapse/Novorossiysk/Gelendzhik; Prokhorovka gas station strike; weather conditions impacting EO/IR in southern sectors.
  • MEDIUM: RF AD redeployment to Adler; extent of UAF aerial surveillance over Melitopol–Chonhar corridor; SBU counter-infiltration operations near Pokrovsk.
  • LOW/UNCONFIRMED: RF claims of D-20 destruction near Rudovskie Dachi; PFM-1 dispersal narrative in St. Petersburg; 30th MSP (Luga) recruitment friction; territorial gains in Konstantinovka/Kupiansk.

The Bottom Line

RF will continue exploiting 85–100% cloud cover across Zaporizhzhia and Kherson to mask FAB/KAB delivery and low-altitude UAS transit, while maintaining attritional infantry pressure on the Pokrovsk axis. UAF defensive posture must prioritize radar-acoustic cueing integration, harden rear logistics against cross-border UAS routing, and validate RF AD reallocation to coastal sectors via SIGINT. Monitor London diplomatic outcomes for concrete aid delivery timelines and watch for potential RF escalation in rear-area security protocols following sustained Krasnodar and Belgorod strikes.

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

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

0 visuals

No report-specific visuals are available for this briefing.

Geospatial Analysis

Frontline comparison

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.

No geocoded places are stored for this report.

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.