Port of Immingham — Period 2 2026-27 (26 April – 23 May) report
Port of Immingham received 251 monitored inbound services in Period 2 2026-27 — 91% of 243 completed arrivals were within 15 minutes of schedule, against a national freight benchmark of 90%. The cancellation rate of 3% represents a marked improvement on Period 1 2026-27's 21% and Period 13 2025-26's 32%. PRELIMINARY at T+2; FINAL re-publication at T+35 after Network Rail's batch correction.
- Edition
- v1.0 (industry review edition)
- Last updated
- 28 May 2026
- Next update
- Period 3 2026-27 — late June 2026
Headline facts and figures
Services monitored
251
9 a day across the eight Immingham terminal TIPLOCs (IMNGCIT, IMNGHIT, IMNGHOT, IMNGSS, IMNGBIO, IMNGHOR, IMNGLCR, IMNGNOR); Period 2 2026-27 (26 Apr – 23 May 2026); NROD-derived arrivals data; baseline 307 services in Period 1 2026-27; queried gauge_intelligence_v2 at 2026-05-28
Within 15 minutes
91%
243 completed services arriving within 15 minutes of schedule (Wilson 90% interval 87%–93%); baseline 86% [82%–90%] over 242 completed services in Period 1 2026-27 — ranges overlap; national freight benchmark 90% over 12,042 completed services in Period 2 2026-27; queried gauge_intelligence_v2 at 2026-05-28
Cancellation rate
3%
8 cancellations across 251 scheduled paths; down from 21% (65 of 307) in Period 1 2026-27 — an 18 percentage-point improvement; queried gauge_intelligence_v2 at 2026-05-28
Busiest operator
DB Cargo UK
238 of 243 completed arrivals (98%); aggregated by operator from TRUST toc_id; Period 2 2026-27; DB Cargo UK continues to dominate Immingham 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 2 2026-27, roughly 1 inbound train a day arrived at Port of Immingham more than 15 minutes late, about 1 in 9 of 220 completed arrivals over the 28-day period, 26 late arrivals in total. The cancellation rate fell sharply to 3% from 21% in Period 1 2026-27 and 32% in Period 13 2025-26 — the completed-arrivals base is substantially more representative this period. 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 2 2026-27 (215 of 220 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 2 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
Drax Power Station took 84 of 173 outbound services (49%) in Period 2 2026-27 — the largest outbound destination from Port of Immingham, arriving within 15 minutes on 85% of trips.
| Inland terminal | Outbound services | Share | Within 15 minutes |
|---|---|---|---|
| Drax Power Station | 84 | 49% | 85% (77–90%) |
| Scunthorpe Steelworks | 37 | 21% | 95% (85–98%) |
| Birch Coppice (BIFT) | 5 | 3% | 20% (5–57%) |
| Earles Sidings (Hope cement works) | 1 | 1% | — |
Source: Gauge Intelligence NROD-derived journey data, Period 2 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 2 2026-27 services arrived early — the median was 5 min ahead of timetable. The long tail the A2F binary misses: 5% of services ran +29 min or more late, and 1% arrived over +93 min late. The 15-minute A2F threshold sits at the 91th percentile — 9% of services exceeded it.
Median arrival delay is 2 minutes later than Period 1 2026-27 (median was -7 min then, -5 min now).
| Percentile | Arrival delay |
|---|---|
| 50th percentile (median) — A2F threshold sits at the 91th percentile | -5 min |
| 75th percentile — A2F threshold sits at the 91th percentile | +1 min |
| 85th percentile — A2F threshold sits at the 91th percentile | +7 min |
| 90th percentile — A2F threshold sits at the 91th percentile | +13 min |
| 95th percentile | +29 min |
| 99th percentile | +93 min |
220 services with confirmed terminal arrival in Period 2 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: 95 min.
Baseline (Period 1 2026-27): median -7 min, p99 +99 min. Period-on-period median shift +2 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 2 2026-27
Daily on-time arrivals are up 1.6 percentage points on Period 1 2026-27 (87% then, 88% now).
Range 0%–100% across 28 days. Weekend mean 92% vs weekday 87% (+4.9 percentage points). Mean 88%.
Period 2 2026-27 daily A2F averaged 98% across 28 observations. One or more observations fell outside the expected range (14 day(s) beyond the expected range; 14 run(s) of two-of-three days off-mean; 1 run(s) of four-of-five days off-mean), indicating an unusual event rather than ordinary noise.
Mean punctuality in Period 1 2026-27 was 87%. The current period is up 1.6 percentage points on Period 1 2026-27.
Source: Gauge Intelligence NROD-derived journey data, Period 2 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 2 2026-27, 11% of scheduled services were cancelled (27 of 254) — 6.6pp above the national mean of 4% across all freight operators; FOC traction, crew, and terminal decisions accounted for the largest share.
Cancellations are down 13.70 percentage points on Period 1 2026-27 (24% then, 11% now). The largest shifts in the responsible-party split are reported in the table below.
| Scheduled or activated paths | 254 |
| Cancelled (post-activation + pre-activation) | 27 |
| Cancellation rate | 11% 8%–14% |
| National cancellation rate (all freight) | 4% |
Attribution
| Responsible party | Cancellations | Share of cancelled |
|---|---|---|
| Network Rail infrastructure and possessions | 2 | 7% |
| FOC traction, crew, and terminal decisions | 25 | 93% |
| Third party | 0 | 0% |
| Unattributed | 0 | 0% |
Cancellation rate in Period 1 2026-27 was 24% across 309 scheduled paths. The current period is down 13.70 percentage points on Period 1 2026-27.
Source: NROD/TRUST activation feed and BPLAN scheduled paths, Period 2 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.