The facts

  1. Seatrade Maritime placed the incident at 22:12 UTC, about 25 nautical miles northeast of Khasab, Oman. Two devices attached above the waterline detonated, causing an engine-room fire and temporary loss of operation. [1]

  2. Ship & Bunker reported UKMTO's updated account that the tanker continued towards its next port and no environmental impact was reported. This is a reported status, not an independent pollution survey. [2]

  3. UKMTO's public post on 30 October announced warning 187-26, update 001. The original linked full warning could not be retrieved; the incident details here are attributed to the checked shipping reports. [3][1][2]

  4. A separate outbound vessel was reportedly struck by an unknown projectile at 16:00 UTC on 29 October, according to Seatrade's account of UKMTO. That incident is distinct from the later hull-explosives attack. [1]

Still unconfirmed

  • The attackers' identities and responsibility.
  • Official confirmation of the tanker’s identity and the full damage assessment.

Sources

References support the numbered facts above. Source checks: 30 Oct 2026, 06:10 UTC.

Two separately owned shipping publications corroborate the attributed core. UKMTO's public post was read, but its linked full warning was inaccessible. Iranian responsibility, earlier mine claims and a tentative vessel identity are not established here.

  1. Tanker catches fire in Hormuz after explosives attached to hull

    Seatrade Maritime, Marcus Hand · Reporting · 30 Oct 2026

    Informa-owned specialist publication. It reports UKMTO's warning and separately quotes a vessel-identification assessment; that tentative identity and its attribution of responsibility are not adopted here.

  2. Tanker Attacked by Small Boat Off the Coast of Oman: UKMTO

    Ship & Bunker · Reporting · 30 Oct 2026

    Separately owned specialist report. Its incident account shares UKMTO's underlying evidence; it is not a second eyewitness.

  3. UKMTO warning 187-26 update 001

    UKMTO Operations Centre · Primary source · 30 Oct 2026

    Read through X's public unauthenticated embed. It verifies the warning identifier and posting date, not the contents of its inaccessible linked alert.

Report a factual error