Skip to content
You can now search across every topic, entity and event.What's new
Iran Conflict 2026
6AUG

Two tanker claims, one logged blast

2 min read
15:43UTC

Houthi spokesman Yahya Saree claimed strikes on two tankers on 5 August, off Yanbu and in the Gulf of Aden. Only the Gulf of Aden explosion reached the incident log.

ConflictDeveloping
Key takeaway

The Houthis claimed two tanker strikes; UKMTO logged one explosion, and the vessel identification remains unconfirmed.

Houthi military spokesman Yahya Saree made two separate claims on Wednesday 5 August: a ballistic-missile strike on the tanker Wafaa off Yanbu on Saudi Arabia's Red Sea coast, and a strike on the tanker Daisy in the Gulf of Aden 1. Several wires merged them into a single vessel of disputed name 2. Yanbu and the Gulf of Aden sit more than 800 nautical miles apart, at opposite ends of the Red Sea, so evidence for one strike is no evidence at all for the other.

UKMTO (United Kingdom Maritime Trade Operations), the Royal Navy cell to which merchant captains report incidents at sea, recorded one event: a loud explosion 95 nautical miles south-east of Aden at 14:30 UTC, crew accounted for, no environmental impact 3. As of Thursday 6 August its record held nothing matching the Yanbu claim. A UKMTO log entry and a Saree announcement carry different evidential weight. A master reporting to UKMTO is describing something that happened to their own ship; a belligerent announcing a hit has every reason to claim ones it did not land. Cutting the other way, vessels in this corridor routinely run dark or decline to report, so an unlogged claim is weaker evidence of nothing having happened than an absent satellite fire signature would be. The Yanbu claim should be held open, not dismissed.

Naming the vessel rests on thinner ground still. The open-source analyst AtlasObserver tentatively named the Gulf of Aden vessel as the Dominica-flagged product tanker Daisy, International Maritime Organization (IMO) number 9516545, and no flag state, owner, insurer or official body has confirmed it 4.

The "eighth tanker since 22 July" figure now circulating is the movement's own running count, not a verified total, and that distinction carries a price. War-risk underwriters set premiums off demonstrated capability, and the Houthis have moved rates before by announcing intent, widening their target set to Yanbu and Jazan Aramco sites in late July and claiming strikes on crude transport infrastructure days later . An unverified claim, repeated widely enough, costs shipowners money whether or not a missile ever flew. Riyadh struck Houthi-held military sites near Hodeidah after the NCC Masa was hit off Al-Shuqaiq in July , , which is what turns a second unconfirmed claim into something more consequential than a bookkeeping dispute.

Deep Analysis

In plain English

A Houthi military spokesman said the group had struck two oil tankers, named Wafaa and Daisy, in the Gulf. The UK's maritime monitoring body, UKMTO, only recorded one explosion, and has not confirmed which ship, if either, was actually hit. Houthi claims about ship strikes have often run ahead of what can be independently verified.

Deep Analysis
Root Causes

Houthi strike claims have historically outpaced what UKMTO can independently confirm within the same window, and this claim follows that pattern: one explosion logged against two claimed strikes, with vessel identification still pending.

UKMTO's logging depends on vessel operators reporting in, and neither the Wafaa nor Daisy operator has yet confirmed which, if either, was hit.

What could happen next?
  • Risk

    A doubled claim against a single confirmed incident risks becoming the reported figure in wire coverage before either vessel operator responds, inflating the apparent tempo of Gulf strikes.

First Reported In

Update #166 · Two Hormuz deals, neither one published

gCaptain· 6 Aug 2026
Read original
Causes and effects
This Event
Two tanker claims, one logged blast
War-risk premiums are being set off a tally the attacking party maintains, with no independent reconciliation of what was actually hit.
Different Perspectives
Hengaw
Hengaw
The Norway-based monitoring group reported the Urmia executions of Omid Behzad and Pouria Safvat, the only source to do so, consistent with its documented pattern of recording far more executions than the Iranian state acknowledges. Iran's government has not confirmed either execution.
Shipping and insurance underwriters
Shipping and insurance underwriters
War-risk premiums price the Houthi campaign because the group announces its targets in advance, but a reopening Trump has promised without a published text gives underwriters no benchmark to reprice Hormuz cover against. Insurers want a text before they move rates, not a promise.
Houthi movement
Houthi movement
Spokesman Yahya Saree claimed strikes on two tankers in the Red Sea and Gulf of Aden on 5 August, only one of which UKMTO could confirm. The group's campaign against shipping continues on its own schedule, independent of any Hormuz arrangement further north.
Oman
Oman
Muscat has brokered the coordinates both Tehran and Washington's wire sources now describe differently, but has published no account of its own. Oman's position depends on treating Hormuz as a shared route, which is not what Iran is currently describing.
United States Central Command
United States Central Command
CENTCOM raised its interdiction tally from 35 to 44 redirected vessels and disclosed its first boardings on 3 August, the day before Trump promised a reopening. The command's own enforcement record does not yet reflect the release the President has described.
Iran's Foreign Ministry
Iran's Foreign Ministry
Spokesman Esmaeil Baghaei described the agreed Hormuz coordinates as a wholly new corridor under Iranian management, not a split of the existing route, days after his own deputy rejected Oman's lane proposal. Tehran wants the arrangement read as a change of ownership, not a compromise on access.