Regional Transportation District (RTD)

What changed since the last check

• Correctness no change
• Freshness no change
• Rider experience no change
• Realtime quality no change

Top three things to fix

1. Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default).

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

   Effort: Often one default setting in your export.

   Agencies here usually clear this within about 1 week (based on 5 observed fixes).

2. Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.

   The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

   Effort: A small file for most flat-fare systems.

3. Check the flagged stop times for transposed minutes.

   Some scheduled trips move faster between stops than a bus can. Usually a typo'd stop time; riders get arrival times no bus can meet.

   Effort: A few minutes per flagged trip.

   Agencies here usually clear this within about 2 weeks (based on 6 observed fixes).

NTD certification readiness: Ready

Published at a public URL, valid, and current: the three things the NTD GTFS requirement asks of a feed all hold here. Only your own D-10 certification makes that official; this is a heads-up, not a determination.

Published Ready

Published at a public URL.

Valid Ready

Passes validation with no errors.

Current Ready

Service data covers the next 80 days.

agency_id and NTD ID: Not aligned. Your feed's agency_id is RTD; your National Transit Database ID is 80006. A feed that serves several agencies (a shared regional feed) can legitimately carry more than one agency_id, so a difference here is a heads-up, not an error. Optionally set the agency_id for your service to 80006 in agency.txt (and the matching agency_id in routes.txt) so the feed lines up with your NTD record. It is a convenience, not a required feed change: FTA also links agency_id to your NTD ID on your P-50 form.

The bar this score answers to

The state transit-data program is CDOT Digital Transit Mobility. Colorado's program coordinating GTFS data across transit providers.

Key facts

Feed URL

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

Last checked

2026-07-09

Service window

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

Feed version

Jun26-36807-13-20-20260708-030320

State

Colorado