mvo-rail - GTFS transit data for Austria

Active
Mobilitaetsverbuende-Oesterreich Austria December 14, 2025 — December 13, 2026

About This Feed

mvo-rail is the GTFS feed Mobilitaetsverbuende-Oesterreich publishes for Austria: 393 routes, 3,545 stops, 13 transit agencies. BusMaps provides the original source through the API. Corrected and validated builds are not available in the API and require the data request form.

Valid from December 14, 2025 to December 13, 2026.

Checked and corrected automatically. How we do it →

One API for this feed

The API behind this page serves the same 393 routes and 3,545 stops: stops near a point, departures, trips, timetables and source GTFS files. The requests below use the coordinates of this feed.

  • Stops within a radius of a coordinate.

    GET /v1/stopsInRadius?location=47.8081,14.5824&radius=1000
  • Departures at the nearby stops, with real-time delays where the agency publishes them.

    GET /v1/nextDepartures?location=47.8081,14.5824&radius=500&results=30
  • Itineraries between two points on this network.

    GET /v1/routes?origin=47.8081,14.5824&destination=49.2466,18.5628
  • Directions, stop order and the schedule of one route.

    GET /v1/line?routeId={routeId}
  • The original source feed, source validation report, and provider links. Processed data is not returned.

    GET /v1/getGtfsFeedsDownloads?feedName=mvo-rail
  • Claude, ChatGPT or any MCP client asks this network questions in plain language.

    https://mcp.busmaps.com/mcp

Base URL https://capi.busmaps.com:8443. Send the key in the capi-key header. Route ids come from the responses above.

393
Routes
3,545
Stops
13
Agencies

GTFS Data Products

Request enhanced data access

The API provides source files only. Submit the data request form to discuss enhanced or custom data, coverage, and delivery terms.

Open the data request form →

Enhanced & Validated Recommended

Updated 2026-09-12

Cleaned, corrected, and validated against GTFS specifications. View corrections.

ZIP GTFS Feed - Corrected & Enriched
58.69 MB
Access: Submit the data request form This work is licensed under Custom_license. Content Hash: c8d22534d9c4c43e
ZIP Validation Report
0.06 MB
2,840 Errors
560 Warnings
1,323 Info
Top Issues
block trips with overlapping stop times 2,836
location without parent station 4
expired calendar 404
GeoJSON GeoJSON Data
0.25 MB

Original Source

Obtained 2026-09-10

Unmodified GTFS data from official sources. May contain errors or inconsistencies.

ZIP GTFS Source Data
221.59 MB
Available through API License: Custom_license Content Hash: 5a31605ddd78e209
ZIP Validation Report
0.12 MB
Available through API
10,053 Errors
3,889 Warnings
1,429 Info
Top Issues
decreasing or equal stop time distance 7,458
block trips with overlapping stop times 2,521
equal shape distance diff coordinates 39

Overlapping Feeds

Other feeds that share stops or routes with this one.

Feed Stops Overlap Routes Overlap
mvo-rail-changeover 2612 (73.99%) 248 (63.1%)
konzern-au 1793 (50.79%) 188 (47.84%)
delfi 5 (0.14%) 11 (2.8%)
ulmer-eisenbahnfreunde 5 (0.14%) 11 (2.8%)
deutschen-all 7 (1.78%)
altoadige-mobilita 3 (0.08%) 5 (1.27%)
bwspnv 14 (0.4%) 4 (1.02%)
vor 454 (12.86%) 2 (0.51%)
bwgesamt 24 (0.68%) 2 (0.51%)
kaerntner-linien 134 (3.8%) 1 (0.25%)
vmobil 24 (0.68%) 1 (0.25%)
geops-chl 1 (0.25%)
ids-jmk 1 (0.25%)
jizdnirady 1 (0.25%)
mav-menetrend 1 (0.25%)
si-nap-gtfs 1 (0.25%)
trenitalia-italy 1 (0.25%)
zsr 1 (0.25%)
ooevv 183 (5.18%)
verbund-linie 149 (4.22%)
vvt 64 (1.81%)
salzburg-verkehr 43 (1.22%)
wiener-linien-original 5 (0.14%)
ids-bk-regional 3 (0.08%)
linz-ag 2 (0.06%)
nordrhein-westfalen-2 2 (0.06%)

Frequently Asked Questions

What is GTFS data?

GTFS, the General Transit Feed Specification, is the open format transit agencies use to publish schedules, stops and route shapes. Trip planners, routing engines and analytics tools read it directly.

What is the difference between enhanced and source data?

Source data is the original GTFS feed obtained from the transit agency or official provider. The enhanced version has been processed to fix errors, remove inconsistencies, and ensure compliance with GTFS specifications. API plans include source data only. Enhanced data requires a separate request through the data request form. Request access through the form →

Can I use this data in my application?

Source-data use depends on the licence set by the publisher; check it before integration. Enhanced and custom data is supplied under terms agreed for your coverage, delivery, and intended use.

How do I validate a GTFS feed?

Every feed here ships with a validation report of errors and warnings. For an independent check, run the MobilityData GTFS Validator. The enhanced feed has the critical issues resolved.

All data comes from public sources. If a file was posted in error, carries a wrong licence or lacks attribution, we will fix it.

Contact us →