Skip to content
ÖffiGo
00Data & method

How ÖffiGo knows what it knows.

This page shows a number only where one exists, and says where it comes from. Where the data doesn't hold up, you'll see a dash or a gap, not a pretty guess.

01Three kinds of timehow each one is labelled
01

Operator realtime

Delays and cancellations exactly as the operators report them, for example from the Wiener Linien official feeds. This data streams in by the second.

Labelled “operator delay”.

02

Official timetable

The scheduled times as planned. They exist for every trip, even when no realtime is coming in, and they are the base everything else builds on.

Labelled “timetable”.

03

Our own measurement & estimates

From measured arrivals and departures we compute our own numbers: punctuality after the fact, departure estimates ahead of it. An estimate is only shown where it grades well against official realtime.

Labelled “our own live estimate” or “measured”.

02Sources and their roleactive, publicly attributable access
01

Verkehrsauskunft Österreich (VAO)

Primary source for nationwide timetables, place search, routing and embedded disruption information.

02

Wiener Linien Open Data

Official operator realtime for Vienna stops and the network map's live departure boards.

03

Verbund Linie · TRIAS

Authorised regional scheduled and realtime stop events for Styria and the reliability history derived from them.

04

OpenStreetMap · Apple MapKit

OpenStreetMap supplies mapped station paths; MapKit provides maps plus supplementary on-device address and POI search.

05

GeoSphere Austria · Open-Meteo

GeoSphere observations inform the server-side estimate inputs; Open-Meteo adds weather context in the iPhone app.

Infrastructure, not passenger data

The website runs on Vercel and the ÖffiGo API on Railway. Supabase stores approved aggregates and beta requests, Cloudflare protects and caches public API responses and archives raw data, and Resend sends transactional confirmations only when mail delivery is configured.

Currently inactive

HERE Traffic currently supplies no data to ÖffiGo. Technical fallbacks are not publicly guaranteed data sources and are therefore not presented as partners.

03What we measure ourselves

We count individual stops: arrivals and departures at the platform. No GPS points from moving vehicles, which wouldn't say anything about schedule deviation anyway. Every day we hold our own estimates against the operators' official realtime and note the deviation. Those grades decide whether an estimate is shown at all. Current figures:

1,555,356
stops measured
arrivals and departures
94.5 %
on time
under 3 minutes deviation
0.6 min
average deviation
across all measured stops
44
days covered
since the first measurement
04Coverage windows15 July 2026 — 29 August 2026

Processing completes each day before it counts: a day appears in the statistics only once all of that day's arrivals and departures have been handled. So the end of a chart can sit behind today's date. When collection for an area is paused, the affected charts show the historical stand through the last complete day and say so.

Processed period15 July 2026 — 29 August 2026
Fully processed throughCollection paused29 August 2026
DeparturesDeparture times at your stop, including operator realtime.running
Route planningConnections from A to B, transfers and guidance.running
Live estimatesOur own estimate when it's more reliable than the timetable.running
Punctuality dataThe analysis behind the punctuality page.running

The numbers in context

Today's measurements, long-run punctuality, service state and every change to the data: every view on this website draws from the same sources as this page.

Live →Reliability →Status →Changelog →