This feed has expired Service dates: 2018-12-09 - 2019-12-14

deutsche-bahn - GTFS transit data for Germany

Expired
Rhein-Neckar-Verkehr Germany December 9, 2018 — December 14, 2019

About This Feed

deutsche-bahn is the GTFS feed Rhein-Neckar-Verkehr publishes for Germany: 1,364 routes, 661 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.

Active from December 9, 2018 to December 14, 2019; 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 1,364 routes and 661 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=50.1077,11.274&radius=1000
  • Departures at the nearby stops, with real-time delays where the agency publishes them.

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

    GET /v1/routes?origin=50.1077,11.274&destination=51.6205,17.8545
  • 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=deutsche-bahn
  • 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: 1,364 routes, 661 stops, 13 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-22

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

ZIP GTFS Feed - Corrected & Enriched
1.14 MB
Access: Submit the data request form The license for this work is not specified Content Hash: 6295d5646f23f6ae
ZIP Validation Report
0.02 MB
0 Errors
2,979 Warnings
0 Info
Top Issues
expired calendar 2,921
non ascii or non printable char 56
feed expiration date7 days 1
GeoJSON GeoJSON Data
0.06 MB

Original Source

Obtained 2019-01-10

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

ZIP GTFS Source Data
0.83 MB
Available through API The license for this work is not specified Content Hash: 9df4a0aadaa78c64
ZIP Validation Report
0.02 MB
Available through API
3 Errors
2,984 Warnings
1 Info
Top Issues
stop time with arrival before previous departure time 3
expired calendar 2,924
non ascii or non printable char 56

Overlapping Feeds

Other feeds that share stops or routes with this one.

Feed Stops Overlap Routes Overlap
deutschen-all 274 (41.45%) 93 (6.82%)
delfi 164 (24.81%) 89 (6.52%)
ulmer-eisenbahnfreunde 140 (21.18%) 84 (6.16%)
corredores-concesionados-lu 30 (2.2%)
geops-chl 28 (4.24%) 28 (2.05%)
nationaal-toegangspunt-its 23 (1.69%)
odp-swiss 37 (5.6%) 19 (1.39%)
nah-sh-rjqfrkqhgu 31 (4.69%) 19 (1.39%)
bwgesamt 16 (1.17%)
horaires-des-tgv 15 (1.1%)
toplevel-dhid-siflecehpr 22 (3.33%) 7 (0.51%)
bwspnv 16 (2.42%) 4 (0.29%)
flix-bus-eu 4 (0.29%)
region-grandest-gtfs 4 (0.29%)
eurostar 4 (0.61%) 1 (0.07%)
bel-rail 1 (0.07%)
mvv 1 (0.07%)
vvs 1 (0.07%)
mdv-mastscharf 15 (2.27%)
avv 11 (1.66%)
hamburger-verkehrsverbund 6 (0.91%)
vmt 4 (0.61%)
nrw 2 (0.3%)

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 →