A vessel transiting the Strait of Hormuz was struck by a suspected projectile Sunday evening and the fire it caused was extinguished — yet the incident did not surface publicly until Monday, when UK Maritime Trade Operations issued a "time-late" third-party report. The delay is the latest evidence that the public record of attacks in the strait no longer captures the full scope of the fighting.

UKMTO classified Warning 143-26 as "suspicious activity" rather than an attack, despite stating the vessel was struck. The ship remained underway and its crew was safe.

The warning followed Iran's weekend claim that its forces had targeted or intercepted 19 vessels operating outside Tehran-designated routes through Hormuz — 12 on Friday and seven on Saturday. Iran has named no ships and produced no evidence. The new UKMTO report confirms at least one vessel was hit during that window, and only after the fact.

That does not validate Tehran's number. But it exposes a structural problem for shipowners, insurers and analysts: the incident log is incomplete, and decisions on crewing, routing and war-risk premiums are being made against a partial picture.

A voluntary system with built-in lag

UKMTO remains one of the industry's most important maritime security sources, but its Voluntary Reporting Scheme depends on ships registering voyages, filing daily position reports and reporting incidents themselves. UKMTO warns that non-participating vessels may delay military assistance because authorities may not know they are there.

The lag is measurable. A Sept. 16 attack was not publicly reported until Sept. 18, described by UKMTO as a "verified, time-late report." Other September incidents — including one involving an LPG tanker and another vessel strike reported Sept. 15 — also emerged after the fact.

Individual operators often hold a broader picture than the alerts suggest. In August, ADNOC said 15 of its vessels had been targeted by missiles or drones since the conflict began, leaving one crew member dead and 20 injured. Because UKMTO warnings frequently omit vessel identities, reconciling company totals with the public incident list is difficult.

Analyst Brett Erickson, who has tracked the attacks, argues additional recent strikes may still be missing from public reporting and suggested the latest incident may only have surfaced after detection through satellite imagery. UKMTO has not said what prompted the third-party report, and that theory is unconfirmed.

The Joint Maritime Information Center adds a layer, combining open-source data with military and maritime stakeholder input and aiming, in its own words, at "ground truth." But JMIC too depends on incidents becoming known in the first place. During Somali piracy and the Houthi campaign in the Red Sea and Gulf of Aden, UKMTO and JMIC reporting gave the industry a dependable reference point. Hormuz is proving harder to count.

Transits going dark

The same verification gap now applies to traffic itself. AIS has long been the backbone of commercial ship tracking, but growing numbers of vessels are crossing Hormuz without publicly visible transponder signals. Reuters reported last week that some ships operating without active tracking are absent from public transit counts. Kpler and vessel-tracking data put average traffic at roughly 18 vessels per day, against around 125 large commercial vessels per day before the conflict.

That gap matters most when assessing Project Freedom, the U.S.-coordinated effort to keep commercial shipping moving. U.S. Central Command began supporting the operation May 4 with destroyers, more than 100 aircraft, unmanned systems and roughly 15,000 personnel. CENTCOM commander Adm. Brad Cooper said the United States had "assumed the risk" of opening a commercial passage through the strait.

Much of that operation runs outside public view. A vessel coordinating directly with U.S. forces can transit without appearing on public AIS services, which helps explain why U.S. estimates often exceed visible traffic.

Treasury Secretary Scott Bessent said Sunday that Hormuz was already open, with flows averaging 15 million to 22 million barrels per day versus around 20 million before the conflict, and more than 1 billion barrels moved out of the region while Iranian oil exports were halted.

Independent trackers show substantial movement, but lower. TankerTrackers.com estimated in early September that crude exports across the U.S. blockade line had averaged 7.54 million barrels per day over the prior 28 days — about 5.04 million barrels per day through Hormuz and 2.49 million from Gulf of Oman terminals. More recent Kpler data reported by Reuters puts preliminary September Middle East crude exports above 16 million barrels per day, with roughly 9.7 million barrels per day through Hormuz, explicitly excluding vessels that may have crossed with AIS switched off.

The figures are not directly comparable — different periods, different petroleum streams, and government data may include vessels invisible to commercial trackers. That is precisely the problem: no single dataset now reliably answers how many ships pass Hormuz, how much oil they carry, or how many are attacked en route.

Iran's claim of 19 vessels targeted remains unverified, and the absence of matching UKMTO attack reports weighs against treating it as confirmed. But Monday's time-late warning shows the public incident list cannot be treated as a census either — a distinction that will shape risk pricing and routing decisions for as long as the fog over Hormuz persists.