Scunthorpe Steelworks — Period 13 2025-26 (1–28 March) report
Scunthorpe Steelworks handled 197 monitored inbound services and 224 monitored outbound services in Period 13 2025-26. Inbound arrivals read 91% within 15 minutes of schedule against a national freight benchmark of 90%; outbound services read 90% within 15 minutes. Inaugural per-site supply-chain period report; the Period 12 2025-26 trailing baseline is below the publishable threshold, so no comparison against the prior period is published.
- Edition
- v1.0 (industry review edition)
- Last updated
- 28 March 2026
- Next update
- Period 1 2026-27 — 21 May 2026
Headline facts and figures
Services monitored (inbound)
197
queried gauge_intelligence_v2 at 2026-05-25; across the Scunthorpe cluster tiplocs (SCNTHEC, SCNTANS, SCNTSOT, SCNTTTC); Period 13 2025-26 (1–28 Mar 2026); NROD-derived arrivals data; the Period 12 2025-26 trailing baseline is below the publishable threshold for a defensible comparator
Within 15 minutes (inbound)
91%
queried gauge_intelligence_v2 at 2026-05-25; 179 of 197 completed inbound services arriving within 15 minutes of schedule (range 87–94% given the sample size); national freight benchmark 90% over 16,826 services in Period 13 2025-26
Services monitored (outbound)
224
queried gauge_intelligence_v2 at 2026-05-25; across the Scunthorpe cluster tiplocs (SCNTHEC, SCNTANS, SCNTSOT, SCNTTTC); Period 13 2025-26 (1–28 Mar 2026); NROD-derived departures data; the Period 12 2025-26 trailing baseline is below the publishable threshold for a defensible comparator
Within 15 minutes (outbound)
90%
queried gauge_intelligence_v2 at 2026-05-25; 202 of 224 completed outbound services departing within 15 minutes of schedule (range 86–93% given the sample size); national freight benchmark 90% over 16,826 services in Period 13 2025-26
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 13 2025-26, 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 169 completed inbound arrivals and 199 completed outbound departures over the 28-day period. Scunthorpe is a bidirectional supply-chain site: this report carries inbound and outbound figures as twin panels. Figures aggregate every monitored journey at the Scunthorpe cluster tiplocs in 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.
Inbound — services arriving at Scunthorpe Steelworks
Operators at Scunthorpe inbound
DB Cargo UK ran the most scunthorpe inbound services in Period 13 2025-26 (134 of 169 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.
What the 15-minute threshold hides
Half of Period 13 2025-26 services arrived early — the median was 4 min ahead of timetable. The long tail the A2F binary misses: 5% of services ran +19 min or more late, and 1% arrived over +45 min late. The 15-minute A2F threshold sits at the 92th percentile — 8% of services exceeded it.
| Percentile | Arrival delay |
|---|---|
| 50th percentile (median) — A2F threshold sits at the 92th percentile | -4 min |
| 75th percentile — A2F threshold sits at the 92th percentile | +1 min |
| 85th percentile — A2F threshold sits at the 92th percentile | +5 min |
| 90th percentile — A2F threshold sits at the 92th percentile | +8 min |
| 95th percentile | +19 min |
| 99th percentile | +45 min |
169 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.
Cancellation rate
No scheduled paths or activated journeys recorded for Period 13 2025-26.
Outbound — services departing from Scunthorpe Steelworks
Operators at Scunthorpe outbound
DB Cargo UK ran the most scunthorpe outbound services in Period 13 2025-26 (176 of 199 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.
What the 15-minute threshold hides
Half of Period 13 2025-26 services arrived early — the median was 5 min ahead of timetable. The long tail the A2F binary misses: 5% of services ran +27 min or more late, and 1% arrived over +59 min late. The 15-minute A2F threshold sits at the 91th percentile — 10% of services exceeded it.
| Percentile | Arrival delay |
|---|---|
| 50th percentile (median) — A2F threshold sits at the 91th percentile | -5 min |
| 75th percentile — A2F threshold sits at the 91th percentile | +4 min |
| 85th percentile — A2F threshold sits at the 91th percentile | +8 min |
| 90th percentile — A2F threshold sits at the 91th percentile | +13 min |
| 95th percentile | +27 min |
| 99th percentile | +59 min |
199 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.
Cancellation rate
No scheduled paths or activated journeys recorded for Period 13 2025-26.
What this report doesn't yet carry
Four blocks routinely carried on more mature period reports are absent here, 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 (different operator mixes, different timetabling pressure), 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 13 2025-26; 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 13 2025-26 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.
The 12-week trailing baseline window (7 December 2025 to 28 February 2026) carries fewer than ten monitored journeys per direction — its 90% range spans a band too wide to anchor a defensible change against the prior period, so this report does not quote one. Baseline depth becomes informative once a full quarter of monitoring has cleared, expected from Period 2 2026-27 onward.
Each of the suppressed blocks above unlocks as baseline depth grows. The first follow-up period (Period 1 2026-27, closing 25 April 2026) adds four more weeks of monitored journeys, after which the weekly SPC threshold per direction and the operator-by-week matrix become candidates for inclusion.
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.