A ninety-minute window on Ukraine's southern coast

At 23:29 UTC on 28 August 2026, the open-source mapping channel AMK Mapping reported that at least six Russian Banderol cruise missiles and Geran-2 drones were flying toward Mykolaiv from the south, with a Su-34 detected over Crimea that might launch cruise missiles against Odesa. Two minutes later the channel logged explosions in Mykolaiv, and over the following three hours it continued to post repeated strikes from Banderol cruise missiles and Geran-2/4 drones across the city, with the barrage running into the early hours of 29 August. By 02:37 UTC a Russian naval formation had changed course for Odesa city from roughly ninety kilometres offshore; by 02:39 UTC, explosions were being heard inside Odesa itself.

In ninety minutes the southern coast absorbed two distinct strike tracks, and the channel that documented them compressed the night's whole logic into six short posts. Read together, those posts describe not a single dramatic blow but a routine that has hardened into something close to policy: layered pressure on two port cities whose daily functioning depends on infrastructure that absorbs repeated hits.

What the six posts actually say

The Mykolaiv barrage on 28-29 August was layered rather than singular. AMK Mapping's timeline shows an explosions-in-Mykolaiv post at 23:31 UTC, a fresh salvo from Banderol cruise missiles and Geran-2/4 drones flagged at 00:07 UTC on 29 August, and a continuing pattern of Geran-2/4 strikes logged at 00:26 UTC. The opening post described at least six cruise missiles and Geran drones arriving from the south, with the additional Su-34 over Crimea signposted as a possible launch platform for a follow-on package against Odesa.

The division of labour in the salvo is consistent with how the channel frames Russian strike packages: cruise missiles grouped with drone swarms in the same bulletin, with the drones reported separately in the second and third posts as the dominant sound over Mykolaiv in the early hours. The cruise-and-drone combination is itself a routine the channel has logged before; what is distinctive about this overnight is the simultaneous naval tease off Odesa while the first barrage was still running.

The naval tease off Odesa

Ninety minutes after the first Mykolaiv strike, attention shifted ninety kilometres down the coast. AMK Mapping reported at 02:37 UTC on 29 August that a Russian formation had been tracked about ninety kilometres from the coast before changing course toward Odesa city, and within two minutes, at 02:39 UTC, the channel logged explosions in the city. The geography matters: Mykolaiv sits at the confluence of the Southern Bug, Odesa sits on the open Black Sea, and between them lie the ports through which Ukraine has continued to export grain and steel despite the war.

The dual-track pattern, a missile-and-drone package against one city while a naval group manoeuvres off another, is read here as the same script that has played out repeatedly in the items available to this article. The aim, in this assessment, is rarely a single decisive blow; it is to keep both cities' residents and port workers inside the sound of air-raid sirens, to stretch Ukrainian air defence across two fronts, and to remind foreign insurers and shippers that the western Black Sea is not a normal sea lane.

Monexus assessment

Read together, the six AMK Mapping posts describe a routine that has hardened into policy. Russia does not need to sink a vessel or destroy a grain silo to register strategic effect; it needs only to ensure that no week on the southern coast passes without a recognisable pattern of explosions, and that every few weeks one of those patterns is large enough to make the wire. The Mykolaiv package was modest by the channel's own framing, half a dozen cruise missiles and an unspecified drone swarm, but the simultaneous tease off Odesa turned a local strike into a coastal event.

This publication's assessment: the channel's overnight output is best read as Moscow signalling patience rather than preparing a one-shot escalation. The pattern of missile-and-drone packages on Mykolaiv while a surface group pressures Odesa is consistent with a strategy of cumulative harassment rather than a discrete operation. What remains on the Ukrainian side is a coastal-defence posture whose currency, per the items available here, is the resilience of two cities under near-nightly bombardment.

What remains uncertain

The available posts are tactical and unverified beyond AMK Mapping's own OSINT work. The channel does not specify interception rates, casualties, or damage to port infrastructure in either city; it does not name the Russian formation off Odesa, its composition, or its weapons fit. Independent Ukrainian air-force reporting for the overnight of 28-29 August had not, in the cited posts, been published. The Su-34 over Crimea, the source notes, might launch against Odesa, language that signals detection without confirmation of employment. Readers should treat the casualty and damage picture in both cities as preliminary until Ukrainian official channels and Western wires publish their own tallies.

The pattern, however, is already clear in the items available: on the southern coast, the war is now a metronome, and the metronome ticked twice in ninety minutes on the night of 28-29 August.

Desk note: Monexus frames this as routine attrition against two Ukrainian port cities under invasion, sourcing the tactical timeline to a single open-source mapping channel and labelling the assessment as such, rather than as a stand-alone tactical claim. Where a Russian-aligned framing would describe the strikes as legitimate pressure on military-logistics targets, the article instead foregrounds the cumulative effect on civilian port infrastructure and the structural aim of normalising nightly bombardment, as recorded by an OSINT channel that is neither Ukrainian official nor Russian state media.

Wire provenance

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

• https://t.me/AMK_Mapping/36647
• https://t.me/AMK_Mapping/36652
• https://t.me/AMK_Mapping/36667
• https://t.me/AMK_Mapping/36672
• https://t.me/AMK_Mapping/36697
• https://t.me/AMK_Mapping/36702