What explains Goldman Sachs' Hormuz traffic volume forecast error — and what does it imply for price reliability?

Question

Goldman Sachs predicted Hormuz traffic would reach 120% of normal by May 2026. Traffic has not returned to normal. What does this forecast error reveal about Goldman Sachs' reliability as an information source in this crisis — and does it undermine their price forecasts?

What We Have

The Goldman Sachs Traffic Prediction

As documented in the contradictions log (May 7, 2026 entry), Goldman Sachs predicted that Hormuz vessel traffic would reach 120% of normal by May 2026 — implying an above-baseline rebound that would signal normalization of the Strait. This was cited via a Goldman research slide in a May 7, 2026 tweet (@sam_d_1995).

Reality: Traffic Remains Severely Disrupted

The actual situation as of May 2026, per IEA April 2026 data, is that export losses exceed 13 mb/d — double OIES's maximum pre-conflict modeled scenario. Per WTO/HormuzStraitMonitor live tracking:

  • Transit collapsed from ~130 ships/day to ~6 ships/day (a ~95% drop)
  • By April 17, Iran declared Hormuz "open" and Brent crashed 9% — but physical crude stayed at ~$150
  • By April 19, ceasefire collapsed and the Strait closed again
  • By April 28, Europe Middle East jet fuel imports had stopped entirely
  • As of early May, tanker movement remains severely depressed; Kpler Matt Smith described the physical market as "very laborious" even with reopening signals

The 120% of normal prediction was directionally wrong — not merely a timing miss.

Goldman's Prior Forecasting Errors

Goldman Sachs has now made two categories of error in this crisis:

  1. Pre-war baseline price error: Predicted ~$56/b pre-crisis (wildly too low; the $56 figure was from their pre-conflict 2026 outlook, before the conflict began)
  2. Traffic rebound error: Predicted 120% of normal traffic by May 2026 (directionally wrong; disruption persists)

Both errors were in the same direction — underestimating disruption severity.

The contradictions log () now flags Goldman Sachs' reliability score for Hormuz-flow predictions as downgraded.

What's Missing

  • Goldman's specific research note on the traffic forecast — the KB does not yet have a dedicated article on the Goldman Sachs traffic prediction (only the contradiction log entry). The original Goldman research slide or note needs to be sourced and its methodology examined.
  • Historical accuracy of Goldman energy forecasts — whether this pattern of underestimating geopolitical disruption is consistent with Goldman's track record, or specific to this event.
  • Which other institutions' traffic or flow predictions were more accurate? Vitol Hardy and TankerTrackers have provided real-time AIS-based data. Did any institution predict persistent disruption correctly?
  • Implication for price forecasts: Goldman also trimmed their Q2 Brent forecast from $110 → $90 post-ceasefire (April 9). Given their traffic error, does the $90 target carry lower credibility?

What's Contested

  • Whether the Goldman traffic error reflects a systematic methodology flaw or a data timing issue. The traffic prediction may have been based on a model assuming rapid political resolution, which the KB already knows was a shared assumption among many institutions (EIA, Goldman, OIES).
  • Whether institutional credibility scores should be tracked in the KB. The contradictions log has flagged this but there is no formal mechanism for tracking which sources are reliable vs. systematically wrong.

Proposed Research Path

  1. Source the original Goldman Sachs research note or slide predicting 120% of normal Hormuz traffic — tweet (@sam_d_1995, May 7, 2026) is the current citation; find the primary Goldman research document.
  2. Compare Goldman's traffic forecast against Vitol Hardy (FT Summit, May 2026: 1B barrels baked-in, 600-700M already lost April 29) and TankerTrackers/AIS-based data to assess relative accuracy.
  3. Assess whether Goldman's $90/b post-ceasefire trim (April 9) should be treated with lower confidence given the traffic volume error.
  4. Consider whether a formal goldman-sachs-hormuz-traffic-forecast-error article should be created in the KB to document this pattern explicitly.