UAF Sinks RF Patrol Ship in Crimea; RF Enforces 20L Fuel Cap Amid Multi-Axis UAS Saturation
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
Analyst briefMachine-generated narrative. Labels inside it are written by the model. How to read these labels
Strategic Overview
Ukrainian Special Operations Forces (SBS) and UAS units have executed a successful maritime strike on an RF Project 10410 patrol ship in occupied Crimea, reinforcing UAF Black Sea denial capabilities. Concurrently, systemic UAF deep-strike campaigns have resulted in quantified RF rear-area fuel degradation, evidenced by a strict 20-liter voucher cap instituted in Crimea and supply restrictions expanding across 15 Russian regions.
To offset logistical friction, RF forces are heavily exploiting persistent theater-wide overcast conditions to launch multi-vector UAS and guided aerial bomb (KAB) saturation strikes. These strikes are deliberately targeting central logistics nodes and critical energy redundancy infrastructure, notably placing the Zaporizhzhia Thermal Power Plant (ZTPP) and its connection to the Zaporizhzhia Nuclear Power Plant (ZNPP) under extreme operational threat.
Operational Updates
- Southern Sector (Black Sea/Crimea): UAF UAS and SBS units successfully struck the RF Project 10410 border patrol ship "Svitlyak" near Yurkyne, with multiple sources confirming the impact and resulting visual evidence.
- Southern Sector (Zaporizhzhia/Kherson): RF executed 924 combined attacks across 52 settlements in the Zaporizhzhia region within 24 hours. IAEA monitors explicitly warned that deliberate shelling of the Zaporizhzhia Thermal Power Plant (ZTPP) threatens the final external power transmission line supporting ZNPP safety systems. Weather in Zaporizhzhia/Orikhiv (23.4°C, 99% cloud cover, 2.0 m/s wind) heavily masks KAB launch trajectories.
- Northern/Central Sector: UAF early warning tracked multi-axis UAS penetrations targeting the Boryspil approach corridor and Dnipropetrovsk logistics nodes, resulting in a confirmed strike on a dual-use Nova Poshta terminal. Weather in Kharkiv/Vovchansk (18.7°C, 84% cloud cover, 2.6 m/s wind, light rain) enforces strict UAF reliance on radar and acoustic tracking.
- RF Rear & Logistics: Occupation authorities in Crimea mandated a strict 20-liter fuel voucher cap per person, quantifying acute logistical vulnerability. RF security services formally designated OSINT monitoring groups (OVD-Info, Revolt-center) as extremist to tighten domestic information control.
- UAF Administration: UAF Military Law Enforcement officially established "SCORPION," a rapid reaction unit designed for rear-area internal security and counter-sabotage operations.
SAR Intelligence (Satellite Data)
- High Priority: CRITICAL anomalous activity deviations detected at the 3rd Radio-Technical Regiment (2.62), a Vehicle Park (2.62), the 38th Fighter Aviation Regiment (2.31), AB Belbek (2.31), and the 1311th Central Tank Storage and Repair Base (1.02).
- Analysis: Extremely high deviation scores (>2.00) at Crimean aviation and AD nodes (AB Belbek, 38th Fighter Aviation Regiment) correlate with asset dispersal or heightened alert posturing following the UAF maritime strike on the "Svitlyak". Concurrent high activity at vehicle storage and tank repair nodes aligns with documented RF logistical friction and emergency fuel rationing protocols.
Equipment & Losses
- Confirmed RF Losses: Project 10410 "Svitlyak" border patrol ship struck near Yurkyne. UAF "Strix" kinetic interceptors successfully neutralized a high-value RF "Skat-450M" reconnaissance UAV ($400k value).
- RF Capabilities: Unconfirmed field reports suggest the localized deployment of wire-guided (fiber-optic) FPVs and "Molniya-1" drone carriers to bypass UAF EW dominance in the Kharkiv sector.
- Civilian/Infrastructure Damage: Sustained damage to the Nova Poshta logistics terminal in Dnipropetrovsk and a multi-story residential building in Kherson (2 KIA, 9 WIA).
Confidence Check
- HIGH: UAF maritime strike on RF "Svitlyak" patrol ship; implementation of Crimean 20L fuel cap; IAEA confirmation of ZTPP grid threats; Boryspil UAS tracking vectors.
- MEDIUM: Interception of the RF "Skat-450M" UAV; Austrian interior ministry proposal to suspend EU-wide temporary protection for Ukrainian men (23-60) by March 2027.
- LOW: RF operational claims of territorial capture at Komsomolskoye (Zaporizhzhia); RF milblogger narratives alleging impending US reductions in NATO contributions (assessed as cognitive warfare).
The Bottom Line
RF command is leveraging persistent low-visibility weather to maximize stand-off strikes against critical Ukrainian energy grids and transit corridors, attempting to dilute UAF air defenses while masking their own severe rear-area fuel shortfalls. Over the next 12-24 hours, expect sustained RF artillery and UAS pressure on the ZTPP grid to threaten nuclear safety redundancy. UAF operations will likely focus on leveraging radar-cued AD intercepts to defend the Boryspil axis and exploiting verified RF maritime vulnerabilities in the northwestern Black Sea.
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.
Against the previous report from 03 Jun 2026, 16:22 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.
Report Visuals
0 visualsNo 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.
