VIENNA RAIL
A network-analysis layer beyond route planning: transparent train-position estimates, delay patterns and service signals across Vienna.
Open the live map
WienMobil and ÖBB Scotty focus on passenger essentials such as journey planning, live travel information and service updates. Vienna Rail’s added layer is network-wide analysis: patterns, estimates and model signals in one place.
Follow U-Bahn movement inferred from departure updates alongside S-Bahn timetable estimates and optional tram layers. The map labels estimates as estimates—not as onboard GPS.
NETWORK-WIDE · SOURCE-LABELEDRank observed delay by train, station and line, compare rolling time windows, and build longer-term reports as the archive grows.
RANKINGS · ROLLING WINDOWS · HISTORYHeadway monitoring points to the affected line and corridor or station. Dwell-time and recovery signals add context, with experimental status kept visible.
GAPS · BUNCHING · DWELL · RECOVERYExplore a delay scenario, inspect the 200 m grid where observations exist, and see which models are collecting data, monitored or evaluated. Not every signal is a trained or validated model.
SCENARIOS · SPATIAL LAYERS · MODEL STATUSUse the right tool for the job. Official apps remain the source for operator-issued notices, confirmed journey advice and ticketing. Vienna Rail is an independent analysis companion—not a replacement.
These are captures of the live Vienna Rail interface—not concept artwork. The displayed feed and counts change over time; the notes explain how to read each view.
Route colours distinguish lines; the map legend separates live departure timing with inferred positions from scheduled timetable estimates. A train marker is not an onboard GPS fix.
Rank the operator-reported observations by train, station or line and choose a time window. Missing station metadata can appear as “unknown”; the ranking only covers records the source provides.
Monitoring signals highlight possible headway gaps and close-running trains; the grid summarizes observations where data exists. These are decision-support indicators, not verified causes or operating instructions.
Screens captured from the public app on 15 October 2026. Live values, train counts and source coverage can change after capture.
Start with the network. Then move from a train or station into the information behind it—from departures and delay history to emerging service patterns.
Explore U-Bahn, S-Bahn and optional tram layers, search for favourite stations, and open a train or station for its available details.
Rank reported delay patterns by train, station and line. Explore rolling time windows and compare recent conditions with the wider history being collected.
Model and rule-based signals turn repeated observations into useful prompts—not automatic operational commands.
Vienna Rail brings several kinds of evidence into one place. Each signal keeps its source and certainty visible, so a timetable estimate is never dressed up as a GPS fix.
Open the map and exploreEstimate how a reported delay may evolve, and compare the model with the live departure estimate.
Flag unusually large or small gaps, with the station or corridor where the pattern appears.
Explore station-level delay summaries, dwell-time indicators and post-disruption recovery signals.
Bring together service messages and available weather, mobility or event context where a source is connected.
Model availability and validation status can vary by feature. The in-app model dashboard shows the current status and evaluation metrics; experimental signals should be read as indicators, not guarantees.
The platform keeps published facts, derived estimates and model outputs distinct. That separation is central to understanding what a marker or prediction can—and cannot—tell you.
Read public Wiener Linien departure and service-message feeds, plus published ÖBB timetable data and other connected open sources.
Match departures to stations, lines and planned times. Keep source timestamps and known coverage gaps alongside the observations.
Interpolate train movement from departure predictions and route timings. A marker describes an estimate, not a device installed on the train.
Train on earlier observations, test on later held-out data, compare with a simple baseline, and show the scores in the app.
Vienna Rail is an independent project—not an official Wiener Linien or ÖBB service. It complements operator information with map-based estimates and experimental analysis.
GPS is optional. The app compares your device location with the station list on your device; it does not send the coordinates to the app server.
Predictions can be wrong. They are not operator instructions, a safety system or a substitute for official service notices.
The optional GPT-based advisor is currently disabled in the public app. No AI API key is exposed in the website.
A few important details for using the map and reading its predictions.
No. Wiener Linien’s public real-time feed provides departure predictions, not train GPS. U-Bahn locations are estimated from those predictions and route timing. ÖBB S-Bahn locations are scheduled timetable interpolations.
The app polls its shared snapshot frequently (about every 1.5 seconds). That describes the app’s request cycle, not how often an operator changes its source data; network delays and source updates can affect the information shown.
Yes. The site is a Progressive Web App. On iPhone, open it in Safari, choose Share, then Add to Home Screen. GPS works only after you choose a location feature and grant permission.
No. Some are rule-based or monitored baselines; other candidates may still be collecting labels or awaiting validation. Check the in-app model dashboard for current status, sample counts and scores.
Open the map, choose a line, and follow the evidence from station to station.
