Data sources
Last updated 28 Apr 2026
The open data feeds and reference datasets that Gauge Intelligence processes.
All data processed by Gauge Intelligence originates from Network Rail open data feeds or ORR-published reference tables. No proprietary commercial feeds are used. The full processing pipeline is documented at data window methodology.
Quick reference
These feeds power flow-attributed aggregates — combined across operator, corridor, and destination views. See league-table methodology for cross-view reconciliation.
| Source | What it feeds | Last loaded | Period covered |
|---|---|---|---|
| NROD / TRUST feed | All train movement data, punctuality, delay attribution | Live (continuous) | Real-time |
| CIF / Working Timetable | Schedule lookup, planned paths, identity resolution | 1 May 2026 (593,276 records) | Current timetable period |
| BPLAN geography | Corridor point resolution, STANOX→location mapping | 2026-04-24 | Current timetable period |
| STANOX reference | Location name resolution for all published references | 2026-04-24 | Current timetable period |
| Schedule 8 rate tables | All S8 compensation calculations | 2026-04-24 | CP7 (2024–2029) |
NROD — Network Rail Open Data (TRUST feed)
Source: Network Rail Open Data, available at datafeeds.networkrail.co.uk
What it contains: Real-time train movement events for all signalled trains on the National Rail network. Gauge Intelligence subscribes to the full national TRUST feed, which carries:
- 0001 (Activation): a new train has been activated in TRUST
- 0002 (Cancellation): an activated train has been cancelled
- 0003 (Movement): a passing, arrival, or departure at a reporting point
Each message carries the TRUST ID, timestamp, and location (STANOX). The 0001 message
also carries the toc_id field, which is used for operator identification.
Licence: Open Government Licence v3.0
Refresh cadence: Real-time stream, continuous ingestion via STOMP consumer.
Notes: The full national feed is ingested. There is no corridor filter on ingestion. BST (British Summer Time) correction applies: 3,600,000ms must be subtracted from TRUST timestamps during BST. See the domain rules in data window methodology.
CIF — Common Interface File (Working Timetable)
Source: Network Rail Open Data (NROD), timetable update feed
What it contains: The planned working timetable. Each CIF record defines a schedule
with a train_uid, STP indicator, calling pattern, and timing points. CIF schedules are
the planned benchmark against which TRUST actuals are compared.
What it feeds: Schedule lookup for train activations: headcode-to-service resolution, planned path, scheduled stops. Used in identity resolution and journey building.
Licence: Open Government Licence v3.0
Refresh cadence: Per timetable period change (typically twice per year at major timetable dates). Daily update feed via NROD between period changes.
Last loaded: 1 May 2026 (593,276 schedule records)
Period covered: Current CIF timetable period
Notes: STP priority (C > O > N > P) resolves conflicts where multiple schedules share
the same train_uid and date. The O/P swap bug in TRUST 0001 activations means the
schedule_type field must be corrected before lookup.
BPLAN — Block Plan geography
Source: Rail Data Marketplace (RDM), Peter Hicks weekly product P-f754be7e-06d5-4fa6-8436-c6a801d2ea7c
What it contains: Network Rail’s location reference data: STANOX, TIPLOC, and ELR mappings with geographic coordinates. Used for corridor assignment (mapping STANOX codes to named locations and route corridors) and for distance calculations.
What it feeds: Corridor point resolution: maps each STANOX to its containing national
freight corridor. Powers CorridorPoint and all corridor-scoped performance queries.
Licence: Open Government Licence v3.0
Refresh cadence: Manual download and reload per timetable period. Gauge Intelligence monitors freshness and flags any gap exceeding 10 days. BPLAN is reloaded via a truncate-and-reload transaction.
Last loaded: 2026-04-24
Period covered: Current CIF timetable period
Notes: BPLAN is not deployed with the application (the binary is gitignored). BPLAN staleness is invisible to automated tests. Outdated geography produces silent data drift rather than errors.
STANOX reference table
Source: Network Rail STANOX (Station and Node) reference data, distributed via BPLAN (Rail Data Marketplace product P-f754be7e-06d5-4fa6-8436-c6a801d2ea7c).
What it contains: The full national STANOX registry: numeric codes, location names, and the correspondence between STANOX and TIPLOC. Every location reference in a TRUST message arrives as a raw STANOX code; this table resolves it to a human-readable name.
What it feeds: Location name resolution: converts raw STANOX codes from TRUST messages into human-readable station and junction names. Used in all published location references.
Licence: Open Government Licence v3.0
Refresh cadence: Imported with BPLAN geography; updated when Network Rail publishes STANOX amendments.
Last loaded: 2026-04-24
Period covered: Current timetable period
Schedule 8 rate tables
Source: ORR Track Access Consolidated Agreements, Control Period 7 (2024–2029). Published at orr.gov.uk.
What it contains: The contractual per-minute rates for both directions of Schedule 8 liability — Network Rail to freight operators and freight operators to Network Rail — by control period.
What it feeds: All Schedule 8 compensation calculations.
Control Period 7 base rates (2022-23 prices): Network Rail-to-operator £25.81 per minute (2022-23 base — see inflation indexation methodology); operator-to-Network Rail £51.98 per minute (2022-23 base).
After inflation indexation, the 2025-26 rates are Network Rail-to-operator £28.42 per minute (indexed from the £25.81 base) and operator-to-Network Rail £57.24 per minute (indexed from the £51.98 base).
These rates apply to all bilateral Schedule 8 calculations processed by this archive. The rates are uniform; no per-category structure applies under Control Period 7.
Licence: Open Government Licence / public domain.
Refresh cadence: Fixed for the CP7 period (2024–2029). No reload required until CP8.
Last loaded: 2026-04-24
Period covered: CP7 (April 2024 – March 2029)
Historic Delay Attribution (HDA)
Source: Network Rail, distributed via Rail Data Marketplace under a data sharing arrangement. RDM product identifier: pending verification.
What it contains: Post-hoc attribution of delay minutes to Network Rail or operator responsibility, per incident. HDA data links delay events to root-cause categories and responsible party.
Licence: Non-commercial / attributed. Not reproduced verbatim; used to compute NR-attributed delay minutes for Schedule 8 exposure calculations.
Refresh cadence: Period-end. Manual download or push delivery; no REST endpoint.
Last loaded: pending verification
Open data licensing
All source data is released under the Open Government Licence v3.0 or equivalent open-data terms. Gauge Intelligence’s derived outputs are separately licensed. See the citation guide for reproduction terms.
The processing pipeline that transforms raw feeds into published figures is proprietary but the methodology is fully documented at methodology.