This feed has expired Service dates: 2021-01-06 - 2021-02-21

flixbus-eu - GTFS transit data for Germany

Expired
NDOV-Loket Germany January 6, 2021 — February 21, 2021

About This Feed

flixbus-eu is the GTFS feed NDOV-Loket publishes for Germany: 457 routes, 1,568 stops, 2 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.

Active from January 6, 2021 to February 21, 2021; the schedule has ended. The files stay available for analysis.

Checked and corrected automatically. How we do it →

One API for this feed

The API behind this page serves the same 457 routes and 1,568 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=44.8103,15.3181&radius=1000
  • Departures at the nearby stops, with real-time delays where the agency publishes them.

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

    GET /v1/routes?origin=44.8103,15.3181&destination=48.5879,22.4682
  • 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=flixbus-eu
  • 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.

Per-feed pages: 457 routes, 1,568 stops, 2 agencies

Public pages merge every feed. Sign in to browse this feed on its own, which helps when you integrate or debug it.

Sign in →

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-08-21

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

ZIP GTFS Feed - Corrected & Enriched
0.54 MB
Access: Submit the data request form This work is licensed under Custom_license. Content Hash: ca273562a93992a5
ZIP Validation Report
0.08 MB
0 Errors
1,721 Warnings
14 Info
Top Issues
fast travel between consecutive stops 861
fast travel between far stops 455
expired calendar 389
GeoJSON GeoJSON Data
0.14 MB

Original Source

Obtained 2021-01-07

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

ZIP GTFS Source Data
0.46 MB
Available through API License: Custom_license Content Hash: 12eaaff39f4e9dfb
ZIP Validation Report
0.09 MB
Available through API
3 Errors
1,768 Warnings
70 Info
Top Issues
missing required column 3
fast travel between consecutive stops 920
fast travel between far stops 481

Overlapping Feeds

Other feeds that share stops or routes with this one.

Feed Stops Overlap Routes Overlap
flix-bus-eu 164 (10.46%) 69 (15.1%)
flixbus-tr 4 (0.26%) 52 (11.38%)
idbus 15 (3.28%)
ulmer-eisenbahnfreunde 27 (1.72%) 14 (3.06%)
deutschen-all 20 (1.28%) 12 (2.63%)
blablacar 9 (1.97%)
bwgesamt 5 (1.09%)
sverige-sw 5 (1.09%)
sverige-3 2 (0.13%) 4 (0.88%)
jdfa 4 (0.88%)
eurolines 2 (0.44%)
jizdnirady 2 (0.44%)
atm 1 (0.22%)
dft-gtfs 1 (0.22%)
generalitat-catalunya 1 (0.22%)
great-britain 1 (0.22%)
horaires-des-lignes-intercites-sncf 1 (0.22%)
horaires-des-lignes-ter-sncf 1 (0.22%)
norsk 1 (0.22%)
rejseplanen-dk 1 (0.22%)
sncf 1 (0.22%)

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 →