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

The flixbus-eu GTFS feed by NDOV-Loket provides structured public transit data for Germany, covering 457 routes, 1,568 stops, and 2 transit agencies. Formatted according to the General Transit Feed Specification (GTFS), this dataset is ready for transit apps, routing engines, and urban planning tools.

This feed was active from January 6, 2021 to February 21, 2021 and is no longer current. It remains available for historical analysis and research.

Data is automatically validated and corrected. View our quality pipeline →

Transit map showing flixbus-eu routes and stops in Germany
Explore 457 routes, 1,568 stops, and 2 agencies

Browse routes, stops, and agencies from this feed. Public pages show merged data from all feeds. Sign in for per-feed details useful for GTFS integration and debugging.

Sign in to access →

Download Data

Enhanced & Validated Recommended

Updated 2026-07-17

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

ZIP GTFS Feed - Corrected & Enriched
0.54 MB
Download GTFS
This work is licensed under Custom_license. Content Hash: ca273562a93992a551b63d02fd03df40aed6def4
ZIP Validation Report
0.08 MB
Download
0Errors
1,721Warnings
14Info
Top Issues
fast travel between consecutive stops861
fast travel between far stops455
expired calendar389
GeoJSON GeoJSON Data
0.14 MB
Download

Original Source

Obtained 2021-01-07

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

ZIP GTFS Source Data
0.46 MB
Download
License: Custom_license Content Hash: 12eaaff39f4e9dfb799deab45d0b93c12805e352
ZIP Validation Report
0.09 MB
Download
3Errors
1,768Warnings
70Info
Top Issues
missing required column3
fast travel between consecutive stops920
fast travel between far stops481

Overlapping Feeds

Feeds that share stops or routes with this dataset.

Feed Stops Overlap Routes Overlap
flix-bus-eu 164 (10.46%) 72 (15.75%)
flixbus-tr 4 (0.26%) 51 (11.16%)
delfi 28 (1.79%) 15 (3.28%)
idbus 15 (3.28%)
ulmer-eisenbahnfreunde 27 (1.72%) 14 (3.06%)
deutschen-all 20 (1.28%) 12 (2.63%)
blablacar 8 (1.75%)
bwgesamt 5 (1.09%)
sverige 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%)
Build real-time departures into your app Free API Access →

Frequently Asked Questions

What is GTFS data?

General Transit Feed Specification (GTFS) is an open data format for public transit schedules and geographic information. Created by Google and TriMet, it enables transit agencies to publish interoperable data for applications, trip planners, and mobility analytics tools.

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. We recommend the enhanced version for production applications.

Can I use this data in my application?

Data usage depends on the license specified by the original provider. Check the license information in the download section. Many GTFS feeds use open data licenses that allow free use with attribution. Always verify the license terms before integration.

How do I validate a GTFS feed?

Each feed includes a validation report documenting errors and warnings. You can also use the MobilityData GTFS Validator for independent validation. Enhanced feeds have already been processed to resolve the most critical validation issues.

All data on this site comes from publicly available sources. If a file was posted in error, has an incorrect license, or lacks correct source attribution, please contact us and we will correct it.