Feed status · checked 2026-08-01
Asheville Rides Transit
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in North Carolina.
A data-quality and completeness lens to help an agency improve its GTFS feed. Not an official compliance determination from any transit program. New to this? How to read your scorecard. Interactive view of this scorecard. Rubric v1.3, validator 8.0.1.
Checked for changes 83 minutes ago; last changed 22 days ago.
Measured 4 of 4 score categories from the agency's own feed.
How we measured this
Confidence in this measurement: high.
- All four score categories were measured this run.
- Realtime was sampled in one bounded window of 3 snapshots.
- The feed was downloaded from the agency's own URL.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
Check the service alerts endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
The service alerts realtime feed failed during sampling. When this feed is down, riders see scheduled times presented as if they were live.
⏱ Usually a vendor support ticket.worth about +100 points in its category
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.Likely your team
668 of 677 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.
⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category
Remove retired stops from the export, or add them back to the trips that should serve them.Likely your export tool
Some stops exist in the feed but no trip ever stops at them. Riders may walk to a stop where no bus is scheduled to arrive.
⏱ A review pass in your scheduling software.worth about +6 points in its category
Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
Finding handoff
Move one finding to a recheck
Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.
- Feed evidence
- The service alerts realtime feed failed during sampling.
- Next action
- Check the service alerts endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- 668 of 677 stops don't say whether a wheelchair user can board there.
- Next action
- Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- Some stops exist in the feed but no trip ever stops at them.
- Next action
- Remove retired stops from the export, or add them back to the trips that should serve them.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
How to make and check these changes
Check the result on the published feed. Read the guide, make the change in your tool, and use the next comparable run to see whether the finding is still reported. Only an action or ticket record can attribute who made the change.
Check the service alerts endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. · Read the fix guide
Make the change. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. · Read the fix guide
Make the change. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Remove retired stops from the export, or add them back to the trips that should serve them. · Read the fix guide
Make the change. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Rider view: what this feed publishes
A quick read of rider-facing information in this feed.
- Schedule visibility
- The feed's last published service date is in 152 days.
- Published accessibility data
- Accessibility information is stated for 1.3% of stops and 100% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- Fare information is published using GTFS Fares v1.
- Realtime information
- No realtime feed was reachable during sampling.
Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.
Send Trillium a fix request
This feed is produced and hosted by Trillium. Copy this and send it to your Trillium contact; they make the change and republish the feed. Each fix names the validator notice and a guide link.
Score by category
The MobilityData validator flagged 6 kinds of issue across 77 instances (0 error, 32 warning, 45 informational).
Service data covers the next 152 days.
1% of stops state wheelchair accessibility (1% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
1% of stops state accessibility (1% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
653 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Hendersonville Rd at Allen Ave", "Airport Rd at Terminal Dr", "Asheville Regional Airport / Wright Brothers Way", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
This feed models stations or entrances but has no pathways.txt and levels.txt.
Consider: Add pathways.txt connecting entrances, platforms, and elevators, and levels.txt for each floor, so the step-free route is described.
Opportunities to strengthen the data, not deductions from the sub-score above. States what the second accessibility lens can check from the feed, not verified physical usability.
Fares are applied to trips.
Sampled 3 times: 0 of 1 configured feed healthy.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 677 stops.
The route and stop data is ready below. Load the map only when you want the geographic view. It uses additional data.
Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- N1 (teal)
- N2 (red)
- N3 (green)
- 170 (brown)
- S1 (red)
- S2 (orange)
- S3 (gray)
- S4 (pink)
- W1 (orange)
- W2 (green)
- S5 (purple)
- W5 (orange)
- N4 (purple)
- N5 (green)
- WE1 (teal)
- WE2 (gray)
- W6 (red)
- S6 (teal)
| Route | Type | Line color |
|---|---|---|
| N1 North 1 | Bus | teal |
| N2 North 2 | Bus | red |
| N3 North 3 | Bus | green |
| 170 | Bus | brown |
| S1 South 1 | Bus | red |
| S2 South 2 | Bus | orange |
| S3 South 3 | Bus | gray |
| S4 South 4 | Bus | pink |
| W1 West 1 | Bus | orange |
| W2 West 2 | Bus | green |
| S5 South 5 | Bus | purple |
| W5 West 5 | Bus | orange |
| N4 North 4 | Bus | purple |
| N5 North 5 | Bus | green |
| WE1 West East 1 | Bus | teal |
| WE2 West East 2 | Bus | gray |
| W6 West 6 | Bus | red |
| S6 South 6 | Bus | teal |
List every stop
- Hendersonville Rd at Allen Ave
- Airport Rd at Terminal Dr
- Asheville Regional Airport / Wright Brothers Way
- Long Shoals Rd at Overlook Rd
- Long Shoals Rd at Overlook Rd
- Long Shoals Rd at Schenck Pkwy
- Long Shoals Rd at Skyland Inn Dr
- Medical Park Dr at Sweeten Creek Rd
- Swannanoa River Rd at E Hawthorne Dr
- Hill St at Riverside Dr
- Mt. Carmel Rd at Ingles
- Old County Home Rd at Exxon
- Old County Home Rd at Fire Department
- New Leicester Hwy at Walgreens
- New Leicester Hwy at Tradewind Dr
- Bartlett St at Depot St
- Bartlett St at Bartlett Arms
- Depot St at Livingston St
- MAHEC at Hampton Inn
- Old Haw Creek Rd at Dillingham Rd
- Old Haw Creek Rd at Trinity Chapel Rd
- Old Haw Creek Rd at Bethesda Rd
- Bethesda Rd at Old Haw Creek Rd
- Spruce Hill Lane at Building 146
- Spruce Hill Lane at Building 102
- Old Haw Creek Rd at Spruce Hill
- New Haw Creek Rd at Rendezvous
- Beverly Rd at Avon Rd
- N Bear Creek Rd at Cub Rd
- N Bear Creek Rd at Johnston Blvd
- Johnston Blvd at Oakmont Terrace
- Haywood Rd at Balm Grove Ave
- Haywood Rd at Baker Ave
- Haywood Rd at Allen St
- ART Station (on Coxe Ave)
- ART Station (170 + WE1 EB Bay)
- ART Station (S3 + N3 Bay)
- ART Station (S2 + WE2 EB Bay)
- ART Station (N1 + N2 Bay)
- ART Station (N4, N5 + S6 Bay)
- ART Station (W1, W2 + W6 Bay)
- ART Station (W5 + WE2 WB Bay)
- ART Station (S1 + S5 Bay)
- ART Station (S4 + WE1 WB Bay)
- Biltmore Ave at John Walker Ave
- River Ford Parkway at Verde Vista Apartments
- N Louisiana Ave at Emma Rd
- N Louisiana Ave at Emma Elementary School
- N Louisiana Ave at Mosswood Mobile Home Park
- Adams Hill Rd at Pearson Bridge Rd
- Bingham Rd at Adams Hill Rd
- Bingham Rd at Crossroad Ct
- Bingham Rd at Keith Dr
- Bingham Rd at Emma Rd
- Emma Rd at Emma Hill Dr
- Emma Rd at N Louisiana Ave
- N Louisiana Ave at Hazel Mill Rd
- N Louisiana Ave at Patton Ave
- Fairview Rd at The District
- Fairview Rd at Eastview Ave
- Fairview Rd at East St
- Fairview Rd at Ridge Ave
- Cedar St at Fairview Ave
- Fairview Rd at Unaka Ave
- Fairview Rd at Shannon Dr
- Fairview Rd at Harmony Ln
- Fairview Rd at Liberty St
- Fairview Rd at Old Fairview Rd
- Fairview Rd at I-240
- River Ridge Dr at River Ridge Shopping Center
- River Ridge Dr at J & S Cafeteria
- Fairview Rd at Oakley Plaza Shopping Center
- Fairview Rd at The District
- Wood Ave at River Hills Rd
- N Louisiana Ave at Arctic Rd
- Wood Ave at Future Dr
- Wood Ave at Cheerio Ln
- Cedar St at Fairview Rd
- Pearson Bridge Rd at Bingham Rd
- Fairview Rd at Harmony Ln
- Fairview Rd at Blalock Ave
- Fairview Rd at Third St
- Fairview Rd at East St
- Fairview Rd at Stoner Rd
- N Louisiana Ave at Patton Ave
- N Louisiana Ave at Hazel Mill Rd
- ART Station
- Broadway St at College St
- Broadway St at Walnut St
- Broadway St at Woodfin St
- Merrimon Ave at Marcellus St
- Merrimon Ave at E Chestnut St
- Merrimon Ave at Hillside St
- Merrimon Ave at Spears Ave
- Merrimon Ave at Coleman Ave
- W T Weaver Blvd at Merrimon Ave
- W T Weaver Blvd at King St
- W T Weaver Blvd at Barnard Ave
- UNC Asheville at Edgewood Rd
- UNC Asheville at Sherrill Center
- UNC Asheville at Governors Hall
- UNC Asheville at Zeis Hall
- W T Weaver Blvd at Barnard Ave
- W T Weaver Blvd at King St
- Merrimon Ave at Murdock Ave
- Merrimon Ave at Edgewood Rd
- Merrimon Ave at E Larchmont Rd
- Merrimon Ave at Gracelyn Rd
- Merrimon Ave at Ottari Rd
- Merrimon Ave at Beaverdam Rd
- Merrimon Ave at Beaver Point Park
- Merrimon Ave at Wembley Rd
- Merrimon Ave at Midland Dr
- Merrimon Ave at Stratford Rd
- Elkwood Ave at Merrimon Ave
- Elkwood Ave at N Ridge Dr
- Elkwood Ave at Valley Park Rd
- Lakeshore Dr at Cherry Ln
- Lakeshore Dr at Westwood Rd
- Lakeshore Dr at Glenview Rd
- Lakeshore Dr at Pine Tree Cir
- Lakeshore Dr at Mt Vernon Pl
- Lakeshore Dr at Merrimon Ave
- Merrimon Ave at Colonial Pl
- Merrimon Ave at Larchmont Rd
- Merrimon Ave at Edgewood Rd
- Merrimon Ave at Coleman Ave
- Merrimon Ave at Spears Ave
- Merrimon Ave at Hillside St
- Merrimon Ave at E Chestnut St
- Merrimon Ave at Whole Foods
- Broadway St at Woodfin St
- Broadway St at Walnut St
- Beaverdam Rd at Merrimon Ave
- Beaverdam Rd at Kimberly Ave
- Beaverdam Rd at Elk Mountain Scenic Hwy
- Beaverdam Rd at Timber Trail
- Beaverdam Rd at Sycamore St
- Beaverdam Rd at Carter Cove Rd
- Beaverdam Rd at Wolfe Cove Rd
- Centre Park Dr at Social Security Administration
- Valley Rd at Complete Care
- Beaverdam Rd at Valley Rd
- Beaverdam Rd at Faircrest Rd
- Beaverdam Rd at Carter Cove Rd
- Beaverdam Rd at Wild Cherry Rd
- Beaverdam Rd at Killian Rd
- Beaverdam Rd at Elk Mountain Scenic Hwy
- Beaverdam Rd at Kimberly Ave
- Merrimon Ave at Beaverdam Rd
- Merrimon Ave at Lakeshore Rd
- Patton Ave at Otis St
- Patton Ave at Clingman Ave
- Montford Ave at Haywood St
- Hill St at Montford Ave
- Hill St at Isaac Dickson Elementary
- Hill St at Cross Pl
- Atkinson St at Hill St
- Atkinson St at Community Center
- Atkinson St at Building 24
- Atkinson St at Building 1
- Atkinson St at Hill St
- Hill St at Cross Pl
- Hill St at Isaac Dickson Elementary
- Hill St at Montford Ave
- Patton Ave at Clingman Ave
- Patton Ave at S French Broad Ave
- Patton Ave at Otis St
- Patton Ave at Haywood St
- College St at Court Plaza
- College St at S Charlotte St
- College St at Martin Luther King Jr Dr
- Tunnel Rd at College St
- Tunnel Rd at Ingles
- Tunnel Rd at Chunns Cove Rd
- Tunnel Rd at I-240
- Tunnel Rd at Kenilworth Rd
- Tunnel Rd at White Pine Dr
- S Tunnel Rd at Asheville Mall
- S Tunnel Rd at Best Buy
- S Tunnel Rd at Lowes
- Swannanoa River Rd at S Tunnel Rd
- Swannanoa River Rd at U-Haul
- Bleachery Blvd at WalMart / Kohls
- Swannanoa River Rd at Bleachery Blvd
- Swannanoa River Rd at Fairway Dr
- Swannanoa River Rd at Fairview Rd
- Swannanoa River Rd at Manna Food Bank
- Swannanoa River Rd at Kensington Dr
- Swannanoa River Rd at Azalea Rd E
- Swannanoa River Rd at E Hawthorne Dr
- Tunnel Rd at Swannanoa River Rd
- Tunnel Rd at Riceville Rd
- Veterans Affairs Medical Center at Tunnel Rd
- Tunnel Rd at Riceville Rd
- Swannanoa River Rd at Tunnel Rd
- Swannanoa River Rd at Governors View Rd
- Swannanoa River Rd at Azalea Rd E
- Swannanoa River Rd at Kensington Dr
- Swannanoa River Rd at Fairview Rd
- Swannanoa River Rd at Fairway Dr
- Tunnel Rd at Oteen Church Rd
- Swannanoa River Rd at Bleachery Blvd
- Swannanoa River Rd at Beechwood Rd
- Swannanoa River Rd at S Tunnel Rd
- S Tunnel Rd at Swannanoa River Rd
- S Tunnel Rd at Overlook Village
- S Tunnel Rd at Asheville Mall
- Tunnel Rd at White Pine Dr
- Tunnel Rd at Kenilworth Rd
- Tunnel Rd at I-240
- Tunnel Rd at Chunns Cove Rd
- Tunnel Rd at Ingles
- College St at Town Mountain Rd
- College St at Oak St
- College St at Court Plaza
- College St at Broadway St
- Tunnel Rd at Crockett Ave
- Tunnel Rd at Overbrook Rd
- Tunnel Rd at Arco Rd
- Tunnel Rd at Governors View Rd
- Beverly Rd at Tunnel Rd
- Beverly Rd at Avon Rd
- Beverly Rd at New Haw Creek Rd
- New Haw Creek Rd at Bethesda Rd
- New Haw Creek Rd at Bell Rd
- Old Haw Creek Rd at Willowbrook Rd
- Old Haw Creek Rd at Pressley Rd
- Old Haw Creek Rd at Greenbriar Rd
- Old Haw Creek Rd at Dillingham Rd
- Old Haw Creek Rd at Spruce Hill Ln
- Waters Rd at Old Haw Creek Rd
- Middlebrook Rd at New Haw Creek Rd
- New Haw Creek Rd at Crockett Ave
- New Haw Creek Rd at Arco Rd
- New Haw Creek Rd at Beverly Rd
- Beverly Rd at Tunnel Rd
- Tunnel Rd at Maple Springs Rd
- Tunnel Rd at Pleasant Ridge Rd
- Tunnel Rd at Reddick Rd
- Tunnel Rd at E Azalea Rd
- US 70 East at ABCCM
- US 70 East at Porters Cove Rd
- US 70 West at Moffitt Branch Rd
- US 70 West at ABCCM
- Tunnel Rd at Lower Grassy Branch Rd
- Tunnel Rd at Arnold Rd
- Tunnel Rd at Oteen Church Rd
- Tunnel Rd at Swannanoa River Rd
- Tunnel Rd at Maple Springs Rd
- and 427 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 68.2 | first check |
| 2026-07-30 | 68.2 | no change |
| 2026-07-31 | 68.2 | no change |
| 2026-08-01 | 68.2 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
- Realtime quality no change
What changed in this feed
Overall grade and score held steady since 2026-07-31.
Same feed file as 2026-07-31; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
Everything we checked
10 findings, ordered by severity.
Show every finding
- Error1 instance
The service alerts realtime feed failed during sampling.
When this feed is down, riders see scheduled times presented as if they were live.
Fix: Check the service alerts endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. (Usually a vendor support ticket.)
Finding code: scorecard_rt_service_alerts_unreachable · Read the fix guide · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)
- Warning668 instances
668 of 677 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.
Fix: Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. (A column in stops.txt; your scheduling software likely has it.)
Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning30 instances
Some stops exist in the feed but no trip ever stops at them.
Riders may walk to a stop where no bus is scheduled to arrive.
Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)
Finding code: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some values have extra spaces at the start or end.
A stray space can break a match, so a stop or route may fail to link across files.
Fix: Trim leading and trailing spaces on export. The scorecard's auto-fixed copy already does this. (Usually one export setting.)
Finding code: leading_or_trailing_whitespaces · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Same stop and agency url (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'same_stop_and_agency_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: same_stop_and_agency_url · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
This feed describes flexible (demand-responsive) service but has no booking_rules.txt.
Riders can see the service area but not how or when to reserve a trip, so they can't actually use the service.
Fix: Add booking_rules.txt saying how far ahead and how to book (phone, app, or web). (A small file; one rule often covers the whole service.)
Finding code: scorecard_flex_no_booking_rules · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning1 instance
This feed models stations or entrances but has no pathways.txt.
Trip planners can't guide riders through the station, and there is no step-free route information for wheelchair users.
Fix: Add pathways.txt connecting entrances, platforms, and any elevators, with a level for each. (Worth it for multi-level or large stations; flat stops don't need it.)
Finding code: scorecard_station_no_pathways · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Info34 instances
Some files contain columns that are not part of the GTFS spec.
Harmless to riders, but apps ignore these columns and they can hide typos in real column names.
Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)
Finding code: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info8 instances
The feed includes a file that is not part of the GTFS spec.
Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.
Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)
Finding code: unknown_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info3 instances
Some service dates fall outside the date window set in feed_info.txt.
feed_info.txt should span every day your service runs, so apps know when the data applies.
Fix: Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside. (Two fields in feed_info.txt, or one export setting.)
Finding code: service_window_outside_feed_period · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Beyond the grade
Opportunities that do not change your grade today: fare detail, on-demand service, and deeper accessibility data.
Flex zones are published but no booking_rules.txt is present.
Consider: Add booking_rules.txt with how far ahead and how to reserve (phone, app, or web).
NTD GTFS readiness Ready
Published at a public URL, valid, current, and identified with agency_id: the four feed checks for RY2026 all hold here. Only your own D-10 and P-50 filings make 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 152 days.
- agency_id provided Ready
- agency.txt provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk each value on the P-50 form.
- agency_id equals your NTD ID (optional) Not checked yet
- This feed provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk it on the P-50 form. The value does not need to equal the five-digit NTD ID; we do not have that ID on file, so the optional equality comparison is not checked yet.
- shapes.txt covers your trips Ready
- All 1831 trips have a shape in shapes.txt.
In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed, provide a stable agency_id for each represented reporter, and confirm the feed and P-50 crosswalk each year. This box is a heads-up; your filings are the official check.
A readiness signal mapping this feed to the FTA National Transit Database GTFS requirement (Report Year 2023 onward: a public, valid, current feed, certified annually on the D-10). For RY2026, each represented reporter needs a stable agency_id, unique within the feed and crosswalked to its five-digit NTD ID on P-50; the values do not need to be equal. FTA also requires shapes.txt in the published GTFS: Full Reporters from Report Year 2025, and Reduced, Rural, and Tribal Reporters from Report Year 2026. Not an official determination; your certification is the official check.
Conformance mark Not yet
This feed is close to the conformance mark. States wheelchair access on 1% of stops and 100% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 152 days.
- Accessible Not yet
- States wheelchair access on 1% of stops and 100% of trips; the mark needs 90% of each.
In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.
A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 30 of 676 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.
These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.
Realtime reliability
The realtime feed responded on 0.0% of 200 checks over the last 34 days, with lag not reported by the feed.
Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.
Clears the Google and Apple Maps four-week coverage bar. This feed has 152 days of service ahead, clearing the four-week (28-day) window Maps asks for. No validator errors either, so riders keep seeing this agency in their trip planners; warnings lower the grade here but do not remove a feed from Maps.
How this agency maps to the standards
The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance, FTA National Transit Database GTFS requirement. Read the full standards crosswalk.
- Correctness 84 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading covers stop locations, route names, and colors. Google Transit requires a feed to pass validation for publication. FTA NTD readiness also checks that the published feed is valid.
- Freshness 100 / 100
- GTFS Schedule best practices call for a dataset that stays current. An expired calendar can remove service from Google Transit and other rider trip planners. FTA NTD readiness also checks that the published feed is current.
- Rider experience 75 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality 0 / 100
- GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.
Show your grade
Put a badge on your agency site or feed README. It updates after each completed scoring check and links back to this scorecard.
Prefer a shields.io style? Point a dynamic endpoint badge at the published badge.json.
Cite this record
This page updates on every check. The record below does not: it is the dated file this grade came from, published at https://gtfsscorecard.org/data/artifacts/asheville-rides-transit/2026-08-01.json and never overwritten, pinning the grade, category scores, rubric version, validator version, reader archive profile, and the scored feed's sha256 as they stood on 2026-08-01. Use it in a board packet, a regulatory filing, or a research citation instead of linking the live page, whose content will differ on your next visit.
Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.