bwgesamt - GTFS transit data for Germany
ActiveAbout This Feed
bwgesamt is the GTFS feed Nahverkehrsgesellschaft-Baden-Wurttemberg publishes for Germany: 3,676 routes, 56,808 stops, 305 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 9, 2026 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 3,676 routes and 56,808 stops: stops near a point, departures, trips, timetables and source GTFS files. The requests below use the coordinates of this feed.
- Stops around a point Free
Stops within a radius of a coordinate.
GET /v1/stopsInRadius?location=48.5686,9.0391&radius=1000 - Next departures Free
Departures at the nearby stops, with real-time delays where the agency publishes them.
GET /v1/nextDepartures?location=48.5686,9.0391&radius=500&results=30 - A-to-B trip planning Free
Itineraries between two points on this network.
GET /v1/routes?origin=48.5686,9.0391&destination=50.3448,13.9041 - Route timetables Pro
Directions, stop order and the schedule of one route.
GET /v1/line?routeId={routeId} - GTFS source files Free
The original source feed, source validation report, and provider links. Processed data is not returned.
GET /v1/getGtfsFeedsDownloads?feedName=bwgesamt - AI agents (MCP) Free
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.
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
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-22Cleaned, corrected, and validated against GTFS specifications. View corrections.
Original Source
Obtained 2026-08-16Unmodified GTFS data from official sources. May contain errors or inconsistencies.
Overlapping Feeds
Other feeds that share stops or routes with this one.
| Feed | Stops Overlap | Routes Overlap |
|---|---|---|
| ulmer-eisenbahnfreunde | 35612 (62.7%) | 3291 (89.53%) |
| delfi | 35132 (61.85%) | 2994 (81.45%) |
| deutschen-all | 30431 (53.58%) | 2898 (78.84%) |
| vvs | 4556 (8.02%) | 690 (18.77%) |
| vrn | 5272 (9.28%) | 332 (9.03%) |
| kvv | 2110 (3.71%) | 256 (6.96%) |
| odp-swiss | 663 (1.17%) | 232 (6.31%) |
| geops-chl | 582 (1.02%) | 189 (5.14%) |
| nvbw-rbs | 113 (0.2%) | 159 (4.33%) |
| verkehrsverbund | 545 (0.96%) | 138 (3.75%) |
| sbg | 3739 (6.58%) | 128 (3.48%) |
| bwspnv | 149 (0.26%) | 103 (2.8%) |
| flix-bus-eu | 9 (0.02%) | 59 (1.61%) |
| rnv | 2 (0%) | 58 (1.58%) |
| ostalbmobil-verkehrsverbund | 16 (0.03%) | 49 (1.33%) |
| tuticket | 530 (0.93%) | 45 (1.22%) |
| nvbw-filsland | 94 (0.17%) | 42 (1.14%) |
| rvs | 77 (0.14%) | 39 (1.06%) |
| sweg | 468 (0.82%) | 38 (1.03%) |
| rhein-neckar-verkehrgmbhrnv | 2 (0%) | 30 (0.82%) |
| erfurter-verkehrsbetriebe-ag | 126 (0.22%) | 9 (0.24%) |
| region-grandest-gtfs | 11 (0.02%) | 9 (0.24%) |
| flixbus-eu | — | 5 (0.14%) |
| mvv | 71 (0.13%) | 4 (0.11%) |
| cts2 | — | 3 (0.08%) |
| deutsche-bahn | — | 2 (0.05%) |
| horaires-des-lignes-ter-sncf | — | 1 (0.03%) |
| nah-sh-rjqfrkqhgu | — | 1 (0.03%) |
| pays-de-la-loire2 | — | 1 (0.03%) |
| ter-sncf | — | 1 (0.03%) |
| konzern-au | 28 (0.05%) | — |
| nrw | 5 (0.01%) | — |
| sverige-3 | 2 (0%) | — |
| vmt | 2 (0%) | — |
| vrs | 2 (0%) | — |
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 →