RF Claims Kostiantynivka Capture Amidst Deep-Strike Logistics Degradation
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 26.8 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
Analyst briefMachine-generated narrative. Labels inside it are written by the model. How to read these labels
Strategic Overview
The Russian Federation (RF) has launched a high-tempo Information Operation (IO) claiming the full capture of Kostiantynivka and multiple settlements in the Kharkiv sector (Shiykovka, Novy Mir, Cherneshchina, Druzhelyubovka). Ground truth verification remains pending, with conflicting reports from pro-Russian channels suggesting these claims are premature or fabricated to project momentum. Concurrently, RF forces are conducting consolidation and demining operations in Krasnyi Lyman, indicating an imminent official announcement of its capture.
In the deep rear, Ukrainian Armed Forces (UAF) continue to degrade RF logistical resilience. Confirmed strikes have damaged the St. Petersburg oil terminal and the Avtopritsep-KAMAZ plant in Stavropol, compounding existing RF fuel supply friction. In response, RF is accelerating the construction of deepened field fuel reservoirs and has signed legislation to support domestic refineries. The operational environment is further constrained by severe weather, with heavy precipitation forecast across the frontline, restricting off-road mobility and favoring artillery and FPV drone engagements over mechanized maneuver.
Operational Updates
-
Eastern Sector (Donetsk / Kharkiv):
- Kostiantynivka: RF MoD and Kremlin spokesperson Peskov claim full control. UAF General Staff reports 9 attacks repelled in this direction, contradicting total collapse narratives. Assessment: Likely IO exaggeration; frontline remains contested.
- Kharkiv / Borova: RF Zapad Group claims control of Shiykovka, Novy Mir, Cherneshchina, and Druzhelyubovka. Geolocated imagery confirms RF presence in western Druzhelyubovka, but broader operational breakthrough is unverified. Some footage cited by RF sources appears recycled from April/May.
- Krasnyi Lyman: RF 67th MRD (25th Army) is actively conducting mine clearance and mop-up operations, signaling imminent formal capture.
- Pokrovsk: UAF SBU "Alpha" drones struck RF assault troops and equipment. RF continues high-tempo assaults (17 attacks reported), utilizing FAB-500 glide bombs against UAV command posts near Dobropillia.
-
Southern Sector (Zaporizhzhia / Dnipropetrovsk):
- Zaporizhzhia City: RF KAB strikes hit a civilian car parking lot, resulting in 4 wounded (including a child) and dozens of vehicles destroyed. Previous strikes on industrial enterprises caused 1 KIA and 5 WIA.
- Huliaipole: UAF repelled 15 RF attacks. RF continues aggressive probing operations.
- Tokmak: Unconfirmed reports indicate a UAF strike on a local market resulted in 21 casualties.
-
Deep Rear & RF Interior:
- St. Petersburg: Satellite imagery confirms damage to storage tanks and pipelines at the "Saint Petersburg" oil terminal following a UAF strike.
- Taganrog: The "Atlant Aero" drone production facility has rapidly repaired blast damage and constructed new connecting corridors to harden production lines.
- Stavropol: A major fire was reported at the Avtopritsep-KAMAZ plant, a key manufacturer of military logistics trailers.
- Fuel Logistics: RF "West" grouping is constructing deepened (4-8 cubic meter) reservoirs for open-field fuel storage to mitigate drone interdiction. Putin signed legislation to support the domestic fuel market, acknowledging systemic supply issues.
SAR Intelligence (Satellite Data)
- High Priority: No high-priority SAR anomalies detected at major frontline airbases or logistics hubs. All monitored locations show baseline activity or low-confidence noisy acquisitions due to weather.
- Moderate Activity:
- FSB Department for the Stavropol Krai (Score: 2.20): Elevated activity detected; correlates with recent strikes on logistics infrastructure in the region.
- 689th Command Intelligence Center GRU (Score: 3.84): Significant deviation from baseline; monitor for C2 relocation or heightened security posture.
- Analysis: The absence of significant SAR changes at major airbases suggests no immediate mass dispersal or surge in sortie generation visible via satellite today. RF rear-area logistics nodes remain at baseline visually, despite reported ground-level fuel friction and adaptation efforts (deepened reservoirs).
Equipment & Losses
- RF Infrastructure: Structural damage to St. Petersburg oil terminal (storage tanks/pipelines); fire at Avtopritsep-KAMAZ plant in Stavropol; rapid repair and hardening of Atlant Aero facility in Taganrog.
- RF Tactics: Deployment of deepened field fuel reservoirs by RF "West" grouping to counter UAF drone interdiction. Institutionalization of UAV training in RF schools (104 schools in Sakhalin).
- Civilian Impact: 4 wounded in Zaporizhzhia city strike; 21 casualties reported in Tokmak market strike (unconfirmed).
Confidence Check
- HIGH: UAF strikes on St. Petersburg oil terminal and Stavropol logistics plant; RF IO campaign regarding Kostiantynivka; RF fuel market legislative intervention.
- MEDIUM: RF territorial gains in Kharkiv settlements (Shiykovka, Novy Mir, etc.); extent of damage to Atlant Aero production capacity post-repair.
- LOW: RF claims of full capture of Kostiantynivka; casualty figures for Tokmak strike; effectiveness of new RF school-based UAV training pipeline.
The Bottom Line
RF is leveraging a coordinated IO campaign to mask tactical stagnation and project momentum through exaggerated claims in Kostiantynivka and Kharkiv. While localized advances in Druzhelyubovka and consolidation in Krasnyi Lyman are credible, the broader narrative of breakthrough is unsupported by current ground truth. UAF deep-strike capabilities continue to impose significant costs on RF energy and logistics infrastructure, forcing adaptive measures like hardened fuel storage and rapid industrial repair. Monitor the Kostiantynivka axis for verified frontline geometry changes and assess the operational impact of RF's new fuel storage adaptations.
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 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.
The latest control-map interval ended 26.8 hours before this report. These map dates may differ from the reporting period and do not establish when territorial changes occurred.
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 visualsGeospatial Analysis
15 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 15 places with coordinates
| Place | Country | Latitude, longitude | Copy |
|---|---|---|---|
| Kostiantynivka | UA | 48.52394289999999, 37.7075811 | |
| Shiykovka | UA | 49.9935, 36.230383 | |
| Novy Mir | UA | 49.9935, 36.230383 | |
| Cherneshchina | UA | 49.31327539999999, 37.8456465 | |
| Druzhelyubovka | UA | 49.9935, 36.230383 | |
| Krasnyi Lyman | UA | 48.9897585, 37.8049964 | |
| Pokrovsk | UA | 48.282193, 37.1847804 | |
| Dobropillia | UA | 48.4691324, 37.0871223 | |
| Zaporizhzhia City | UA | 47.83928419999999, 35.13870970000001 | |
| Huliaipole | UA | 47.6607145, 36.2732384 | |
| Tokmak | UA | 47.2464085, 35.7098364 | |
| St. Petersburg | RU | 60.0793208, 31.8926644 | |
| Taganrog | RU | 47.2125752, 38.9159658 | |
| Stavropol | RU | 45.0390116, 41.9631954 | |
| Sakhalin | RU | 50.6909848, 142.9505689 |
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.
