toplevel-dhid-siflecehpr - GTFS transit data for Germany

Active
Connect-Info Germany August 6, 2026 — August 5, 2027

About This Feed

toplevel-dhid-siflecehpr is the GTFS feed Connect-Info publishes for Germany: 3,295 routes, 33,986 stops, 112 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 August 6, 2026 to August 5, 2027.

Checked and corrected automatically. How we do it →

One API for this feed

The API behind this page serves the same 3,295 routes and 33,986 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=52.7656,9.181&radius=1000
  • Departures at the nearby stops, with real-time delays where the agency publishes them.

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

    GET /v1/routes?origin=52.7656,9.181&destination=53.3482,10.4368
  • 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=toplevel-dhid-siflecehpr
  • 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: 3,295 routes, 33,986 stops, 112 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
63.35 MB
Access: Submit the data request form This work is licensed under CC_BY-SA_4.0. Content Hash: 047b65fc9a58d166
ZIP Validation Report
0.21 MB
0 Errors
93,983 Warnings
303 Info
Top Issues
fast travel between consecutive stops 86,866
fast travel between far stops 3,167
non ascii or non printable char 2,491
GeoJSON GeoJSON Data
1.6 MB

Original Source

Obtained 2026-08-20

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

ZIP GTFS Source Data
86.12 MB
Available through API License: CC_BY-SA_4.0 Content Hash: 1dae986fb01a2457
ZIP Validation Report
0.22 MB
Available through API
0 Errors
144,939 Warnings
1,161 Info
Top Issues
fast travel between consecutive stops 132,127
fast travel between far stops 4,492
service has no active day of the week 3,111

Overlapping Feeds

Other feeds that share stops or routes with this one.

Feed Stops Overlap Routes Overlap
ulmer-eisenbahnfreunde 6512 (19.16%) 2759 (83.73%)
deutschen-all 2519 (7.41%) 2666 (80.91%)
delfi 5448 (16.03%) 2133 (64.73%)
nah-sh-rjqfrkqhgu 4852 (14.28%) 493 (14.96%)
hamburger-verkehrsverbund 42 (0.12%) 256 (7.77%)
bwspnv 5 (0.01%) 57 (1.73%)
deutsche-bahn 22 (0.06%) 3 (0.09%)
nrw 11 (0.03%) 3 (0.09%)
nationaal-toegangspunt-its 3 (0.09%)
nordrhein-westfalen-2 2 (0.06%)
vmt 1 (0.03%)
warnow-siflecehpr 16 (0.05%)
avv 8 (0.02%)
mdv-mastscharf 5 (0.01%)
geops-chl 3 (0.01%)
odp-swiss 3 (0.01%)

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 →