UAF Strikes Moscow Refinery; RF Fuel Crisis Escalates Amidst Kostiantynivka Encirclement Attempts
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
The operational environment is defined by the successful degradation of Russian strategic energy infrastructure and a concurrent escalation in ground pressure on Kostiantynivka. Visual evidence confirms a major fire at the Moscow Refinery (Moskovsky NPZ), halting operations after a strike damaged the AVT-6 unit, which accounts for over 50% of its capacity. This event has triggered systemic downstream effects, including nationwide bans on gasoline sales in jerrycans by major RF oil companies (Rosneft, Bashneft, TNK) and the imposition of 90-liter refueling limits.
Simultaneously, RF forces are executing a multi-axis encirclement of Kostiantynivka, advancing from Novodmytrivka, Berestok, and Illinivka to sever the northern logistics isthmus. In the Siversk-Lyman axis, RF troops have advanced 2.5 km along the southern bank of the Siverskyi Donets, securing positions in eastern Piskunivka and reaching railway infrastructure in central Krasnyi Lyman. The compounding fuel crisis and logistical disruptions threaten to degrade RF maneuver capabilities and aviation sortie rates in the coming weeks.
Operational Updates
- Eastern (Donetsk / Luhansk):
- Kostiantynivka: RF forces are applying multi-axis pressure to isolate the city. Pro-Russian sources claim systematic clearing of central districts, while UAF reportedly holds northwestern outskirts. Urgent ISR tasking is required to verify the status of the northern logistics routes.
- Siversk / Lyman: RF advanced 2.5 km along the southern bank of the Siverskyi Donets, occupying new positions in eastern Piskunivka. In Krasnyi Lyman, RF troops reached the railway station and tracks in the Central microdistrict under UAF fire.
- Kupiansk: RF claims territorial advances in urban combat within Kupiansk and towards Kupiansk-Uzlovoy. The 122nd MR Regiment reports critical attrition on the right bank of the Oskil River, with UAF destroying up to 5 RF positions daily.
- Northern (Kharkiv / Sumy):
- Volchansk: RF "North" grouping claims tactical advances south of Volchansk (Burlyuk direction) using small-group tactics. UAV incursions tracked towards Krivelts and Khotin (Sumy).
- Air Threats: UAF Air Force tracked a jet-powered UAV transiting northern Chernihiv towards the Kyiv region. Multi-vector UAV threats also tracked towards Izium and Chuhuiv.
- Southern (Zaporizhzhia / Kherson):
- Zaporizhzhia: Intense RF artillery and drone barrages impacted four districts in the Dnipropetrovsk region, resulting in 3 civilian deaths. UAV threats tracked towards Apostolove and Novyi Buh.
- Logistics Interdiction: UAF Unmanned Systems Forces (SBS) struck an RF Osa SAM system, 5 coastal radars in Crimea, and multiple brigade-level logistics depots (9th MSBr, 72nd MSBr, 14th Airborne, 60th MSBr).
- Deep/Rear (RF Interior & Crimea):
- Moscow Refinery: Operations halted following strike on AVT-6 unit. Nationwide fuel rationing and quality downgrades (Euro-3) reported.
- Novoazovsk Bridge: UAF strike confirmed on the bridge over the Grozsky Yelanchik river (R-280 highway), disrupting a key logistics route to Crimea. RF repair efforts are underway.
- Rybinsk: "Oil rain" reported in the Yaroslavl region following a June 14 strike on the "Temp" Rosrezerv facility.
SAR Intelligence (Satellite Data)
- High Priority Anomalies:
- 12th Anti-Aircraft Missile Regiment (Crimea): Critical anomaly detected (Score: 10.76; Robust Z: 289.36). Activity significantly deviates from historical baselines, warranting immediate investigation for potential relocation or damage assessment.
- Separate Special Purpose Detachment "Rys" (Belarus): Critical anomaly detected (Score: 4.60; Robust Z: 8.79). Indicates potential force generation or equipment staging.
- Training Grounds (Crimea): Critical anomaly detected (Score: 4.03; Robust Z: 2.36). May indicate reactive movements or training intensification.
- Analysis: The majority of frontline SAR readings remain at baseline levels. Critical anomalies in rear-area internal troops and air defense regiments may signal reactive movements following deep strikes or unrelated administrative shifts. No significant mechanized buildup is detected at forward staging areas in the East.
Equipment & Losses
- Confirmed UAF Kinetic Effects:
- Infrastructure: Major fire at Moscow Refinery (Moskovsky NPZ); damage to Novoazovsk Bridge (R-280); strikes on RF Osa SAM and coastal radars in Crimea.
- Logistics: Destruction of RF fuel tanker on E58 highway (previous day); continued disruption of RF fuel supply chains.
- RF Losses/Damage:
- Personnel: 3 civilians killed in Dnipropetrovsk region due to RF artillery/drone barrage.
- Tactical: RF 122nd MR Regiment reporting high attrition in Kupiansk.
- Unconfirmed:
- RF frigate Admiral Grigorovich firing warning shots at a British yacht in the English Channel (assessed as potential disinformation; photo evidence inconsistent with Channel waters).
- RF use of new "Bandrol" subsonic cruise missile against Kyiv.
Confidence Check
- HIGH: Damage to Moscow Refinery; RF nationwide fuel rationing/jerrycan bans; UAF strikes on Novoazovsk Bridge and Crimean air defense assets; RF multi-axis pressure on Kostiantynivka.
- MEDIUM: RF advances in eastern Piskunivka and central Krasnyi Lyman; RF attrition rates in Kupiansk; Jet-powered UAV trajectory towards Kyiv.
- LOW/UNCONFIRMED: Admiral Grigorovich incident in English Channel; Operational deployment of "Bandrol" cruise missile; Full extent of RF control in central Kostiantynivka.
The Bottom Line
The successful strike on the Moscow Refinery has escalated the RF domestic fuel crisis into a systemic logistical constraint, evidenced by nationwide rationing and quality downgrades. This will likely degrade RF military mobility and aviation sortie rates in the near term. On the ground, RF is attempting to replicate the Pokrovsk scenario in Kostiantynivka by severing northern logistics lines. Immediate verification of the Kostiantynivka northern isthmus status is critical to assess the risk of city isolation. Monitor RF fuel distribution nodes for signs of military prioritization over civilian needs.
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 15 Jun 2026, 15:10 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
5 visualsGeospatial 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
| Place | Country | Latitude, longitude | Copy |
|---|---|---|---|
| Kostiantynivka | UA | 48.52394289999999, 37.7075811 | |
| Moscow Refinery (Moskovsky NPZ) | RU | 55.340396, 38.2917651 | |
| Novoazovsk Bridge | UA | 47.1190259, 38.0670367 | |
| Piskunivka | UA | 48.574041, 39.307815 | |
| Krasnyi Lyman | UA | 48.7194807, 38.9703643 | |
| Kupiansk | UA | 49.7055574, 37.6027997 | |
| Crimea | RU | 45.3453029, 34.4997274 | |
| Volchansk | UA | 50.284234, 36.9329429 | |
| Kyiv | UA | 50.0529506, 30.7667133 | |
| Rybinsk | RU | 58.057486, 38.8116968 |
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.
