23JUN

Two tanker claims, one logged blast

2 min read

11:42UTC

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.

← Back to Trump's first Iran paper is an oil licence Jump to analysis ↓

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 ¹. Several wires merged them into a single vessel of disputed name ². 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 ³. 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 ⁴.

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.

Sources:gCaptain·CNN

Mentions:Yahya Saree →Wafaa →Daisy →UKMTO →Yanbu →Gulf of Aden →NCC Masa →Hodeidah →Houthis →Riyadh →Red Sea →United Kingdom →International Maritime Organization →Saudi Arabia →Royal Navy →Al-Shuqaiq →Jazan →

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.

Led to

Houthis claim an oil transport strike

Extends the Houthi campaign against Red Sea shipping tracked since late July.

Occurred 26 Jul 2026

Read story →

Different Perspectives

Turkiye

Erdogan followed the Pakistani delegation to Jeddah for an instrument that has not been signed. Ankara's entry widens Saudi Arabia's defence architecture beyond the existing Pakistan pact, adding a second non-Gulf military partner mid-conflict.

Oman

Muscat is the corridor's broker but has published nothing about the arrangement Fars describes on its behalf. The account leaves Oman administering outbound traffic only, a narrower role than the shared route its mediation has rested on since 1979.

Pakistan

Islamabad sent Sharif, Munir and Dar to Jeddah to widen a defence commitment it has honoured in cheaper registers since March, when Dar invoked the Saudi mutual defence pact. Jeddah tests whether that hedge becomes a binding trilateral instrument with Turkiye.

United States

Washington rejected the Majlis Hormuz bill outright while CENTCOM's own tally kept climbing to 49 vessels redirected since 14 July. Both instruments tightened in the same week Trump promised the strait would reopen soon.

Iran

Iran's foreign ministry is selling a phased Hormuz corridor through Oman and denying any percentage cargo tariff, while its own Majlis is legislating fines to 20% and a bar on Israeli-linked cargo. The two accounts, from the same government, do not agree with each other.

Saudi Arabia

Riyadh published a target forecast, not an attribution, for the campaign it says the Najran strike previewed. That keeps an Article 51 case available while it formalises a trilateral defence architecture with Pakistan and Turkiye.