ulmer-eisenbahnfreunde - GTFS transit data for Germany

Active
Ulmer-Eisenbahnfreunde Germany 15 августа 2026 г. — 13 декабря 2026 г.

About This Feed

ulmer-eisenbahnfreunde is the GTFS feed Ulmer-Eisenbahnfreunde publishes for Germany: 27,141 routes, 458,712 stops, 1,132 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 15 августа 2026 г. to 13 декабря 2026 г..

Checked and corrected automatically. How we do it →

One API for this feed

The API behind this page serves the same 27,141 routes and 458,712 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.8918,9.8612&radius=1000
  • Departures at the nearby stops, with real-time delays where the agency publishes them.

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

    GET /v1/routes?origin=50.8918,9.8612&destination=53.8956,47.2214
  • 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.

27,141
Маршруты
458,712
Stops
1,132
Agencies

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-31

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

ZIP GTFS Feed - Corrected & Enriched
425.57 MB
Access: Submit the data request form This work is licensed under Busmaps_licence_v1. Content Hash: eceaf827ec910609
ZIP Validation Report
0.3 MB
127 Errors
611,494 Warnings
102,786 Info
Top Issues
location without parent station 104
block trips with overlapping stop times 23
fast travel between consecutive stops 573,840
GeoJSON GeoJSON Data
17.28 MB

Original Source

Obtained 2026-08-29

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

ZIP GTFS Source Data
551.3 MB
Available through API License: CC_BY_4.0 Content Hash: dafd64e42454f057
ZIP Validation Report
0.4 MB
Available through API
23,799 Errors
1,291,934 Warnings
110,371 Info
Top Issues
number out of range 23,758
block trips with overlapping stop times 23
location with unexpected stop time 14

Overlapping Feeds

Other feeds that share stops or routes with this one.

Feed Stops Overlap Routes Overlap
deutschen-all 259757 (57.28%) 22494 (82.88%)
delfi 361181 (79.65%) 21426 (78.94%)
bwgesamt 35658 (7.86%) 3332 (12.28%)
toplevel-dhid-siflecehpr 6510 (1.44%) 2809 (10.35%)
nordrhein-westfalen-2 23860 (5.26%) 1609 (5.93%)
nah-sh-rjqfrkqhgu 3274 (0.72%) 1178 (4.34%)
vbb 24980 (5.51%) 1124 (4.14%)
vrn 14709 (3.24%) 1116 (4.11%)
erfurter-verkehrsbetriebe-ag 16668 (3.68%) 979 (3.61%)
mvv 13436 (2.96%) 880 (3.24%)
hamburger-verkehrsverbund 10054 (2.22%) 825 (3.04%)
vmt 11067 (2.44%) 744 (2.74%)
mdv-mastscharf 1466 (0.32%) 700 (2.58%)
vvs 4906 (1.08%) 683 (2.52%)
vrs 118 (0.03%) 516 (1.9%)
bwspnv 1152 (0.25%) 513 (1.89%)
avv 5702 (1.26%) 361 (1.33%)
flix-bus-eu 561 (0.12%) 301 (1.11%)
kvv 3195 (0.7%) 243 (0.9%)
odp-swiss 428 (0.09%) 240 (0.88%)
geops-chl 491 (0.11%) 206 (0.76%)
nvbw-rbs 124 (0.03%) 165 (0.61%)
verkehrsverbund 1634 (0.36%) 148 (0.55%)
mvg-munchen 2650 (0.58%) 124 (0.46%)
warnow-siflecehpr 141 (0.03%) 115 (0.42%)
sbg 3936 (0.87%) 94 (0.35%)
rnv 4 (0%) 91 (0.34%)
rhein-neckar-verkehrgmbhrnv 4 (0%) 57 (0.21%)
ostalbmobil-verkehrsverbund 17 (0%) 49 (0.18%)
tuticket 566 (0.12%) 45 (0.17%)
nvbw-filsland 104 (0.02%) 43 (0.16%)
rvs 66 (0.01%) 42 (0.15%)
munster 37 (0.14%)
sweg 98 (0.02%) 35 (0.13%)
jizdnirady 3 (0%) 32 (0.12%)
hofbus 6 (0%) 26 (0.1%)
deutsche-bahn 132 (0.03%) 23 (0.08%)
duk 12 (0%) 19 (0.07%)
flixbus-eu 27 (0.01%) 14 (0.05%)
nationaal-toegangspunt-its 9 (0%) 13 (0.05%)
jdfa 13 (0.05%)
sverige-3 25 (0.01%) 9 (0.03%)
mvo-rail-changeover 12 (0%) 8 (0.03%)
konzern-au 10 (0%) 7 (0.03%)
mvo-rail 4 (0%) 8 (0.03%)
dft-gtfs 21 (0%) 5 (0.02%)
great-britain 18 (0%) 5 (0.02%)
corredores-concesionados-lu 6 (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%)
horaires-des-lignes-ter-sncf 3 (0.01%)
koleje-dolno 3 (0.01%)
norsk 2 (0.01%)
pays-de-la-loire2 2 (0.01%)
ter-sncf 2 (0.01%)
vvt 33 (0.01%) 1 (0%)
vmobil 26 (0.01%)
salzburg-verkehr 11 (0%)
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%)
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 →