Port of Immingham — Period 1 2026-27 (29 March – 25 April) report
Port of Immingham received 307 monitored inbound services in Period 1 2026-27 — 86% arrived within 15 minutes of schedule across 242 completed arrivals, against a national freight benchmark of 89%. The cancellation rate of 21% is an improvement on Period 13 2025-26's 32%, though it remains elevated. Reliability among completed services held at 86%.
- Edition
- v1.0 (industry review edition)
- Last updated
- 25 April 2026
- Next update
- Period 2 2026-27 — final on 24 May 2026
Headline facts and figures
Services monitored
307
11 a day across the eight Immingham terminal TIPLOCs (IMNGCIT, IMNGHIT, IMNGHOT, IMNGSS, IMNGBIO, IMNGHOR, IMNGLCR, IMNGNOR); Period 1 2026-27 (29 Mar – 25 Apr 2026); NROD-derived arrivals data; baseline 579 services in Period 13 2025-26; queried gauge_intelligence_v2 at 2026-05-28
Within 15 minutes
86%
242 completed services arriving within 15 minutes of schedule (Wilson 90% interval 82%–90%); baseline 86% [83%–89%] over 391 completed services in Period 13 2025-26 — in line; national freight benchmark 89% over 14,267 completed services in Period 1 2026-27; queried gauge_intelligence_v2 at 2026-05-28
Cancellation rate
21%
65 cancellations across 307 scheduled paths; down from 32% (188 of 579) in Period 13 2025-26 — an 11 percentage-point improvement, though the rate remains elevated; queried gauge_intelligence_v2 at 2026-05-28
Busiest operator
DB Cargo UK
236 of 242 completed arrivals (98%); aggregated by operator from TRUST toc_id; Period 1 2026-27; Immingham traffic continues to be dominated by DB Cargo UK bulk commodity flows; queried gauge_intelligence_v2 at 2026-05-28
Context
ORR publishes aggregates only; this page publishes destination-attributed port-level data. Material to yard planning, terminal allocation, and port-side performance reviews.
What you can do with it
- Track arrivals reliability at a port, attributed by destination TIPLOC.
- Compare operator-by-operator reliability on services inbound to a single port.
- Cite the methodology in port operations and corridor reviews.
Who can use it
Port operations leaders · Terminal allocators · Rail journalists
Across Period 1 2026-27, roughly 1 inbound train a day arrived at Port of Immingham more than 15 minutes late, about 1 in 8 of 225 completed arrivals over the 28-day period, 30 late arrivals in total. Monitored services fell from 579 to 225, consistent with the post-Easter freight calendar. The cancellation rate improved from 32% to 21% on the period, though it remains elevated against national norms. Figures aggregate every monitored journey arriving at the eight Immingham terminal TIPLOCs (serving the Humber estuary complex across coal, steel, biomass and container traffic), drawn from Network Rail's NROD/TRUST feed. Cancellations are reported separately below.
Operators at Immingham-inbound
DB Cargo UK ran the most immingham-inbound services in Period 1 2026-27 (219 of 225 completed arrivals). The full per-operator reliability comparison is deferred while the v1.0 industry review edition corrections inbox remains open.
Publishing a per-operator on-time comparison for the busiest freight operators at a single destination before the launch-cohort corrections cycle closes would treat provisional attribution as settled. The table returns at v2.0 general availability. The league-table methodology documents the comparison framework; the release cadence page sets out the four exit criteria for v2.0.
Source: Gauge Intelligence NROD-derived journey data, Period 1 2026-27. Single-destination headline figures (completed arrivals, aggregate within-15-minute rate, cancellations) continue to appear in the panels above; the per-operator breakdown is the panel deferred here.
Outbound destinations — services leaving Port of Immingham
Scunthorpe Steelworks took 51 of 168 outbound services (30%) in Period 1 2026-27 — the largest outbound destination from Port of Immingham, arriving within 15 minutes on 84% of trips.
| Inland terminal | Outbound services | Share | Within 15 minutes |
|---|---|---|---|
| Scunthorpe Steelworks | 51 | 30% | 84% (74–91%) |
| Drax Power Station | 40 | 24% | 98% (90–99%) |
| Birch Coppice (BIFT) | 9 | 5% | 78% (50–92%) |
| Doncaster Yard | 2 | 1% | — |
Source: Gauge Intelligence NROD-derived journey data, Period 1 2026-27. Total outbound services count every journey originating at any Port of Immingham terminal TIPLOC, including services to destinations not yet named in the inland-terminal registry; rows are restricted to registered inland-terminal destinations, so the share column shows each terminal’s slice of total outbound traffic and the row counts will not sum to the total. Destinations with a published archive page link to that page; destinations named in the registry but not yet published render as plain text. The bracketed range on each within-15-minutes figure is the 90% confidence range given the sample size; terminals with fewer than 5 services in the period show a dash. Cancellations are excluded. Lens: supply-chain (port-origin destination-attributed) — see league-table methodology.
What the 15-minute threshold hides
Half of Period 1 2026-27 services arrived early — the median was 7 min ahead of timetable. The long tail the A2F binary misses: 5% of services ran +38 min or more late, and 1% arrived over +99 min late. The 15-minute A2F threshold sits at the 88th percentile — 12% of services exceeded it.
Median arrival delay is essentially unchanged on Period 13 2025-26 (-7 min then, -7 min now).
| Percentile | Arrival delay |
|---|---|
| 50th percentile (median) — A2F threshold sits at the 88th percentile | -7 min |
| 75th percentile — A2F threshold sits at the 88th percentile | +3 min |
| 85th percentile — A2F threshold sits at the 88th percentile | +9 min |
| 90th percentile | +20 min |
| 95th percentile | +38 min |
| 99th percentile | +99 min |
225 services with confirmed terminal arrival in Period 1 2026-27. A2F is binary at 15 minutes — this distribution surfaces what the headline figure does not show. National 99th percentile across all freight operators: 100 min.
Baseline (Period 13 2025-26): median -7 min, p99 +90 min. Period-on-period median shift +0 min.
ORR's Freight rail usage and performance release publishes by Network Rail region and route, not by operator. This page publishes by operator and corridor.
Daily on-time arrivals across Period 1 2026-27
Daily on-time arrivals are down 1.2 percentage points on Period 13 2025-26 (88% then, 87% now).
Range 57%–100% across 28 days. Weekend mean 88% vs weekday 86% (+2.0 percentage points). Mean 87%.
Period 1 2026-27 daily A2F averaged 96% across 28 observations. One or more observations fell outside the expected range (8 day(s) beyond the expected range; 5 run(s) of two-of-three days off-mean), indicating an unusual event rather than ordinary noise.
Mean punctuality in Period 13 2025-26 was 88%. The current period is down 1.2 percentage points on Period 13 2025-26.
Source: Gauge Intelligence NROD-derived journey data, Period 1 2026-27. A service is counted on time when terminal arrival falls within 15 minutes of schedule. Days with no scheduled services (typically Sundays) render as gaps — a missing bar means no measurement, not a value at zero. Red bars flag days that triggered a statistical signal — see anomaly-detection methodology.
ORR's Freight rail usage and performance release publishes by Network Rail region and route, not by operator. This page publishes by operator and corridor.
Cancellation rate
In Period 1 2026-27, 24% of scheduled services were cancelled (75 of 309) — 17.0pp above the national mean of 7% across all freight operators; FOC traction, crew, and terminal decisions accounted for the largest share.
Cancellations are down 12.50 percentage points on Period 13 2025-26 (37% then, 24% now). The largest shifts in the responsible-party split are reported in the table below.
| Scheduled or activated paths | 309 |
| Cancelled (post-activation + pre-activation) | 75 |
| Cancellation rate | 24% 21%–29% |
| National cancellation rate (all freight) | 7% |
Attribution
| Responsible party | Cancellations | Share of cancelled |
|---|---|---|
| Network Rail infrastructure and possessions | 21 | 28% |
| FOC traction, crew, and terminal decisions | 35 | 47% |
| Third party | 1 | 1% |
| Unattributed | 18 | 24% |
Cancellation rate in Period 13 2025-26 was 37% across 582 scheduled paths. The current period is down 12.50 percentage points on Period 13 2025-26.
Source: NROD/TRUST activation feed and BPLAN scheduled paths, Period 1 2026-27. Cancellation rate = (post-activation + pre-activation cancellations) ÷ scheduled or activated paths. Pre-activation cancellations are TRUST CANCEL messages on schedules that never activated; post-activation cancellations have an activation and a CANCEL event. The bracketed range beside the headline rate is the 90% confidence range on the cancellation proportion given the sample size. Cause attribution uses the responsible-party mapping of the recorded cancellation reason code; see delay-attribution methodology.
What this page does not measure
Pre-activation cancellations fall outside the dataset: TRUST requires an activation event before it records a journey, so services cancelled before activation produce no TRUST record. VSTPs are excluded from the path-utilisation denominator because no Working Timetable row exists against which to measure them. Journeys without a confirmed terminal arrival are excluded from the delay distribution. The 15-minute A2F threshold is a regulatory artefact, not a natural cut-off — the "What the 15-minute threshold hides" panel surfaces the distribution behind that line.
Commercial licence
Four derivations are released to commercial-licence subscribers rather than the public archive. Each one reconciles TRUST source-data against Network Rail's Historic Delay Attribution record independently, not republished from public statistics.
- Schedule 8 net position
- Why late — delay attribution
- Schedule 4 possession exposure
- Path utilisation — corridor breakdown
Available under commercial licence. Contact [email protected] for subscription terms.
Methodology & sources
All figures derive from Network Rail's NROD TRUST feed, processed via the Gauge Intelligence ingest pipeline. Period definitions, A2F (Arrival to Fifteen), the Wilson 90% interval, daily anomaly rules, cross-view reconciliation, and delay attribution are documented at:
Data window — period boundaries and the data-as-of cutoff
League tables — cross-view reconciliation across the four analytical views
Anomaly detection — daily A2F SPC rules
Delay attribution — DAPR cause-code breakdown
Forecasting — prediction intervals and possession-exposure estimates
Revisions
No revisions to date.
A revision restates a published figure because the upstream data changed, typically a Network Rail delay-attribution refresh. The minor tier is corrected in the next release; cells affected carry an (r) flag. The intermediate tier triggers immediate amendment with an (r) flag. The wholesale tier is flagged at the top of the page and notified directly to operators and rail journalists subscribed to revision alerts.
Corrections
No corrections to date.
A correction fixes an error in the published output: an arithmetic slip, a typo, a mis-rendered chart. Revisions are different; they restate a figure because the upstream data changed. The distinction matters because corrections never silently rewrite a published number.