Port of Immingham — Period 13 2025-26 (1–28 March) report
Port of Immingham received 579 monitored inbound services in Period 13 2025-26 — 86% arrived within 15 minutes of schedule across 391 completed arrivals, against a national freight benchmark of 89%. The cancellation rate of 32% across 579 scheduled paths is high and materially reduces the completed-arrivals base. Inaugural Immingham period report; the Period 12 2025-26 baseline carried fewer services and is below the publishable threshold, so no comparison against a prior period is published.
- Edition
- v1.0 (industry review edition)
- Last updated
- 28 March 2026
- Next update
- Period 1 2026-27 — 28 May 2026
Headline facts and figures
Services monitored
579
21 a day across the eight Immingham terminal TIPLOCs (IMNGCIT, IMNGHIT, IMNGHOT, IMNGSS, IMNGBIO, IMNGHOR, IMNGLCR, IMNGNOR); Period 13 2025-26 (1–28 Mar 2026); NROD-derived arrivals data; Period 12 2025-26 baseline is below the publishable threshold; queried gauge_intelligence_v2 at 2026-05-28
Within 15 minutes
86%
391 completed services arriving within 15 minutes of schedule (Wilson 90% interval 83%–89%); national freight benchmark 89% over 17,665 completed services in Period 13 2025-26; note: the 32% cancellation rate substantially reduces the completed-arrivals base; queried gauge_intelligence_v2 at 2026-05-28
Cancellation rate
32%
188 cancellations across 579 scheduled paths; this is a high cancellation rate — 1 in 3 scheduled services did not run to the terminal; Period 12 2025-26 baseline is below the publishable threshold for a defensible comparator; queried gauge_intelligence_v2 at 2026-05-28
Busiest operator
DB Cargo UK
378 of 391 completed arrivals (97%); aggregated by operator from TRUST toc_id; Period 13 2025-26; Immingham traffic is 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 13 2025-26, roughly 2 inbound trains a day arrived at Port of Immingham more than 15 minutes late — about 1 in 8 of 356 completed arrivals over the 28-day period, 43 late arrivals in total. The cancellation rate of 32% (188 scheduled paths that did not run to the terminal) is the defining feature of this period and substantially reduces the completed-arrivals base. 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. The Period 12 2025-26 trailing window is below the threshold for a stable comparator; subsequent periods will carry the comparison against the prior period. Cancellations are reported separately below.
Operators at Immingham-inbound
DB Cargo UK ran the most immingham-inbound services in Period 13 2025-26 (343 of 356 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 13 2025-26. 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
Drax Power Station took 111 of 323 outbound services (34%) in Period 13 2025-26 — the largest outbound destination from Port of Immingham, arriving within 15 minutes on 96% of trips.
| Inland terminal | Outbound services | Share | Within 15 minutes |
|---|---|---|---|
| Drax Power Station | 111 | 34% | 96% (92–98%) |
| Scunthorpe Steelworks | 81 | 25% | 93% (86–96%) |
| Birch Coppice (BIFT) | 27 | 8% | 85% (71–93%) |
| Earles Sidings (Hope cement works) | 2 | 1% | — |
| Doncaster Yard | 2 | 1% | — |
Source: Gauge Intelligence NROD-derived journey data, Period 13 2025-26. 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 13 2025-26 services arrived early — the median was 7 min ahead of timetable. The long tail the A2F binary misses: 5% of services ran +43 min or more late, and 1% arrived over +90 min late. The 15-minute A2F threshold sits at the 85th percentile — 15% of services exceeded it.
| Percentile | Arrival delay |
|---|---|
| 50th percentile (median) — A2F threshold sits at the 85th percentile | -7 min |
| 75th percentile — A2F threshold sits at the 85th percentile | +3 min |
| 85th percentile — A2F threshold sits at the 85th percentile | +14 min |
| 90th percentile | +21 min |
| 95th percentile | +43 min |
| 99th percentile | +90 min |
356 services with confirmed terminal arrival in Period 13 2025-26. A2F is binary at 15 minutes — this distribution surfaces what the headline figure does not show. National 99th percentile across all freight operators: 98 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 13 2025-26
Range 56%–100% across 28 days. Weekend mean 100% vs weekday 83% (+16.9 percentage points). Mean 88%.
Period 13 2025-26 daily A2F averaged 97% across 28 observations. One or more observations fell outside the expected range (11 day(s) beyond the expected range; 9 run(s) of two-of-three days off-mean), indicating an unusual event rather than ordinary noise.
Source: Gauge Intelligence NROD-derived journey data, Period 13 2025-26. 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 13 2025-26, 37% of scheduled services were cancelled (214 of 582) — 23.3pp above the national mean of 14% across all freight operators; FOC traction, crew, and terminal decisions accounted for the largest share.
| Scheduled or activated paths | 582 |
| Cancelled (post-activation + pre-activation) | 214 |
| Cancellation rate | 37% 34%–40% |
| National cancellation rate (all freight) | 14% |
Attribution
| Responsible party | Cancellations | Share of cancelled |
|---|---|---|
| Network Rail infrastructure and possessions | 44 | 21% |
| FOC traction, crew, and terminal decisions | 139 | 65% |
| Third party | 1 | 1% |
| Unattributed | 30 | 14% |
Source: NROD/TRUST activation feed and BPLAN scheduled paths, Period 13 2025-26. 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.