Skip to content
You can now search across every topic, entity and event.What's new
European Oil Markets
31JUL

Trump's fifth Hormuz deadline expires tonight

2 min read
09:33UTC

The fifth reformulation of the same Hormuz ultimatum in six weeks is set to lapse at 8pm Eastern, with the most probable outcome a sixth extension framed around the Islamabad track.

EconomicDeveloping
Key takeaway

Five extensions in, the deadline mechanism has become the instrument rather than a precursor to action.

Donald Trump's fifth Hormuz ultimatum expires at 8pm ET (0000 UTC Wednesday). It follows the 6 April power-grid deadline and the second replacement that itself ran out , and reformulates the same threat for the fifth time in six weeks .

Each previous expiry produced an extension. The rhetoric escalated each cycle while the operational ceiling stayed flat: no civilian-infrastructure threshold ever crossed, no new target category announced, no military fact on the ground that the prior subsequents had not already established. The most probable outcome tonight, on the pattern, is a sixth extension framed around whatever the Islamabad track allows.

Tehran is now planning around the assumption that the deadline itself is the instrument, not a precursor to action. The risk is not that one of these expiries is theatre, it is that the day Trump genuinely intends to follow through, no actor in the system will read the signal differently from the four that preceded it.

Deep Analysis

In plain English

Trump has now issued five versions of the same ultimatum over six weeks: open Hormuz or face consequences. Each previous deadline has produced an extension rather than action , the 6 April power-grid deadline, the second replacement, and three further reformulations. Tonight's version expires at 8pm Eastern time. The most likely outcome, on pattern, is a sixth extension framed around whatever the Pakistan diplomatic track allows. The practical effect of five extensions is that Iran now plans on the assumption the deadline itself is the tool, not a warning of what follows. The danger is not that each expiry is theatre , it may well be , but that the day it is not, no one reads it differently.

Deep Analysis
Root Causes

The five-extension pattern reflects a structural mismatch between Trump's political need to signal toughness on Hormuz domestically and the operational reality that the US has not found a military solution within the constraints it has set for itself , no civilian infrastructure thresholds crossed, no new target categories announced, carriers moved out rather than in.

Each extension preserves the option while deferring the cost; the cumulative cost is the credibility of the next deadline.

Escalation

The fifth deadline expiry does not itself raise escalation risk; the pattern has lowered it by training both sides to treat expiry as routine. The risk is asymmetric: on the day the US genuinely intends to follow through, the signal will be indistinguishable from the four that preceded it, creating a window for catastrophic Iranian miscalculation.

What could happen next?
  • Risk

    Five consecutive extensions have habituated Iran to treating US deadlines as negotiating variables; if Trump does eventually order enforcement action, the prior pattern means the signal will not be read as materially different, raising the risk of a genuine miscalculation.

  • Precedent

    The five-extension cycle establishes that this administration will not cross civilian-infrastructure thresholds under deadline pressure alone, narrowing Iran's incentive to offer substantive concessions before a threshold is actually crossed.

First Reported In

Update #61 · Carriers retreat; Iran codifies Hormuz

US Energy Information Administration· 7 Apr 2026
Read original
Different Perspectives
Sanctions compliance officer reviewing a Lukoil International GmbH bid
Sanctions compliance officer reviewing a Lukoil International GmbH bid
OFAC's amended FAQ 1224 gives a compliance desk its first published standard: full severance from Lukoil and a US-jurisdiction blocked account for sale proceeds. The conditions name neither ISAB nor Italy, so a Priolo Gargallo-linked bid answers a different question than a Neftochim Burgas or Petrotel Ploiesti one.
Managed-money funds on Brent Last Day
Managed-money funds on Brent Last Day
CFTC data for the week to 21 July showed managed money flipping 74,400 contracts to a net long of 15,665 against 1,410 short on the Brent Last Day contract, code 06765T. A fund that held that short through July has now covered it, and the spent short base raises the bar for the next leg higher.
Saudi crude exporters
Saudi crude exporters
Saudi-linked tanker transits through Bab el-Mandeb fell to about 7.5 a day after the 24 July underwriting withdrawal, pushing more barrels onto the longer route round the Cape or through the Yanbu terminal. Every diverted barrel ties up a ship for longer, and a fleet that turns slower charges more.
Tanker owners on the Bab el-Mandeb route
Tanker owners on the Bab el-Mandeb route
Lloyd's-market syndicates withdrew war-risk cover from Saudi-linked hulls on 24 July, leaving owners of that class of vessel to sail Bab el-Mandeb uninsured or not at all. Tanker transits on the route fell to roughly 7.5 a day, and cover, once withdrawn, does not return on a shipowner's timetable.
Eni
Eni
Eni's board approved second-quarter results on 29 July, swinging refining EBIT to a EUR0.08bn profit from a year-earlier loss even as group profit doubled, and named Red Sea freight cost as a cap on that improvement. A refiner absorbing higher shipping costs on Saudi-linked crude while its numbers improve treats the freight line as a drag, not a crisis.
Asian buyers (India, Japan, China, South Korea)
Asian buyers (India, Japan, China, South Korea)
Asian refiners are absorbing 62% of Yanbu's 3.75m b/d flow, the bulk of Saudi Arabia's rerouted crude now clearing east rather than into the Atlantic basin. That destination split leaves Asian buyers more exposed to any single Yanbu-specific disruption than under the kingdom's normal multi-terminal export pattern.