Germany long-distance rail aggregate (gtfs.de)

What changed since the last check

• Correctness no change
• Freshness down 1.7
• Rider experience no change

Top three things to fix

1. Re-export with a validity window that reaches at least 60 days out.

   Service data runs out in 29 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.

   Effort: One export setting.

2. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.

   1219 of 1219 stops don't say whether a wheelchair user can board there. Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.

   Effort: A column in stops.txt; your scheduling software likely has it.

3. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.

   5147 of 5147 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the transit vehicle itself can take them.

   Effort: A default or per-trip field in your export.

Ready to send to the agency

Hi Germany long-distance rail aggregate (gtfs.de) team, Service data runs out in 29 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice. The fix is usually one export setting: Re-export with a validity window that reaches at least 60 days out. This came from your GTFS data quality scorecard, which checks the feed you publish and lists the fixes in plain language: https://gtfsscorecard.org/agency/gtfs-de-long-distance-rail/

Copy this note from the full scorecard.

Key facts

Feed URL

https://download.gtfs.de/germany/fv_free/latest.zip

Last checked

2026-07-19

Service window

29 days of service data remain. Last service date 2026-08-17.

Feed version

latest-fv-free

Location

Germany