ulmer-eisenbahnfreunde - GTFS transit data for Germany

Active
Ulmer-Eisenbahnfreunde Germany July 25, 2026 — December 13, 2026

About This Feed

ulmer-eisenbahnfreunde is the GTFS feed Ulmer-Eisenbahnfreunde publishes for Germany: 26,847 routes, 454,746 stops, 1,129 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 July 25, 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 26,847 routes and 454,746 stops: stops near a point, departures, trips, timetables, live vehicle positions 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.8837,9.8554&radius=1000
  • Departures at the nearby stops, with real-time delays where the agency publishes them.

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

    GET /v1/routes?origin=50.8837,9.8554&destination=53.8895,47.217
  • Directions, stop order and the schedule of one route.

    GET /v1/line?routeId={routeId}
  • GTFS-RT positions inside the bounding box of the feed.

    GET /v1/rawVehiclePositions?boundingBox=39.075,-8.861,62.907,159.302
  • The original source feed, source validation report, and provider links. Processed data is not returned.

    GET /v1/getGtfsFeedsDownloads?feedName=ulmer-eisenbahnfreunde
  • 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: 26,847 routes, 454,746 stops, 1,129 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
354.03 MB
Access: Submit the data request form This work is licensed under Busmaps_licence_v1. Content Hash: 44bfeabc8c491528
ZIP Validation Report
0.32 MB
146 Errors
431,163 Warnings
101,973 Info
Top Issues
location without parent station 134
block trips with overlapping stop times 12
fast travel between consecutive stops 402,826
GeoJSON GeoJSON Data
17.16 MB

Original Source

Obtained 2026-08-10

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

ZIP GTFS Source Data
451.04 MB
Available through API License: CC_BY_4.0 Content Hash: 9521850a73cb57d9
ZIP Validation Report
0.39 MB
Available through API
23,276 Errors
808,771 Warnings
112,159 Info
Top Issues
number out of range 23,245
location with unexpected stop time 16
block trips with overlapping stop times 13

Overlapping Feeds

Other feeds that share stops or routes with this one.

Feed Stops Overlap Routes Overlap
delfi 363736 (80.63%) 21667 (80.71%)
deutschen-all 254115 (56.33%) 21225 (79.06%)
nrw 51768 (11.48%) 5418 (20.18%)
bwgesamt 35612 (7.89%) 3305 (12.31%)
toplevel-dhid-siflecehpr 6512 (1.44%) 2780 (10.35%)
nordrhein-westfalen-2 23882 (5.29%) 1598 (5.95%)
nah-sh-rjqfrkqhgu 3285 (0.73%) 1183 (4.41%)
vrn 14541 (3.22%) 1102 (4.1%)
vbb 24457 (5.42%) 1090 (4.06%)
erfurter-verkehrsbetriebe-ag 16516 (3.66%) 961 (3.58%)
mvv 13397 (2.97%) 885 (3.3%)
hamburger-verkehrsverbund 10165 (2.25%) 823 (3.07%)
vmt 10919 (2.42%) 730 (2.72%)
mdv-mastscharf 1470 (0.33%) 679 (2.53%)
vvs 4875 (1.08%) 672 (2.5%)
vrs 109 (0.02%) 508 (1.89%)
bwspnv 1163 (0.26%) 501 (1.87%)
avv 5698 (1.26%) 360 (1.34%)
flix-bus-eu 560 (0.12%) 299 (1.11%)
kvv 3209 (0.71%) 243 (0.91%)
odp-swiss 426 (0.09%) 238 (0.89%)
geops-chl 487 (0.11%) 208 (0.77%)
nvbw-rbs 124 (0.03%) 168 (0.63%)
verkehrsverbund 1625 (0.36%) 149 (0.55%)
mvg-munchen 2618 (0.58%) 121 (0.45%)
warnow-siflecehpr 139 (0.03%) 110 (0.41%)
sbg 3957 (0.88%) 94 (0.35%)
rnv 4 (0%) 86 (0.32%)
rhein-neckar-verkehrgmbhrnv 4 (0%) 59 (0.22%)
rvs 68 (0.02%) 47 (0.18%)
ostalbmobil-verkehrsverbund 17 (0%) 49 (0.18%)
tuticket 566 (0.13%) 45 (0.17%)
nvbw-filsland 104 (0.02%) 44 (0.16%)
munster 37 (0.14%)
sweg 94 (0.02%) 35 (0.13%)
jizdnirady 3 (0%) 31 (0.12%)
hofbus 6 (0%) 26 (0.1%)
deutsche-bahn 140 (0.03%) 19 (0.07%)
duk 12 (0%) 19 (0.07%)
flixbus-eu 27 (0.01%) 14 (0.05%)
jdfa 13 (0.05%)
nationaal-toegangspunt-its 9 (0%) 11 (0.04%)
sverige-3 25 (0.01%) 9 (0.03%)
konzern-au 10 (0%) 7 (0.03%)
dft-gtfs 20 (0%) 5 (0.02%)
idbus 6 (0.02%)
sverige-sw 6 (0.02%)
blablacar 5 (0.02%)
miejska-boleslawiec 5 (0.02%)
region-grandest-gtfs 5 (0.02%)
circula 26 (0.01%) 2 (0.01%)
great-britain 17 (0%) 3 (0.01%)
corredores-concesionados-lu 4 (0.01%)
horaires-des-lignes-ter-sncf 3 (0.01%)
norsk 2 (0.01%)
pays-de-la-loire2 2 (0.01%)
ter-sncf 2 (0.01%)
flixbus-tr 4 (0%)
wielkopolska 4 (0%)
auvergne-rhone-alpes 1 (0%)
bel-rail 1 (0%)
emtu 1 (0%)
eu-es-gtfs 1 (0%)
eurolines 1 (0%)
koleje-dolno 1 (0%)
linek-pid 1 (0%)
mav-menetrend 1 (0%)
rejseplanen-dk 1 (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 →