Ports

A port is where freight trains meet the maritime network — the node at each end of a corridor where containers arrive by sea and leave by rail. Gauge Intelligence tracks these ports because port-level throughput, rail modal share, and terminal reliability determine whether traffic stays on rail or shifts to road. Port performance is also where Schedule 8 delay costs concentrate, particularly at capacity-constrained facilities.

Each port has a living reference page that updates at every period close.

Performance summary — Period 2 2026-27

Destination-attributed A2F — services counted by arrival TIPLOC across every inbound corridor traversal. Computed nationally across all inbound corridor traversals for each port. For corridor-stratified figures and Simpson's-paradox handling, see the league-table methodology.

Inbound journeys and A2F are computed live from Network Rail TRUST arrivals at the port’s terminal TIPLOCs across Period 2 2026-27. Cancellations are excluded from the A2F denominator. The 12-week trailing mean is unavailable for every port at this stage: the TRUST data window only extends back to 23 February 2026 (Period 12 2025-26), and no port carries a defensible trailing sample yet. Trailing means backfill once enough prior periods accumulate. Onward corridors is editorial — the count of corridors a port anchors as origin or terminus (not the count of corridors its traffic transits) — and backfills as each port’s archive page publishes.

Coverage

The published archive covers sixteen UK rail-connected ports as at the industry review edition of 2 June 2026. Each entity page carries identity, corridor footprint, and links to period reports where available. Period reports backfill as each port accumulates sufficient closed periods of clean TRUST data. For methodology, see league-table methodology.