Russian 'Oreshnik' Missiles Deploy to Belarus as UAF Degrades Crimean Radar Network and Encounters Fiber-Optic Drone Threat
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 over the last 12 hours is characterized by a high-intensity exchange of deep-rear strikes, technological adaptation on the forward line of contact, and strategic signaling. Ukrainian Armed Forces (UAF) successfully degraded Russian early warning and air traffic control infrastructure in occupied Crimea, prioritizing the systematic dismantling of the regional Integrated Air Defense System (IADS). Concurrently, Ukrainian deep strikes continue to stress Russian domestic infrastructure, resulting in a total blackout in Belgorod and airspace closures over Moscow.
In response, the Russian Federation is escalating its strategic deterrence posture by deploying "Oreshnik" ballistic missile systems to Belarus under the newly formalized Union State security integration. Tactically, Russian forces are bypassing Ukrainian Electronic Warfare (EW) dominance in the northern sector through the introduction of fiber-optic guided FPV drones, while actively targeting Ukrainian unmanned ground logistics in the Donbas.
Operational Updates
- Northern Sector (Kharkiv/Chernihiv/Sumy): A Russian fiber-optic guided FPV drone—rendering it immune to traditional EW jamming—successfully impacted Kharkiv, marking a significant technological shift in the sector. A Russian ballistic missile successfully penetrated air defenses in Chernihiv, resulting in a confirmed impact. Russian tactical aviation maintains a high frequency of Guided Aerial Bomb (KAB) strikes targeting Sumy. Weather in Vovchansk (0.8°C, 100% cloud cover, wind 2.4 m/s) continues to degrade optical ISR capabilities.
- Eastern Sector (Donetsk/Luhansk): In the Kostiantynivka direction, Russian forces have begun utilizing FPV drones specifically to interdict UAF Unmanned Ground Vehicles (UGVs) utilized by the "SKELE" unit for MEDEVAC and last-mile logistics. This "drone-vs-robot" engagement highlights the increasing automation of contested supply lines. Ground conditions in Pokrovsk (0.7°C, 100% cloud cover, wind 4.6 m/s) remain saturated, stalling heavy mechanized maneuver.
- Southern Sector (Zaporizhzhia/Kherson/Crimea): UAF strikes successfully destroyed a Russian P-18 "Terek" and an RSP-6M2 radar system in Dzhankoi, Crimea, degrading local airspace monitoring. Concurrently, Russian tactical aviation shifted targeting vectors, launching KABs at Zaporizhzhia and Dnipropetrovsk, while UAF Air Force reports a shift in hostile UAV flight paths toward Mykolaiv.
- Deep Rear & Counter-Logistics: UAF precision strikes targeted a Russian command post in Bryansk. Ukrainian FP-1 drones successfully struck the "Dorogobuzh" plant in Smolensk, destroying ammonium nitrate production capacity. Drone incursions triggered the closure of Moscow airspace, and targeted strikes induced a total energy blackout affecting 10,000 residents in Belgorod.
Equipment & Losses
- Confirmed: 1 Russian P-18 "Terek" radar system destroyed in Dzhankoi, Crimea.
- Confirmed: 1 Russian RSP-6M2 radar system destroyed in Dzhankoi, Crimea.
- Confirmed: Unspecified number of UAF Ground Robotic Complexes (UGVs) destroyed by Russian FPVs near Kostiantynivka.
- Sighting: Russian "Oreshnik" ballistic missile systems deployed on combat duty in Belarus.
- Sighting: Deployment of new Russian fiber-optic guided FPV drone (estimated 50km range) in the Kharkiv sector.
- Development: Russian State Duma passed legislation banning the extradition of foreign nationals serving in the Russian Armed Forces, legally shielding foreign recruits.
Confidence Check
- HIGH: UAF destruction of radar assets in Dzhankoi; Belgorod energy blackout; Moscow airspace restrictions; deployment of UAF UGVs.
- MEDIUM: Combat readiness status of "Oreshnik" systems in Belarus; specific destruction of ammonium nitrate capacity at the Smolensk "Dorogobuzh" plant.
- LOW: Russian claims of a fabricated open letter from Hungarian PM Orbán to President Zelenskyy; uncorroborated Russian claims of striking exclusively UAF UAV launch sites in the border region.
The Bottom Line
The destruction of specialized early-warning radars in Crimea severely limits Russian situational awareness over the Black Sea, likely forcing a repositioning of surviving air defense assets. Russia's deployment of the "Oreshnik" system to Belarus following the Union State security agreement signals a long-term strategic threat axis aimed at Central/Western Ukraine and NATO observers. On the tactical level, the introduction of fiber-optic drones and the interdiction of robotic supply lines indicate a rapidly accelerating technology cycle where EW immunity and unmanned ground logistics will dictate localized tactical success. Watch for immediate Russian retaliatory strikes leveraging ballistic assets against Ukrainian energy or C2 nodes over the next 12-24 hours.
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 25 Feb 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.
Report Visuals
5 visualsGeospatial Analysis
18 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 18 places with coordinates
| Place | Country | Latitude, longitude | Copy |
|---|---|---|---|
| Dzhankoi | Ukraine | 45.7353108, 34.4782161 | |
| Kharkiv | Ukraine | 50.00201269999999, 36.3073994 | |
| Chernihiv | Ukraine | 51.4982, 31.28935 | |
| Sumy | Ukraine | 50.9077, 34.7981 | |
| Vovchansk | Ukraine | 50.284234, 36.9329429 | |
| Kostiantynivka Direction | Ukraine | 48.52394289999999, 37.7075811 | |
| Pokrovsk | Ukraine | 48.282193, 37.1847804 | |
| Zaporizhzhia | Ukraine | 47.83928419999999, 35.13870970000001 | |
| Dnipropetrovsk | Ukraine | 48.464717, 35.046183 | |
| Mykolaiv | Ukraine | 46.9660801, 32.003246 | |
| Bryansk | Russia | 53.2635306, 34.41611 | |
| Smolensk | Russia | 54.7903112, 32.0503663 | |
| Moscow | Russia | 55.7568721, 37.6150527 | |
| Belgorod | Russia | 50.5997134, 36.5982621 | |
| Belarus | Belarus | 53.709807, 27.953389 | |
| Air Defense Radars Site | Russia | 61.52401, 105.318756 | |
| Repair-Technical Base | Russia | 61.52401, 105.318756 | |
| UI Site | Russia | 61.52401, 105.318756 |
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.
