Kremenchuk, Hadyach, Sumy: another evening of Russian missiles and the steady math of attrition

At 18:12 UTC on 25 June 2026, the open-source channel AMK Mapping posted a brief alert: another missile in Sumy Oblast. A minute later, the same channel logged a follow-on strike and pivoted its reporting frame toward Poltava Oblast, naming Kremenchuk. By 18:13 UTC, the third item in the sequence had narrowed the location further: something had disappeared near Hadyach, in Poltava Oblast. The three lines, separated by seconds, are the kind of artefact that the war has produced in volume and that the wider press cycle has learned to under-weight. They are also, on this evidence, the only public record of what happened in those particular minutes.

The arithmetic is the story. Russia's full-scale invasion of Ukraine is now in its fifth calendar year of daily long-range strikes against population centres far behind the front line. Reporting from a single Telegram channel is, on its own, a thin evidentiary basis — but the channel's function is precisely to timestamp events the wire services arrive at hours later, and the pattern it documents is consistent with what Ukrainian and Western outlets have tracked for months. The structural fact is not that any one of these strikes is unusual; it is that they have become continuous, that the geographic spread (Sumy in the northeast, Poltava in the centre) compresses the distance between cities Ukrainians assumed were out of range, and that the local silence between alert and confirmation is itself a feature of the conflict's information environment.

The geography of the evening

Sumy Oblast and Poltava Oblast sit on either side of central Ukraine. Sumy, in the northeast, has been a regular target of glide-bomb and missile fire throughout 2025 and 2026, with the regional military administration publishing near-daily evening tallies of damage to civilian infrastructure. Poltava, south of Sumy and east of Kyiv, was the site of one of the war's most heavily publicised strikes in June 2023, when a Russian missile hit a crowded shopping centre in Kremenchuk. Hadyach, the smaller settlement named in the third AMK Mapping item, lies in the northern part of Poltava Oblast and has appeared in periodic strike tallies without drawing sustained international coverage. The cluster of three locations inside roughly an hour is the kind of dispersion that suggests a salvo rather than a single launcher — a routine feature of Russian deep strikes, and a routine absence from the morning news.

What the channel is, and what it is not

AMK Mapping is one of several volunteer-run open-source intelligence accounts that publish geolocated strike reports in near real time. Its posts are short, unverified, and often corrected in follow-up messages; they are not primary documentation in the way a Ukrainian Air Force briefing or a regional military administration update is. The Ukrainian Air Force's official channels, the regional military administrations in Sumy and Poltava, and the State Emergency Service are the bodies that publish confirmed casualty and damage figures, and the wires typically wait for those before reporting. The three items in this thread predate any such confirmation by hours. They are best read as a clock-pulse, not a verdict.

That distinction matters. In a war where the dominant Western framing has tilted toward negotiation and fatigue, the raw temporal record of strikes functions as a corrective — a reminder that the day-to-day experience of cities like Sumy, Kremenchuk and Hadyach is not captured by the rhythm of summit announcements. The same corrective applies to Kyiv's own public communication, which has incentives to consolidate events into daily evening addresses rather than flag each individual launch. The Telegram layer fills a gap that the official layer, by design, leaves open.

The structural frame, in plain terms

The pattern on display is the steady industrialisation of long-range strike. Russia has, over the course of the war, shifted from scarcity — a handful of expensive cruise missiles, rationed and announced — to throughput. Production of Shahed-type drones, ballistic missiles, and glide-bomb kits has scaled to the point that salvoes against multiple oblasts in a single evening are operationally routine rather than exceptional. The Western commentary cycle, by contrast, still tends to treat major strikes as discrete events, each meriting its own headline. The mismatch between daily reality and weekly news rhythm is itself part of the political economy of the war: it is easier to summon political will around a single named atrocity than around a slow background rate of damage.

The counter-narrative — that Ukraine's air-defence intercept rate is the relevant metric, and that most missiles are shot down — is real and Ukrainian sources have published interception data to support it. The trouble with that framing is that an intercept rate of 80 or 90 percent, applied to a salvo of dozens, still leaves a residual that accumulates across evenings like the one described here. The arithmetic of attrition runs in both directions, and the cost of being the city that absorbs the residual is paid in infrastructure, in displacement, and over a long enough horizon, in the willingness of partners to keep underwriting the air-defence bill.

What remains uncertain

The three AMK Mapping items do not specify weapon type, target, casualty count, or damage. They do not say whether the strike near Hadyach was the same event as the Poltava Oblast alert or a separate one. Ukrainian and regional authorities had not, at the time of the final post in the sequence, published a corresponding confirmation. The wires typically catch up within twelve to twenty-four hours, and a fuller picture — including any intercepted debris, any damage to energy infrastructure, any disruption to rail traffic through Kremenchuk — will likely emerge in the next daily cycle. Until then, the most that can honestly be said is what the timestamps already say: that on the evening of 25 June 2026, missile fire was reported across two oblasts in central and northeastern Ukraine, that the tempo matched the established pattern, and that the cost of the pattern continues to be paid in places most international coverage does not name.

How Monexus framed this: the wires will, in due course, report what happened at Kremenchuk, near Hadyach, and in Sumy Oblast. We chose to publish the prompt itself, with its source and its limits, because the rhythm of the war is part of the story, and the rhythm is what the open-source channel captures first.

Wire provenance

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

• https://t.me/AMK_Mapping