The site is built for both immediate travel checks and retrospective review. You can use it while travelling, before travelling, or after disruption when you want to know what actually happened.
Most journeys through the site start from one of three places: a station board, a journey search, or a station information page. From there you can open service detail, check delays, or save the route for later.
Different pages are intended for different levels of detail. Some are for quick operational checks, while others are for deeper review, alerts, or compensation guidance.
Use these links to move straight to the part of the site you want explained, instead of scrolling through the whole page.
The homepage is the starting point for most journeys through the site. It is designed to get you into the right tool quickly rather than make you search through menus first.
If you regularly commute between the same stations, the homepage is the quickest place to open that search again without rebuilding it each time.
Live departure boards are for checking what is happening at a station right now. They show departures and arrivals with operational detail such as expected times, platforms, cancellations, short workings and other live changes.
If you are standing on a platform and want to know whether a train is now late, cancelled or short of its booked destination, the live board is the right view.
Service Detail is the deeper view for one individual train. This example shows N46498 from Manchester Victoria to York, opened from the live Leeds board. It brings the route, formation, delay reason, calling points and service actions together in one place.
If a board tells you a train is delayed and you need the full picture, Service Detail is where you inspect the route in context and decide whether to track it, save it, or use it for a later delay claim.
When a route distance is available on the service detail panel, you can click it to open the route-distance map. This gives a visual view of how the train runs across the network rather than only showing the calling-point list.
If you are checking a longer service and want to understand the overall route rather than only the stops, the distance map gives the geographical context.
Journey Search is for service lookups between two stations across a date and time range. It is intended both for planning and for checking what ran on a given day.
If you need to confirm which trains left after 17:00 between two stations yesterday, Journey Search is usually the right place to start.
The station information page is the reference view for a station itself rather than the trains currently serving it. It focuses on facilities, access and operational context for the location.
If you need to know whether a station has step-free access, staffed ticket facilities or storage before travelling, the station information page is the right view.
Delays by Station is the station-level disruption tool. It is different from the live departure board because it is focused on problems, cancellations and late-running patterns across the whole station rather than only the next departures in sequence.
If you need to know whether a station had widespread cancellations or only a few isolated late trains, this is the better view than the live board.
Network Status gives a wider view of conditions across operators and routes. It is intended for checking system-level disruption rather than one individual train.
If you want to know whether disruption is isolated to one route or part of a wider operator problem, Network Status gives the broader context.
Delay Repay Check is a practical tool for estimating whether a delayed or cancelled journey may qualify for compensation. It is intended to help you review likely eligibility before you claim with the operator.
If a train arrived late or was cancelled and you want a fast check on whether the delay is likely to meet the operator’s threshold, this is the right section.
The alerts section is for repeat use. It lets you save regular journeys, choose which kinds of updates matter to you, and manage tracked trains and notification preferences in one place. It also picks up trains you chose to track from a service-detail panel.
If you travel the same route most weekdays and want updates only when something changes, this is the section built for that workflow.
Regular Journey Alerts are built around a route you make repeatedly. The setup lets you define the stations, the days you care about, the active time window, and then the types of alerts you want to receive.
If you commute on a fixed pattern and only want to hear about problems affecting your usual trains, this is the main account workflow to use.
Pinned journeys are homepage shortcuts for repeat searches. They are different from alerts: they save the route and time settings so you can reopen the search quickly, but they do not themselves send notifications.
If you often run the same search but do not need a saved alert, pinning the journey is the lighter-weight shortcut.
Tracking Map shows the stations you have recorded against your account on a national map. It is intended as a visual way to review where you have been rather than a log of individual trains.
If you want a quick visual sense of where you have travelled around the network, the tracking map gives that wider picture at a glance.
Journey History is your recorded travel log. It is designed for keeping track of journeys you have taken and the mileage you have built up over time. Journeys can be added directly from a service-detail panel with Save journey.
If you want a simple rail travel log for personal records or mileage tracking, this section keeps those journeys together.
Most journeys through the site start from a board, a route search or the homepage. From there, you can move deeper into service detail, save the route for later, check whether disruption looks wider than one service, or review whether compensation may apply.
Questions, feedback or data queries can be sent through the contact form or by email to [email protected]. For information about the data feeds and licences used by the service, see the Data Sources page.