Russia's long-range drone tempo against Ukraine's fuel grid, in one overnight shift

In the space of roughly seven minutes on the morning of 25 June 2026, the open-source mapper AMK_Mapping logged four separate Russian long-range drone impacts across two Ukrainian oblasts: a Geran-3 jet drone on a warehouse in the village of Orilske, Dnipropetrovsk Oblast (48.59253, 34.83514); a pair of Geran-2 strikes on a petrol station inside Sumy city; a further Geran-2 hit on a fuel station near Krolevets in Sumy Oblast; and an operator-controlled Geran-2 strike on a fuel storage facility near Hubynykha, Dnipropetrovsk Oblast, reportedly being used by the Ukrainian military. The picture is fragmentary — single-channel, geolocated from the field rather than from a wire-service pool — but the targeting pattern is consistent. Moscow is hitting fuel.

The pattern matters more than the four incidents do individually. Since early 2024, Russian doctrine against Ukraine has rotated between two long-range strike targets: the civilian power grid in winter, and the fuel-refining and storage network in shoulder seasons. What the 25 June log shows is the second of those cycles in working order: drones hitting depots, retail forecourts and at least one site flagged by the mapper as a military fuel point, with no obvious attempt in the timestamped items to mass-strike a thermal plant or substation on the same night. That is a coherent choice. Ukrainian air-defence crews report fuel interdiction as a quieter, more cumulative problem than grid attacks, because each individual loss is small but the aggregate pressure on logistics is not.

What the four strikes actually tell us

Read narrowly, the four items are simple incident reports. The Geran-3 on Orilske is the highest-profile hit: a jet-powered variant striking a warehouse facility in a village setting suggests either a high-value structure or a target nominated from ISR rather than a generic urban aim-point. The two Geran-2 strikes in Sumy city and at Krolevets hit civilian fuel retail — a slow-acting way to degrade local vehicle availability, emergency-services fuelling, and the willingness of civilians to drive. The Hubynykha strike is the most operationally interesting. The mapper's note — that the storage facility was "reportedly being used by the Ukrainian military" — is the only one in the batch that escalates the target from a logistics nuisance to a directly military object. If that characterisation holds up in subsequent Ukrainian General Staff reporting, it brings the strike inside the recognised category of legitimate military target and removes the protective ambiguity that civilian forecourts enjoy under the law of armed conflict.

The drone type is itself a small data point. Geran-2 — a re-engined, Iranian-designed Shahed-136 derivative produced under Russian serial-manufacturing arrangements — is the workhorse loitering munition. Geran-3, the jet variant, is faster, more expensive, and typically reserved for higher-priority nominations. The fact that Moscow is willing to spend a Geran-3 on a village warehouse means either the target was genuinely high-value, or the supply of jet drones has improved enough that they are no longer being husbanded. Either reading is a separate piece of intelligence, and both bear watching.

The counter-narrative the Russian framing pushes

Russian state and state-adjacent messaging around long-range strikes has, since 2024, consistently framed them as retaliation for Ukrainian strikes on Russian refining and storage — including, periodically, attacks claimed or attributed to Ukrainian long-range drones and ATACMS rounds on the Belgorod, Krasnodar and Volgograd refinery belts. The implicit line is parity: each side hits the other's fuel, and the question is who runs out first. The Ukrainian counter — articulated in Kyiv Post, Ukrainska Pravda and Western-wire coverage of the 2024-25 strikes — is that the underlying situation is not symmetrical, because Ukraine is the invaded party and its strikes inside Russia are responses to an aggressor's campaign against critical civilian and military infrastructure on Ukrainian territory. Both framings can be true at once, and a serious reader should hold them together: the immediate tactical picture is reciprocal, the strategic picture is not.

What the longer arc suggests

A plain-language reading of four overnight strikes is that they are evidence of a working kill-chain, not a war-winning one. Russian long-range production has, on every credible public estimate, scaled faster than Ukrainian air-defence interceptor supply. That asymmetry does not need a clever theoretical frame; it is observable in the cadence of items like the 25 June log, where four separate incidents sit inside a quarter-hour window with no suggestion that any of them were intercepted on the way down. The structural question for Kyiv and its partners is whether fuel-grid hardening — passive protection for depots, decentralised retail inventory, and a faster rotation of fuel points closer to the line — is being treated with the same seriousness as grid hardening was in the winter of 2022-23. The 25 June log is one night in a long campaign, but the kind of night on which that question gets asked.

What remains genuinely uncertain is the scale of damage at each site and whether the Hubynykha characterisation as a military fuel point is corroborated by Ukrainian official briefings. The sources available to Monexus at the time of writing do not specify casualty figures, fire-suppression response, or operational downtime at any of the four facilities. AMK_Mapping is a useful open-source pointer, not a substitute for the Ukrainian Air Force or General Staff daily disclosures, and any policy reading of the night should wait until those disclosures appear.

Desk note: Monexus treats AMK_Mapping as a primary open-source geolocation feed for Russian strike patterns, but flags it as a single-channel source pending Ukrainian official corroboration. The piece is grounded in four timestamped Telegram items and does not extrapolate to claims that those items do not support.

Wire provenance

This editorial synthesis draws on the following public wire/social posts:

• https://t.me/AMK_Mapping/1
• https://t.me/AMK_Mapping/2
• https://t.me/AMK_Mapping/3
• https://t.me/AMK_Mapping/4