Search above, or pick a station below. Each entry pulls together what several separate reference datasets know about the same place — the passenger-facing details from National Rail's KnowledgeBase, the operational identifiers from Network Rail's location database, and the engineering position from the track model.
A station is not one thing to the railway. It is a retail location to the ticketing system, a set of platforms to the signaller, a point on a line to the engineer, and an accounting entity to the settlement system — and each of those built its own identifier decades before anyone tried to join them up.
This page shows all of them together, which is harder than it sounds: no single dataset contains the lot. The passenger details come from National Rail's KnowledgeBase, the operational codes from Network Rail's location database, and they have to be matched to each other before anything can be displayed.
Positions on the railway are measured along a numbered route — an ELR, or Engineer's Line Reference — in miles and chains, where a chain is 22 yards and there are 80 to the mile. So SPC1 0m 10ch means ten chains, a quarter of a mile, along the line coded SPC1.
A station can honestly have several of these at once. Where two lines meet, the station sits at a position on each of them, measured from a different zero — Clapham Junction has more than one position on a single ELR, because the measurement follows the track and the station spans a lot of it. Multiple entries are the correct answer, not duplicates.
Not sure what CRS, TIPLOC or miles-and-chains mean? The FAQ explains the codes. For live trains at a station, use the departure boards.
Guide: what the railway calls a place — why one station has a CRS, a TIPLOC, a STANOX and a NLC, which systems use which, and why ten of the eleven places matching "Corby" are not stations.