Updated daily at 09:00 (EET) Index methodologyRSS
Issue of July 26, 2026 · Sunday

Ukraine's drone war against Russia shifts away from the Baltic-adjacent north-western corner

Digest: military preparations in the Baltics and the wider region

Escalation index: 4.1/10 · elevated

Issue of 26 July 2026 — covering 25 July – 26 July 2026

Note: the previous issue was dated 25 July 2026 (escalation risk 4.2/10). The 25–26 July window remained quiet for direct NATO–Russia incidents inside the Baltics proper: no fresh dated interceptions of Russian aircraft over the Baltic, no border violations of Estonia/Latvia/Lithuania, and no confirmed drone alerts over the Baltic states dated 25 or 26 July — the skies over the three countries were calm in the window. The dominant background shift of the cycle: Ukraine's intensive drone war against Russia continues, but in the 25–26 July window it moved away from the north-western corner bordering the Baltics (Leningrad and Pskov oblasts, St. Petersburg) toward central, Volga and southern regions of Russia. Per Russian MoD tallies, 328 UAVs were downed nationwide overnight into 25 July (22 regions — the Black Earth belt, the Volga, the South, the Moscow region, Crimea, the Sea of Azov) and a further 146 during the day of 25 July (Belgorod, Bryansk, Vladimir, Kaluga, Kursk, Oryol, Ryazan, Tula, Tyumen oblasts, the Moscow region, Krasnodar Krai, Crimea, the Sea of Azov); neither tally lists Leningrad/Pskov oblasts or St. Petersburg — after the largest strike in the series on 24 July, the north-western corner went quiet in the window. The second dated event of the window is Russian Navy Day on 26 July (the fleet's 330th anniversary): the main naval parade in St. Petersburg and Kronstadt has been cancelled for the second year running, with no salute — a restrained naval posture at the north-western corner confirmed on the holiday itself. A 2026 "July Storm" fleet-wide exercise involving the Baltic Fleet still has no official announcement. The kinetics remain directed against Russia (spillover from the Russia–Ukraine war), not against NATO.


Top stories of the day

  1. 25.07 — Ukraine's drone war against Russia shifts away from the Baltic-adjacent north-western corner: 328 UAVs downed overnight into 25 July across 22 regions per the Russian MoD — Leningrad/Pskov oblasts and St. Petersburg absent from the tally. Per the official Russian MoD summary, between 20:00 on 24 July and 08:00 on 25 July air defences destroyed 328 fixed-wing Ukrainian UAVs over 22 regions: Belgorod, Oryol, Voronezh, Ulyanovsk, Volgograd, Nizhny Novgorod, Saratov, Bryansk, Samara, Kirov, Rostov, Tula, Kursk, Ryazan and Lipetsk oblasts, the Moscow region, Krasnodar Krai, Crimea, Chuvashia, Kalmykia, Mari El and the Sea of Azov. Key for the region: the north-western, Baltic-adjacent corner (Leningrad and Pskov oblasts, St. Petersburg) is absent from this tally — after the largest strike in the series on the NW on 24 July (571 claimed nationwide, 59 over Leningrad oblast, 30+ over the Pskov area — previous issue, out of window), the drone kinetics in the window shifted to the Black Earth belt, the Volga and the South. The fact of the ongoing massive drone war is not disputed, but the national figure "328" rests on a single official source (Russian MoD) and is not independently verified. ⚠️ Contradiction (high-profile figure): "328" is presented as a Russian claim, not an established fact; the regional breakdown has no independent confirmation (two-source rule). Sources: Interfax (25.07, direct link — citing the Russian MoD); RIA/EADaily/ura.news — restricted outlets, no direct links (citing the same MoD summary).

  2. 25.07 — During the day of 25 July the Russian MoD reported a further 146 UAVs downed — again without Leningrad/Pskov oblasts or St. Petersburg: confirmation the strike moved south and central, not onto the Baltic flank. Per the MoD summary, between 08:00 and 20:00 on 25 July 146 Ukrainian drones were destroyed over Belgorod, Bryansk, Vladimir, Kaluga, Kursk, Oryol, Ryazan, Tula and Tyumen oblasts, the Moscow region, Krasnodar Krai, Crimea and the Sea of Azov. The Baltic-adjacent regions (Leningrad and Pskov oblasts, St. Petersburg) are again absent — a second same-day confirmation that in the 25–26 July window the vector of Ukrainian strikes passed clear of NATO's eastern flank, lowering the background risk of an unintended overflight near the Baltics in this window specifically. The figure "146" rests on a single official source (Russian MoD) and is not independently verified; presented as claimed. Sources: Kommersant (25.07, direct link — citing the Russian MoD); m24.ru (25.07); vz.ru/EADaily/ura.news — restricted/sanctioned outlets, no direct links.

  3. 26.07 — Russian Navy Day (the fleet's 330th anniversary): the main naval parade in St. Petersburg and Kronstadt is cancelled for the second year running, with no salute — a restrained naval posture at the NW corner confirmed on the holiday itself. On Sunday 26 July Russia marks Navy Day (the last Sunday of July; in 2026 the jubilee 330th anniversary). The main naval parade in St. Petersburg and Kronstadt — as in 2025 — is not being held; the traditional salute is also cancelled, the programme reduced to concerts, exhibitions and museum events. The decision (parade not prepared; a Navy spokesperson's "it's not the right time") was announced in mid-June and is linked by independent outlets and UK Defence Intelligence to the threat of Ukrainian strikes on the water (including after the 3 June strike on Kronstadt that damaged the corvette Boikiy, project 20380, assigned to the Baltic Fleet — context). What falls into the window is the materialisation of that decision on the holiday itself: no parade and no salute at the NW corner. The fleet-wide "July Storm" manoeuvre involving the Baltic Fleet, expected near the window's horizon (23–27 July in 2025), still has not materialised as a confirmed 2026 event: there is no open-source official announcement of a 2026 analogue. Both signals point to a defensive-cautious naval posture at the NW corner. Sources: The Moscow Times (context, 15.06); United24 Media (context, "second year running"); Lenta/RIA — restricted outlets, no direct links (Navy Day programme 26.07).


By area, in detail

Construction of military facilities and fortifications

No new events dated 25–26 July along the Baltic Defence Line in the window. Neighbouring-window context (unchanged): Latvia — by end-September 2026 the entire eastern border is to be covered by automated counter-drone systems and radars (continuous acoustic drone detection, integration of Giraffe 1X radars); the 280 km fence on the border with Russia completed (end-2025). Estonia — ~28 pilot bunkers, >10 km of anti-tank ditches, ~20,000 "dragon's teeth", a patrol road on radar masts along the Narva River, a military settlement in Narva ~150 m from the border (construction to end-2026, commissioning summer 2028, ~200 personnel of the 1st Infantry Brigade permanently). Latvia — ~27 km of anti-tank ditches (to autumn 2027), the largest Baltic training area "Sēlija" in the south-east (~25,000 ha). Lithuania — three rows of "dragon's teeth" and >8 km of infrastructure in 2026, a brigade-size training area at Kapčiamiestis in the heart of the Suwałki corridor (€100m). The full Baltic Defence Line — by end-2027. Sources: context from prior issues (eng.LSM; ERR — Narva; Militarnyi; president.lv — Sēlija; kaitseministeerium.ee).

Deployment and movement of troops

No new rotations/redeployments of combat units in the Baltics dated 25–26 July in the window. Active context: Lithuania's deployment of up to 30 personnel to guard the Klaipėda LNG terminal, the LitPol Link (Alytus substation) and the Kruonis pumped-storage plant (order 17.07, term 19.07–19.08) — amid warnings of possible Russian provocations against critical infrastructure. Other context (out of window): the UK battlegroup at Tapa re-equipping from Challenger 2 tanks to strike drones and growing (~800 → ~1,200); phase 2 of the German 45th Panzer Brigade base at Rudninkai near the Belarusian border; Latvian and Estonian land forces under the operational command of the 1st German-Netherlands Corps (since 1.07); the Multinational Corps Northeast shifting focus to Poland and Lithuania (Suwałki corridor); the Baltic "military mobility zone" (agreement 30.01). Sources: context from prior issues (LRT 17–19.07 — infrastructure guarding; militarnyi.com; estonianworld; mod.gov.lv/eng.LSM — command change 30.06).

Agreements and spending

No fresh agreements/spending decisions dated 25–26 July in the window. General outline (context): on 2026 estimates Lithuania (~5.3–5.38%), Estonia (~5.1%) and Latvia (~4.9% of GDP) sit in NATO's top group by defence-spending share; Estonia's PM K. Michal cites a combined ~7% of GDP (5.4% core + 1.5% related). Lithuania and Latvia agreed on joint military exercises at Latvia's "Sēlija" training area (presidents' statements, ~15.07 — context). The Riga declaration of the energy ministers of Lithuania, Latvia and Estonia on joint power-grid reserves, tied to drone and critical-infrastructure protection (22.07 — context). Sources: context from prior issues (ICDS 07.2026; Euronews 15.07; LRT 22.07; The Baltic Times 22.07).

Military aid and air defence / EW

No fresh deliveries/air-defence decisions inside the Baltics dated 25–26 July in the window. Structural context (unchanged): the "combat" mandate of NATO's Baltic air-defence mission (since 9.07 — pilots may down threats without political consultation); Latvia's plan for continuous counter-drone and radar coverage of the eastern border by end-September; the arrival in Estonia of the first IRIS-T SLM components (June); the persistent backdrop of Russian GPS jamming/spoofing over the Baltic, northern Poland and the Suwałki corridor (hybrid activity, officially qualified by regional states). Sources: context from prior issues (eng.LSM 9.07; ERR; mil.ee; Militarnyi; Defense News — GPS jamming).

Kaliningrad and Russia's border regions

The freshest dated NW-corner development in the window is the shift of Ukraine's drone kinetics away from the Baltic-adjacent north-west: in both Russian MoD summaries for 25 July (overnight — 328 UAVs across 22 regions; daytime — 146 UAVs) Leningrad and Pskov oblasts and St. Petersburg are absent; the strikes in the window fell on the Black Earth belt, the Volga and the South (see Top stories 1–2). After the largest strike in the series on 24 July (out of window), the NW corner went quiet in the window — the unintended-overflight factor at NATO's eastern flank is lowered in this window. Naval posture: the main Navy Day parade (26 July, the fleet's 330th anniversary) in St. Petersburg and Kronstadt is cancelled for the second year running, with no salute (see Top stories 3); "July Storm" 2026 has no official announcement — a signal of restraint at the NW corner. No Baltic Fleet manoeuvres/exercises at Kaliningrad ranges dated 25–26 July appear in open sources; Kaliningrad's structural posture (Bal/Bastion coastal missiles, Iskanders, EW) is a constant backdrop with no fresh dated steps in the window. The "Baltic corridor" narrative (unreliable): the Russian line that Ukrainian drones supposedly transit through the Baltic states' airspace (statements by Russian Deputy FM M. Galuzin on 4 July, D. Peskov on 13 July — out of window) is not backed by any new kinetics in this window and remains rejected by the Baltic states (a joint chargés d'affaires demarche at the Russian MFA on 10 July); it has no independent confirmation, and the documented March–May incidents ran in the opposite direction (from Russia into the Baltics) — we present the Russian line as unverified/propagandistic. Economic-administrative track (context): the full ban on Estonian trucks transiting Russia (decree of 18.07) remains in force. Sources: Interfax (25.07 — 328 UAVs); Kommersant (25.07 — 146 UAVs); The Moscow Times/United24 (context — Navy Day parade cancellation); TASS/RIA/EADaily/Lenta — restricted outlets, no direct links.

Statements

Few key defence statements by top officials inside the Baltics are dated 25–26 July in the window. Active backdrop (context): the presidents of Lithuania (G. Nausėda) and Latvia warned of possible Russian attacks on Baltic or Polish critical infrastructure, citing intelligence (~15.07); Lithuania's Defence Minister Robertas Kaunas reiterated that Moscow may view the Baltics or Poland as the next target, while the Lithuanian army chief stresses the absence of an immediate conventional-attack threat (~20.07). The Baltic states continue to publicly reject the Russian campaign about the "use of their airspace" by Ukrainian drones as baseless. Sources: Euronews (15.07 — presidents' warnings); context from prior issues (LRT — Kaunas/army chief; Baltic states' joint rebuttals).


⚠️ Contradictions and discrepancies

  • The shift of drone kinetics away from the NW corner — a clarification of the previous issue, not an error. The 25 July issue noted that "there is no confirmed repeat of the raid overnight into 25 July [on the NW corner]." This held: the drone war continued in the window (328 overnight into 25 July, 146 during the day of 25 July — per the Russian MoD), but it passed clear of the Baltic-adjacent north-west — Leningrad/Pskov oblasts and St. Petersburg are in neither tally. There is no substantive error in the previous issue; no correction is required.
  • The national figures "328" and "146" UAVs for 25 July rest on a single official source (Russian MoD). The regional breakdown is not independently verified; presented as a Russian claim, not an established fact (two-source rule). The fact of the continuing massive drone war against Russia is not independently disputed.
  • The Russian "Baltic air corridor" narrative for Ukrainian drones — unreliable. The Russian line (Galuzin/Peskov, out of window) is not backed by any new kinetics in this window (the strikes fell on southern/central Russia, not via the Baltic), is rejected by the Baltic states and has no independent confirmation; the documented March–May incidents ran in the opposite direction. Flagged as propagandistic/unverified.
  • The Navy Day parade cancellation — on 26 July this is a dated event of the window (materialisation), but the original decision is mid-June context. It is not presented as a "fresh 25–26 July decision"; what falls into the window is the fact of no parade and no salute on the holiday itself.
  • Filtering out "stale context." The largest strike on the NW corner on 24 July (571/59/30+), the 23 July Baltic Fleet naval-aviation exercise, "July Storm" 2025, the 30.06 command change and the 30.01 "military mobility zone" are NOT included as fresh events for the 25–26 July window and are marked as context.
  • No substantive errors requiring a corrections.json entry were identified in previous issues in this cycle.

📊 Escalation risk assessment (0–10): 4.1 / 10

Drivers on the Russian side:

  • The structural posture of the Baltic Fleet/Kaliningrad (Bal/Bastion coastal missiles, Iskanders, aircraft dispersal, EW/GPS jamming over the Baltic) — a constant A2/AD backdrop at the eastern flank; no fresh dated manoeuvres in the 25–26 July window.
  • Information/propaganda backdrop: the line about the "use of Baltic airspace" by Ukrainian drones — a rhetorical driver with no kinetics against NATO; not backed by new kinetics in this window (the Ukrainian strikes fell on southern/central Russia), rejected as disinformation.
  • Restraint as a reverse signal: cancelling the main Navy Day parade for the second year running (on the holiday itself, 26.07) and the non-announcement of "July Storm" 2026 point to a defensive-cautious naval posture at the NW corner, not to an offensive build-up.

Drivers on the NATO side and its members:

  • NATO's "combat" air-defence mandate over the Baltic (since 9.07) — a constant rapid-response factor at the eastern flank (with no dated use in the window).
  • NATO's structural weight at the Russian/Belarusian borders: strike-drone re-equipping of the UK battlegroup at Tapa, the German 45th Panzer Brigade base at Rudninkai, the Narva military settlement, the Baltic Defence Line, the "military mobility zone", the corps' focus shifts (German-Netherlands — Estonia/Latvia; Northeast — Poland/Lithuania/Suwałki) — a structural "hardening" (context, with no fresh dated steps in the window).
  • Hard rhetoric: warnings by the presidents of Lithuania and Latvia of Russian strikes on critical infrastructure, and Lithuania's defence minister (Moscow may view the Baltics/Poland as a target) — rhetorical drivers with no dated kinetic steps in the window.

Mutual/structural factors:

  • Transfer of Russia–Ukraine war kinetics toward the region: the massive drone war continues (328 + 146 claimed UAVs on 25 July) but in this window shifted away from the Baltic-adjacent NW corner to southern and central Russia — the unintended-overflight factor at the eastern flank is lowered in the window relative to the previous issue.
  • Baltic EW/GPS spoofing (Kaliningrad), the Suwałki corridor and mutual information warfare — a long-horizon structural backdrop.

Stabilisers:

  • Calm skies over the Baltics proper: no new interceptions, border violations or confirmed drone alerts over Estonia/Latvia/Lithuania dated 25–26 July.
  • Drone kinetics shifting away from the Baltic flank: both dated 25 July strikes (328 overnight, 146 daytime) fell on southern and central Russia; the Baltic-adjacent Leningrad/Pskov oblasts and St. Petersburg are outside the tallies, the NW corner quiet in the window.
  • Vector of kinetics — against Russia, not NATO: the drone activity is spillover from the Russia–Ukraine war; no direct NATO–Russia clashes in the window.
  • Russia's restrained naval posture: cancelling the Navy Day parade for the second year running (on the day itself, 26.07) and the non-announcement of "July Storm" 2026 — a signal of caution, not of an offensive build-up.
  • The defensive-resilient character of Baltic measures (infrastructure guarding, the Baltic Defence Line, the "combat" air-defence mandate as a controlled response mechanism).

Rationale for the score: relative to 4.2 (25 July) the risk is nudged down to 4.1. The key driver of recent windows — the transfer of drone kinetics toward the Baltic-adjacent NW corner — weakened in this window: the massive war continues, but both dated 25 July strikes fell on southern and central Russia, and Leningrad/Pskov oblasts and St. Petersburg are in neither tally; the NW corner went quiet. Also pulling down: calm skies over the Baltics proper, the kinetics being directed against Russia, and Russia's restrained naval posture on Navy Day itself (parade cancelled for the second year running, "July Storm" not announced). Holding it up: unchanged structural factors (the high overall tempo of the drone war, the "combat" air-defence mandate, Rudninkai, the Baltic Defence Line, Kaliningrad). There are no direct NATO–Russia clashes inside the Baltics on either side. The score stays in the band of "routine-tense Cold-War manoeuvre confrontation with a heightened but, in this window, spatially receded spillover from the neighbouring war," well below Able Archer 1983 (≈7).

Historical analogue: routine-tense Cold-War manoeuvre confrontation (≈4–4.5) — structural force build-up and hard (including information) rhetoric on both sides, with no direct NATO–Russia incidents inside the Baltics proper; the continuing but flank-receded drone war and Russia's restrained naval posture balance the structural "hardening." Below Able Archer 1983 (≈7) and below the run-up to 2008/2014 (≈6–7).

Delta vs previous issue: ↓ (−0.1) — 4.2 (25 July) → 4.1 (26 July). Down — the spatial recession of drone kinetics from the Baltic-adjacent NW corner (both 25 July strikes on southern/central Russia, without Leningrad/Pskov oblasts or St. Petersburg), Russia's restrained naval posture on Navy Day itself (parade cancelled for the second year running, "July Storm" 2026 not announced), calm skies over the Baltics. No direct NATO–Russia clashes in the window; key structural drivers (the "combat" air-defence mandate, Rudninkai, the Baltic Defence Line, Kaliningrad) unchanged.

Caveat: an analytical assessment based on open sources, not a forecast. Some reporting on both sides is propagandistic; claims without independent confirmation are flagged in the text.


Sources