Regional Transportation District

What changed since the last check

• Correctness no change
• Freshness no change
• Rider experience no change

Top three things to fix

1. Review the rule documentation for 'missing_trip_edge' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

   Missing trip edge (flagged by the MobilityData validator). See the linked rule for what this affects.

   Effort: Varies.

2. Review the rule documentation for 'stop_time_with_only_arrival_or_departure_time' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

   Stop time with only arrival or departure time (flagged by the MobilityData validator). See the linked rule for what this affects.

   Effort: Varies.

3. Review the rule documentation for 'block_trips_with_overlapping_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

   Block trips with overlapping stop times (flagged by the MobilityData validator). See the linked rule for what this affects.

   Effort: Varies.

NTD GTFS readiness: Needs attention

This feed is close to NTD-ready. 4 validator errors to resolve.

Published Ready

Published at a public URL.

Valid Needs attention

4 validator errors to resolve.

Current Ready

Service data covers the next 88 days.

agency_id and NTD ID: Not checked yet. Setting your GTFS agency_id to your five-digit NTD ID is an optional way to line a feed up with its National Transit Database record. FTA links the two on your P-50 form, so it is not a required feed change. We don't have your NTD ID on file, so this is not checked yet.

Key facts

Feed URL

https://www.rtd-denver.com/files/gtfs/google_transit_flex.zip

Last checked

2026-07-11

Service window

77 days of service data remain. Last service date 2026-09-26.

Feed version

Jun26-36807-13-20-20260629-040324