Scunthorpe Steelworks — Period 1 2026-27 (29 March – 25 April) report
Scunthorpe Steelworks handled 116 monitored inbound services and 151 monitored outbound services in Period 1 2026-27. Inbound arrivals read 86% within 15 minutes of schedule against a national freight benchmark of 89%; outbound services read 90% within 15 minutes. The -5 percentage-point move on Period 13 2025-26 inbound sits within plausible sampling variation; the ranges around each reading overlap. Outbound is unchanged against the baseline.
- Edition
- v1.0 (industry review edition)
- Last updated
- 25 April 2026
- Next update
- Period 2 2026-27 — 18 June 2026
Headline facts and figures
Services monitored (inbound)
116
queried gauge_intelligence_v2 at 2026-05-25; across the Scunthorpe cluster tiplocs (SCNTHEC, SCNTANS, SCNTSOT, SCNTTTC); Period 1 2026-27 (29 Mar – 25 Apr 2026); NROD-derived arrivals data; baseline 197 services in Period 13 2025-26
Within 15 minutes (inbound)
86%
queried gauge_intelligence_v2 at 2026-05-25; 100 of 116 completed inbound services arriving within 15 minutes of schedule (range 79–91% given the sample size); baseline 91% [87–94%] over 197 completed services in Period 13 2025-26 — ranges overlap; national freight benchmark 89% over 13,465 services in Period 1 2026-27
Services monitored (outbound)
151
queried gauge_intelligence_v2 at 2026-05-25; across the Scunthorpe cluster tiplocs (SCNTHEC, SCNTANS, SCNTSOT, SCNTTTC); Period 1 2026-27 (29 Mar – 25 Apr 2026); NROD-derived departures data; baseline 224 services in Period 13 2025-26
Within 15 minutes (outbound)
90%
queried gauge_intelligence_v2 at 2026-05-25; 136 of 151 completed outbound services departing within 15 minutes of schedule (range 84–94% given the sample size); baseline 90% [86–93%] over 224 completed services in Period 13 2025-26 — ranges overlap; national freight benchmark 89% over 13,465 services in Period 1 2026-27
Context
ORR publishes aggregates only; this page publishes site-attributed supply-chain data with inbound and outbound directions reported separately. Material to steelworks input logistics, iron-ore scheduling, and corridor performance reviews.
What you can do with it
- Track inbound arrivals and outbound departure reliability at a single supply-chain site.
- Compare operator-by-operator reliability on services to and from the Scunthorpe cluster.
- Cite the methodology in steelworks logistics planning and corridor reviews.
Who can use it
Steel logistics teams · Bulk-flow planners · Rail journalists
Across Period 1 2026-27, roughly inbound trains a day arrived at Scunthorpe Steelworks more than 15 minutes late and roughly outbound trains a day departed more than 15 minutes late, across 106 completed inbound arrivals and 142 completed outbound departures over the 28-day period. Inbound within-15-minutes arrivals read — against 91% in Period 13 2025-26, a -5 percentage-point move; outbound read — against 90%, unchanged. The ranges around each reading overlap, so neither move clears the threshold for a defensible step change on this sample size. Monitored journeys fell from 197 inbound and 224 outbound in the baseline to 106 and 142 respectively, consistent with the post-Easter freight calendar; counting journeys by site does not separate timetable change, traffic mix, or absent operators from underlying demand, and this report does not attribute the movement to a specific cause. Figures aggregate every monitored journey at the Scunthorpe cluster tiplocs in Network Rail's NROD/TRUST feed. Cancellations are reported separately below.
Inbound — services arriving at Scunthorpe Steelworks
Operators at Scunthorpe inbound
DB Cargo UK ran the most scunthorpe inbound services in Period 1 2026-27 (82 of 106 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.
What the 15-minute threshold hides
Half of Period 1 2026-27 services arrived early — the median was 3 min ahead of timetable. The long tail the A2F binary misses: 5% of services ran +28 min or more late, and 1% arrived over +52 min late. The 15-minute A2F threshold sits at the 87th percentile — 13% of services exceeded it.
Median arrival delay is 1 minutes later than Period 13 2025-26 (median was -4 min then, -3 min now).
| Percentile | Arrival delay |
|---|---|
| 50th percentile (median) — A2F threshold sits at the 87th percentile | -3 min |
| 75th percentile — A2F threshold sits at the 87th percentile | +6 min |
| 85th percentile — A2F threshold sits at the 87th percentile | +14 min |
| 90th percentile | +19 min |
| 95th percentile | +28 min |
| 99th percentile | +52 min |
106 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 -4 min, p99 +45 min. Period-on-period median shift +1 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.
Cancellation rate
No scheduled paths or activated journeys recorded for Period 1 2026-27.
Outbound — services departing from Scunthorpe Steelworks
Operators at Scunthorpe outbound
DB Cargo UK ran the most scunthorpe outbound services in Period 1 2026-27 (128 of 142 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.
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 +30 min or more late, and 1% arrived over +49 min late. The 15-minute A2F threshold sits at the 92th percentile — 8% of services exceeded it.
Median arrival delay is 2 minutes earlier than Period 13 2025-26 (median was -5 min then, -7 min now).
| Percentile | Arrival delay |
|---|---|
| 50th percentile (median) — A2F threshold sits at the 92th percentile | -7 min |
| 75th percentile — A2F threshold sits at the 92th percentile | +0 min |
| 85th percentile — A2F threshold sits at the 92th percentile | +6 min |
| 90th percentile — A2F threshold sits at the 92th percentile | +9 min |
| 95th percentile | +30 min |
| 99th percentile | +49 min |
142 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 -5 min, p99 +59 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.
Cancellation rate
No scheduled paths or activated journeys recorded for Period 1 2026-27.
What this report doesn't yet carry
Four blocks routinely carried on more mature period reports remain absent, and the gap is disclosed rather than papered over:
- Partial-pool operator league table. The supply-chain artefact track is not yet wired into the archive renderer — the partial-pool, median-polish, statistical process control (SPC), and compositional log-ratio panels do not yet emit for supply-chain sites. Inbound and outbound flows at a steelworks behave as two distinct populations and the partial-pool shrinkage assumption needs separate calibration for each direction. The block is suppressed pending that calibration.
- SPC process-behaviour chart. Scunthorpe has four weekly A2F (arrivals-to-fifteen-minutes) points per direction in Period 1 2026-27; the signal rules require eight weekly observations before a stability or anomaly claim can be made. The block is suppressed.
- Median-polish operator-by-week matrix. Only two operators (DB Cargo and GB Railfreight) clear the minimum-journeys threshold on a weekly cell at this baseline depth, so the row-by-column matrix degenerates and no decomposition is published.
- Compositional delay-reason breakdown. Network Rail's Historic Delay Attribution (HDA) feed for Period 1 2026-27 has not been imported at the as-of date of this report. Raw percentage-share comparison is misleading when shares are constrained to sum to 100% — an increase in any one cause forces a decrease in another — so the block is suppressed rather than substituted with a naked share. See the delay-attribution methodology.
Each of these unlocks as baseline depth grows. The weekly SPC threshold per direction and the operator-by-week matrix become candidates for inclusion as the trailing window deepens through 2026-27.
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
Three further reads sit behind the commercial licence: a Schedule 8 net-position figure netting the FOC-to-Network-Rail differential against payments the other way; a full Delay Attribution Performance Report breakdown attributing each cause-code's contribution by sample weight; and a Schedule 4 possession-exposure read tracing how planned blockades intersect steelworks-bound path allocation. None is yet substantively informative at Scunthorpe's current baseline depth — the period count that suppresses the SPC chart above leaves each licensed read with too few points to anchor. The licensed access page sets out the methodology behind each.
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.