Asheville Rides Transit

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. Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.

   Service data ended 9 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.

   Effort: Usually one export setting; export on a schedule so it never lapses again.

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

2. Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.

   The trip updates realtime feed failed during sampling. When this feed is down, riders see scheduled times presented as if they were live.

   Effort: Usually a vendor support ticket.

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

3. Check the vehicle positions endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.

   The vehicle positions realtime feed failed during sampling. When this feed is down, riders see scheduled times presented as if they were live.

   Effort: Usually a vendor support ticket.

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

Ready to send to the agency

Hi Asheville Rides Transit team, Service data ended 9 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist. The fix is usually one export setting: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. Your feed is produced by Trillium, so the quickest path is usually forwarding this to your Trillium contact. 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/asheville-rides-transit/

Copy this note from the full scorecard.

NTD certification readiness: Needs attention

This feed is close to NTD-ready. Service data runs out in 3 days; renew before you certify.

Published Ready

Published at a public URL.

Valid Ready

Passes validation with no errors.

Current Needs attention

Service data runs out in 3 days; renew before you certify.

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://data.trilliumtransit.com/gtfs/asheville-nc-us/asheville-nc-us.zip

Last checked

2026-07-09

Service window

Feed has expired. Last service date 2026-12-31.

Feed version

UTC: 16-Jun-2026 19:44

State

North Carolina