Finance entity
Every one of those 1 sits in a single category, markets. Transpacific routes is most often covered alongside Drewry, which appears in 1 of these 1 story. Each story carries 2 original sources on average, compared with 2.7 for the broader beat in this window.
Last mentioned: Mar 19, 2026
Entity pulse
Figures are computed live from our source-verified story record — see our methodology for how impact and sentiment are derived.
Every one of those 1 sits in a single category, markets. Transpacific routes is most often covered alongside Drewry, which appears in 1 of these 1 story. Each story carries 2 original sources on average, compared with 2.7 for the broader beat in this window. At 6, the average consequence score sits below the same-window beat average of 6.4. Transpacific routes appears in 1 tracked Finance story from March 19, 2026.
Computed from the 1 stories linked to this entity, with beat comparisons drawn from all 105 Finance stories published in the same date window. Shares are omitted below five stories and comparisons below a twenty-story baseline.
Coverage cohort
Other entities that clear the same relevance threshold in stories also covering Transpacific routes. Shared-story counts are live from our verified record — not editorial picks.
Hormuz Crisis Escalation
WCI hits $2,172 as geopolitical risks in the Middle East add cost surcharges to major routes.
Second Weekly Gain
Transpacific demand begins to pull the Drewry WCI higher as shippers front-load cargo.
Rate Stabilization
Global spot rates begin to firm after a period of post-holiday softening.
The Drewry World Container Index rose 2% to $2,172 this week, marking a third consecutive period of growth. Gains are being driven by robust Transpacific demand and escalating geopolitical risks in the Strait of Hormuz, which are pushing maritime costs higher.
Transpacific routes is linked from 1 story on this site, each scored at or above our 35% relevance threshold — see how these pages are built.
See something wrong on this page — a misattributed entity, a wrong stat, a broken source link? Report a data issue.
