Hormuz Attack Counts Are a Floor: US Navy Go-Dark Guidance

The official tally of attacks on shipping in the Strait of Hormuz is incomplete, and the body that compiles it says so. In its weekly overview on 16 October 2026, the UK Maritime Trade Operations centre (UKMTO) said it was struggling to establish the true number of attacks because the majority of vessels targeted were refusing to report to it. It recorded 12 attacks that week, ten of them inside the Strait, with one vessel lost. It added that it knew of further incidents through other sources but could not include them without verification.

For oil traders, that matters more than any single weekly figure. Freight rates, war-risk premiums and assessments of supply risk all lean on these counts. If most attacked ships are staying silent, the published number is a minimum, not a measure.

Context — why Hormuz attack counts matter more than any single week

UKMTO's own admission is the comparable that matters. The centre recorded 12 attacks in the week to 16 October, ten inside the Strait, and one vessel lost, then said it could not verify further incidents it knew about through other sources. That gap between what it logged and what it knew is the story.

Shipowners have commercial reasons to stay quiet. The report lists insurance complications, exposure with a vessel's flag state and sensitivity about routing. Each of those is a reason to absorb a hit quietly rather than file a report that raises premiums or invites questions.

A less noticed document may be part of the picture. A US Navy FAQ for shipping companies, highlighted in a post on X by the account @angertab, sets out how the Navy supports transits on the southern route through the Strait. It was issued by the Naval Cooperation and Guidance for Shipping (NCAGS) cell at US Naval Forces Central Command (NAVCENT), the unit that liaises with merchant ships. Copies are posted on the website of the Liberian ship registry and on that of a Turkish shipowners' and agents' association.

The macro backdrop is a war that began on 28 February, a blockade Iran reimposed in mid-July, and October producing the highest attack totals since the conflict started. Shipping risk is being repriced inside a corridor the US presents as the safer option.

Data — what the US Navy FAQ does and does not provide

The FAQ draws a hard line between what the US provides and what it does not. It offers airborne overwatch, intelligence and surveillance, threat response, plus recommended waypoints and transit windows. It does not provide escorts: no US or partner vessels accompany the ships, and no personnel board them.

What ships are asked to do is the operative part. They are told to turn AIS tracking off, keep radar on standby and stay silent on VHF radio, because emissions could be used for targeting. Asked whether the US would give operational security guidance covering crew phones, social media and reporting restrictions, the Navy says best practices will be recommended. It does not say what they are. After the transit, the FAQ says no post-transit debrief is required.

Item	Before mid-July	After mid-July
Attacks logged by UKMTO (latest week)	12, ten inside the Strait	12, ten inside the Strait
Route most projectile strikes hit	Not specified	Southern route, the US-facilitated corridor
Vessel losses in latest week	One	One

A reassurance in the FAQ has aged badly. It says more than 200 transits had been completed with fewer than five successful attacks and no loss of life or vessels. According to the post, the file's metadata dates it to 14 June, which is before Iran reimposed its blockade in mid-July. Reported UKMTO data shows most projectile strikes since early July have hit the southern route, the corridor the US facilitates.

Analysis — where the undercount shows up in pricing

The combination in the FAQ is the point. A ship told to go dark during the transit, and not asked to report afterwards, has little procedural push to file an incident report with UKMTO. The document does not tell ships to stop reporting attacks. The reporting restrictions reference sits in a question about phones and social media, and could simply mean not broadcasting positions online. The FAQ explains how silence could become the default. It does not prove that silence is policy.

The exposure runs through freight and insurance first. War-risk premiums and terms for southern-route transits are the prices that would move if underwriters were marking the undercount. The report flags those as the signal to watch, and it also flags a gap between AIS-visible traffic and US-stated transit figures, which already diverge because facilitated ships run dark.

The counter-argument is straightforward. Nothing in the FAQ instructs vessels to withhold attack reports, and the reporting restriction language is ambiguous enough to cover social media alone. A silent ship may simply be a cautious one, not a suppressed data point. UKMTO's own note that it cannot verify outside incidents cuts both ways: the number is a floor, but the size of the gap is unknown.

Positioning follows the ambiguity. Anyone underwriting Gulf supply risk is leaning on a count that the compiler calls incomplete, while the direction of October's totals runs against the corridor the US markets as safer. The report notes the post says the file's metadata points to an allied, non-US naval connection, suggesting the guidance passed through partner hands; that shows who handled the file, not who wrote it.

Outlook — what to watch on Hormuz shipping risk

UKMTO's next weekly overview is the first checkpoint. Watch whether the share of unreported attacks grows, and whether the centre breaks incidents down by route. A route split would show whether the southern corridor is absorbing the strikes the FAQ's June figures predate.

NAVCENT or NCAGS guidance is the second. Any clarification of what reporting restrictions covers, or any updated guidance replacing the June figures, would settle whether silence is procedural or incidental.

Insurance signals are the third. War-risk premiums and any change to terms for southern-route transits would show whether underwriters are pricing in the undercount. Tracked transits are the fourth: gaps between AIS-visible traffic and US-stated transit figures, which already diverge because facilitated ships run dark.

Frequently Asked Questions

What does the Hormuz attack undercount mean for retail investors?

It means any headline figure on Gulf shipping risk is a lower bound. UKMTO logged 12 attacks in the week to 16 October but said most targeted vessels refused to report, so the true count is higher and unmeasured. For retail investors holding energy or shipping exposure, the direction of the numbers is more informative than the level, because the level is known to be incomplete.

Why would a ship attacked in the Strait of Hormuz not report it?

Commercial reasons dominate. The report lists insurance complications, exposure with a vessel's flag state and sensitivity about routing. The US Navy FAQ adds a procedural angle: ships are asked to turn AIS off, stay silent on VHF and keep radar on standby, and no post-transit debrief is required. A vessel told to go dark and not asked to report afterwards has little push to file.

What happens next for southern-route transits through Hormuz?

Watch UKMTO's next weekly overview for a route breakdown, and NAVCENT or NCAGS for clarification of what reporting restrictions covers. Insurance signals matter most: any change to war-risk premiums or terms for southern-route transits would show whether underwriters are pricing the undercount. Tracked transits already diverge from US-stated figures because facilitated ships run dark.

Bottom Line

Treat weekly Hormuz attack counts as a floor, and watch the direction, not the level.

Disclaimer: This article is for informational purposes only and does not constitute investment advice. CFD trading carries high risk of capital loss.