Search for a station to see departures and arrivals.
Everything you need to know about using OpenTrack.
OpenTrack is a real-time European rail information tool for travellers and enthusiasts. It provides live departure and arrival boards, service detail pages with calling points, and journey planning — all in one place, covering rail networks across Europe.
Track shows a live departure or arrival board for any European rail station. Search for a station, choose a date and time, and click Show board. The board displays up to two hours of services from the selected time.
Each service row shows an inline status. For trains not yet departed: On time or Due at HH:MM (+Xm) if delayed. For trains that have left: Departed at HH:MM (+Xm) or Departed on time. Cancelled services appear struck through in red.
Part-cancelled services show the original destination or origin struck through in orange, with the new effective terminus or origin shown alongside in black. For example, a departure that no longer runs to its full destination will show Original Dest New Terminus, and an arrival from a truncated origin will show Original Origin New Origin.
Filter the board by an intermediate calling station. Choose Will call at to show trains yet to reach that stop, or Has called at for trains that have already passed through. OpenTrack checks the full calling pattern of each service, not just the destination.
Once a board has loaded, an Operator dropdown appears in the sidebar populated with the operators running services in that window. Select any operator to filter the board to their services only, or choose All operators to clear the filter. The dropdown is disabled until results appear.
Pin frequently used stations for quick access. On desktop, pinned stations appear in the track sidebar. On mobile, they appear as a scrollable chip bar just below the nav — tap any chip to load that station's board, or tap the cog icon at the right of the bar to manage your pins. Add and remove pins in Settings → App settings → Pinned stations.
Click any service row to open its detail page. This shows the full calling pattern with planned and real-time times, platform numbers, delay information, and country boundary indicators. On desktop an interactive route map is always shown alongside, with a live train position marker. On mobile, tap the Map button in the bottom bar to reveal it.
The service page has three icon buttons on desktop: copy link, refresh, and station query (the cog icon). On mobile, these appear in the bottom navigation bar alongside a Map toggle.
A coloured pill below the service header shows the train's current state in real time:
When a service is currently running, the route map shows a live marker interpolated between the last departed stop and the next arrival. The marker colour matches the status badge — blue for on time, orange for delayed or part-cancelled, green for early. Click the marker to see which stops the train is between and the current delay.
Click the cog icon on any service page to open the station query tool. Select any two calling points from the dropdowns and click Query stations. The tool shows straight-line distance, compass bearing, and detail cards for each station including country, local time, timezone, coordinates, and stop ID.
A divider row appears wherever the train crosses a national border, labelled with the two country names (e.g. Germany → Austria). Timezone changes are shown alongside where applicable.
Plan lets you search for rail journeys between two stations. Enter a departure and arrival station, choose a date and time, and click Search journeys. Results show up to five itineraries with departure/arrival times, journey duration, number of changes, and leg-by-leg detail.
Tick Arriving by this time to search backwards from an arrival deadline. Click any leg to open its service page. Each result has a map icon.
OpenTrack automatically filters out itineraries that contain implausible connections — specifically, any result with a connection wait longer than 3 hours, or where consecutive legs are geographically disconnected (for example, arriving in one country and departing from a station hundreds of kilometres away with no connecting leg). These phantom results are an artefact of missing data in the underlying timetable feed — most commonly when a cross-channel or ferry leg isn't available — and hiding them keeps results meaningful.
Itineraries that include non-rail legs (such as bus or coach) are also hidden. The journey planner requests rail-only routes, but the underlying engine occasionally returns mixed-mode itineraries where no purely rail path exists — these are suppressed so results always reflect genuine rail connections. If no valid itineraries remain, a "no journeys found" message is shown instead.
By default, itineraries with any connection shorter than 10 minutes are filtered out — a tight connection that may be unrealistic in practice. You can raise or lower this threshold under App settings → Planning → Minimum connection time. Set it to 0 to disable the check entirely.
When Plan debugging is turned on in App settings, a notice appears below the results listing any itineraries that were filtered out, with a brief reason for each. This is off by default. Enable it under App settings → Planning → Plan debugging.
Click the account icon in the top-right corner to open the account menu. From here you can access Account settings, App settings, and Help.
Set your name under Account settings → Profile. It appears as a welcome greeting on each page. You can also upload a profile photo which shows in the top-right corner. Changes are held until you click Save — navigating away with unsaved changes will prompt a confirmation.
Manage your Pinned stations here — add stations using the search modal or remove them with the × button. All changes in App settings go through a save bar at the bottom — click Save to apply or Discard to revert. Navigating away with unsaved changes will prompt a confirmation.
The Planning group controls how journey plan results are filtered:
Minimum connection time — itineraries with any connection shorter than this are hidden. Default is 10 minutes. Set to 0 to disable.
Plan debugging — when on, a notice appears below plan results showing any filtered itineraries and why. Off by default.
All times are shown in each station's local time — not your device's timezone and not UTC. A train leaving London at 10:00 and arriving in Paris at 13:18 is a 2h 18m journey: Paris is UTC+1 (CET), London is UTC+0 (GMT).
The current timezone is shown in the board's updated line (e.g. Times in CET). On service pages, country boundary dividers show timezone changes where applicable.
Live delay and cancellation data is sourced from GTFS-RT feeds provided by operators across Europe. Coverage is still being understood and varies significantly by country, operator, and route — some networks publish comprehensive real-time feeds while others provide timetable data only, with no live delay information.
For time-sensitive travel, always cross-reference with the relevant national operator's own app or website. The Transitous project, which powers OpenTrack's data, is a good place to understand what feeds are currently active.
Real-time data is only available for current and near-future services. For trains that departed hours or days ago, the realtime columns will show "No data".
OpenTrack works well on mobile browsers. On Android with Chrome, you will be prompted to install it as an app. On iOS with Safari, tap the Share button and choose Add to Home Screen. Once installed, OpenTrack opens in standalone mode with no browser chrome.
On mobile, pinned stations appear as a scrollable chip bar below the nav bar on the Track page. The cog icon at the right of the bar opens App settings to manage your pins.
Timetable and real-time data is provided by Transitous / MOTIS, an open-source multimodal routing engine fed by GTFS and GTFS-RT data from operators across Europe. Map tiles by CARTO and OpenStreetMap contributors.
Found a bug, have a feature request, or want to give feedback? Get in touch at projects@harryburr.com.
For known limitations and current information about data coverage, see the Disclaimers page.
OpenTrack is in active development. This page documents current limitations, known bugs, and where to follow progress.
No in-depth research has been done yet into which countries and operators actually provide usable data through the Transitous/MOTIS backend. Coverage varies significantly and has not been systematically tested.
In general, some countries publish comprehensive GTFS and GTFS-RT feeds (real-time delays and cancellations), others publish timetable data only (no live information), and some have little or no data at all. The same country may have excellent coverage for intercity trains and none at all for regional services, or vice versa.
Until proper per-country research is done, treat all data as potentially incomplete. The status displayed as "No real-time data" may mean the operator genuinely doesn't publish live feeds, or simply that they do but aren't yet ingested.
Delay and cancellation information is sourced from GTFS-RT feeds, which vary significantly in quality and latency across operators. Some feeds update in near real-time; others may be several minutes behind or only update at departure. Platform information is often missing entirely.
The journey planner may occasionally suggest routes with very long connection times or geographically implausible transfers. A filtering system suppresses the worst cases, but some unusual results may still appear. Always verify connections are reasonable before booking.
To see which results have been filtered and why, turn on Plan debugging under App settings → Planning. When enabled, a notice appears below plan results listing any hidden itineraries with a brief reason for each.
Some operators (particularly French SNCF) use internal mission codes as headsigns (e.g. VOPE, QURI) rather than readable destination names. OpenTrack attempts to replace these with the actual terminus station where possible, but may not always succeed.
Service page maps draw straight crow-flies lines between stations rather than following the actual railway track. This is a data limitation — the underlying API provides only coarse intermediate waypoints, not full GTFS shape data.
Trains that terminate at the displayed station may not always appear on the arrivals board. This depends on how the upstream feed provides terminus stop data.
UK train services are included in principle but real-time data quality is inconsistent. Some operators work well; others show no live information at all. The Darwin feed (used by National Rail) is not currently integrated.
The full development roadmap, version history, and planned features are maintained externally. Click the button above or visit the link below.