Prep for a call: printable one-page brief · For your board packet: printable one-pager · Fix log: every issue this feed has cleared · Compare with another agency · Watch this feed: get an email before it expires

Feed status · checked 2026-07-09

Radford Transit

Based on the feed this agency publishes

FDCBA

54.8 / 100

unchanged since 2026-07-08

Ahead of 44% of all tracked agencies and 41% of mid-size agencies. Operates in Virginia.

Covers 30 daysAccessibility gapsNo realtime feed

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.1, validator 8.0.1.

Checked for changes 13 minutes ago; last changed 13 minutes ago.

Measured 3 of 4 score categories from the agency's own feed.

How we measured this

Confidence in this measurement: medium.

Realtime quality was not measured this run. It does not count against the grade.
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

Fix 01

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

142 of 142 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

Fix 02

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

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

⏱ Often one default setting in your export.worth about +15 points

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

Fix 03

Populate trip_headsign to match what the bus displays.Likely your export tool

374 of 374 trips have no headsign. Riders at the stop can't tell which direction a bus is going.

⏱ Usually a bulk edit in your scheduling software.worth about +15 points

This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.

Close the loop on each fix. Read the guide, make the change in your tool, and let the next run verify it — the scorecard shows the fix; the agency publishes it.

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. This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. See this feed's dated fix log.
Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default). · Read the fix guide
Make the change. This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. See this feed's dated fix log.
Populate trip_headsign to match what the bus displays. · Read the fix guide
Make the change. This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. See this feed's dated fix log.

Send Passio a fix request

This feed is generated by your Passio system. Copy this and send it to your Passio contact; the fixes apply to the route and stop data behind your AVL setup. Each fix names the validator notice and a guide link.

Hi,

Our GTFS feed (Radford Transit) scored F (54.8 out of 100) on the GTFS Scorecard. Could you review these in our export settings:

1. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
   What: 142 of 142 stops don't say whether a wheelchair user can board there.
   Validator notice: scorecard_wheelchair_boarding_unknown
   Guide: https://gtfsscorecard.org/fix/scorecard_wheelchair_boarding_unknown/

2. Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default).
   What: 374 of 374 trips don't say whether the vehicle is wheelchair accessible.
   Validator notice: scorecard_wheelchair_accessible_unknown
   Guide: https://gtfsscorecard.org/fix/scorecard_wheelchair_accessible_unknown/

3. Populate trip_headsign to match what the bus displays.
   What: 374 of 374 trips have no headsign.
   Validator notice: scorecard_missing_headsigns
   Guide: https://gtfsscorecard.org/fix/scorecard_missing_headsigns/

Full scorecard: https://gtfsscorecard.org/agency/radford-transit/

Score by category

Correctness75.2 / 100

The MobilityData validator flagged 6 kinds of issue across 71 instances (0 error, 65 warning, 6 informational).

Freshness50.0 / 100

Service data covers the next 30 days.

Rider experience29.9 / 100

0% of stops state wheelchair accessibility (0% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.

Accessibility0 / 100

0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.

Realtime qualityNot yet measured

Not scored yet. Nothing here counts against the grade.

Routes and stops

Each route is drawn once, using the longest shape its trips follow; stops are the dots.

Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.

10 (red)
11 (purple)
15 (yellow)
20 (yellow)
25 (orange)
30 (brown)
35 (green)
40 LN (purple)
60 (teal)
Route 50 (teal)

Routes in Radford Transit's feed
Route	Type	Line color
10 Route 10	Bus	red
11 Route 11	Bus	purple
15 Route 15	Bus	yellow
20 Route 20	Bus	yellow
25 Route 25	Bus	orange
30 Route 30	Bus	brown
35 Route 35	Bus	green
40 Route 40	Bus	purple (no shape in feed)
40 LN Route 40 Late Night	Bus	purple
Route 41	Bus	purple (no shape in feed)
Route 41 Late Night	Bus	purple (no shape in feed)
100 Route NRCC	Bus	teal (no shape in feed)
60 Route 60	Bus	teal
Route 50	Bus	teal

This feed has 142 stops.

List every stop

Special Events Stop
Downtown Christiansburg EB
Downtown Christiansburg WB
Main St/Ardmore St NB
First and Main
Multi-Modal Transfer
Uptown CBurg Mall IB
Regal Cinemas IB
Artis
Veterans Field
Dudley's Landing
Shelter 1
Tall Oaks Crossing
Wadsworth St/2nd St
Wadsworth St/6th St
Quality Inn
Food City
NRCC Dublin Campus
Lot CC/Shelter Sun
Draper Hall
Jefferson and Main
Greenhill Apartments
New River Dr
Armstrong
Fairfax Station
Kyle Hall (COBE)
Moffett Hall
Walker Hall
Muse Hall
The HUB
CHBS
University Dr Bridge
University Dr/Lot CC
Dedmon Center Upper
Dedmon Center Riverside
University Dr/Pulaski Ave
Lot FF
Greenhill Clubhouse
Lot CC/Shelter
Lot CC/Stadium Gates
Main St/Madison St
Main St/Burlington St
Clement St/Whitehall St
Burlington Lot
Burlington St/Fairfax St
Fairfax St/Wilson St
Wilson St/Davis St
Calhoun St/Wilson St
Calhoun St/Madison St
Burlington St/Clement St
Walmart
Fulk Dr
Kroger
Main St/Public Library EB
Golden Bowl EB
Main St/Virginia St EB
Food Lion Plaza
Auburn Ave/Cedar Ridge Dr
Ridgewood Lane
Auburn Ave/Villa Trailer Park
Auburn Ave/Tyler Ave
Best Western
Tyler Ave/Auburn Ave
Tyler Ave/Milton Ln
Main St/Virginia St WB
Golden Bowl WB
Main St/CVS WB
Jeffries Dr
Riverbend Apts
2nd St/Highland Ave
Main St/Cowan St EB
Deli Mart EB
Main St/Custis St EB
Main St/Denby St EB
Main St/Carter St EB
Main St/Preston St EB
Main St/Staples St EB
Main St/Robertson St EB
Main St/Kent St EB
Main St/Randolph St EB
3rd Ave/Downey St SB
3rd Ave/Fairfax St SB
George St (to Rec Center)
Rec Center
George St (Rec Center exit)
Park Rd/Sundell Dr EB
6th St/Scott St SB
Randolph St/8th St SB
Wadsworth St/8th St SB
Wadsworth St/Roosevelt Ave SB
Wadsworth St/Sheppard Ave SB
Willow Woods Apts
Willow Woods Apts Exit
Allen Ave/Wadsworth St
Wadsworth St/Heather Glen Dr SB
Staples St/Rock Rd NB
Staples St/PT Travis Ave NB
Staples St/12th St NB
Preston St/12th St NB
Preston St/Lyle St NB
Preston St/7th St NB
Preston St/4th St NB
Preston St/Alley by Soc Serv
Main St/Carter St WB
Main St/Denby St WB
Main St/Custis St WB
Deli Mart WB
Main St/Cowan St WB
Jeffries Dr Midhill
Randolph St/7th St
2nd Ave/Lawrence St
Main St/Randolph St WB
Main St/Kent St WB
Main St/Robertson St WB
Main St/Wirt St WB
Preston St/4th St SB
Preston St/7th St SB
Preston St/Lyle St SB
Preston St/12th St SB
Staples St/12th St SB
Staples St/PT Travis Ave SB
Staples St/Rock Rd SB
Wadsworth St/Heather Glen Dr NB
Wadsworth St/Sheppard Ave NB
Wadsworth St/Roosevelt Ave NB
Wadsworth St/8th St NB
Randolph St/8th St NB
6th St/Scott St NB
Park Rd/Sundell Dr WB
3rd Ave/Fairfax St NB
3rd Ave/Downey St NB
Chrstnsbrg Bnd Mllr St
Squires Student Center
Bburg Municipal Building
Radford Bnd Mllr St
Regal Cinemas OB
Uptown CBurg Mall OB
Copper Beech
Miller St Exit
Calhoun St
Lawrence St/2nd Ave
Miller St Entrance

Over time

Overall score across the last 20 checks — unchanged since 2026-07-08.

Show the numbers

Overall score by check, with the change from the previous check
Check	Score	Change
2026-06-19	52.1	first check
2026-06-20	52.1	no change
2026-06-21	52.1	no change
2026-06-22	52.1	no change
2026-06-23	52.1	no change
2026-06-24	52.1	no change
2026-06-25	52.1	no change
2026-06-26	52.1	no change
2026-06-27	52.1	no change
2026-06-28	52.1	no change
2026-06-29	52.1	no change
2026-06-30	52.1	no change
2026-07-01	52.1	no change
2026-07-02	52.1	no change
2026-07-04	52.1	no change
2026-07-05	52.1	no change
2026-07-06	54.8	up 2.7
2026-07-07	54.8	no change
2026-07-08	54.8	no change
2026-07-09	54.8	no change

What changed since your last check

Correctness no change
Freshness no change
Rider experience no change

What changed in this feed

Overall grade and score held steady since 2026-07-08.

The feed file was re-published since 2026-07-08.

Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.

Everything we checked

Warning374 instances
374 of 374 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible stops, riders need to know the bus itself can take them.
Fix: Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default). (Often one default setting in your export.)
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
Warning374 instances
374 of 374 trips have no headsign.
Riders at the stop can't tell which direction a bus is going.
Fix: Populate trip_headsign to match what the bus displays. (Usually a bulk edit in your scheduling software.)
Validator rule: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
Warning142 instances
142 of 142 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.)
Validator rule: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
Warning50 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.)
Agencies here usually clear this within about 1 week (based on 11 observed fixes).
Validator rule: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning12 instances
Stop too far from shape using user distance (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'stop_too_far_from_shape_using_user_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 6 observed fixes).
Validator rule: stop_too_far_from_shape_using_user_distance · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning1 instance
Some service calendars in the feed have already ended.
Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)
Agencies here usually clear this within about 1 week (based on 61 observed fixes).
Validator rule: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning1 instance
Some rider-facing names are in ALL CAPS or all lowercase.
ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.
Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)
Validator rule: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning1 instance
Stops match shape out of order (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'stops_match_shape_out_of_order' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 6 observed fixes).
Validator rule: stops_match_shape_out_of_order · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning1 instance
The feed contains no fare information.
Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
Fix: 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. (A small file for most flat-fare systems.)
Validator rule: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
Info6 instances
Service window outside feed period (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'service_window_outside_feed_period' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 17 observed fixes).
Validator rule: service_window_outside_feed_period · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

Some fixes we can make for you

These are the safe mechanical fixes, applied to a copy of your feed. They change only what is certain and leave everything else untouched. Review the diff before you publish.

Recased shouting stop names 1 change
For example: CHBS -> Chbs

Run it yourself on your own copy of the feed: scorecard autofix <feed.zip> --out corrected.zip

NTD certification readiness Needs attention

This feed is close to NTD-ready. Service data runs out in 30 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 30 days; renew before you certify.

agency_id matches your 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.

shapes.txt covers your trips Ready: All 374 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 and confirm it once a year. This box is a heads-up on whether yours looks ready; it is not the official sign-off.

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). Aligning agency_id with your NTD ID lets the feed line up with your NTD record; the July 2025 final rule links the two on the P-50 form rather than requiring that feed change, and 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. Service data runs out in 30 days; renew to qualify. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.

Valid Met: Passes validation with no errors.
Current Not yet: Service data runs out in 30 days; renew to qualify.
Accessible Not yet: States wheelchair access on 0% of stops and 0% 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.

50 of 142 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.

Clears the Google and Apple Maps four-week coverage bar. This feed has 540 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

A data-quality lens, not a compliance determination. Each category shows this feed's score and the standards it relates to: the FTA National Transit Database GTFS requirement, the MobilityData grading scheme, and the Google Transit gate. Read the full standards crosswalk.

Correctness 75 / 100: GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading: stop locations, route names and colors. Google Transit: a feed must pass validation to stay in Maps.
Freshness 50 / 100: The FTA National Transit Database expectation of a valid, current feed. Google Transit: an expired calendar drops the agency from Maps.
Rider experience 30 / 100: GTFS Best Practices for rider-facing fields. MobilityData grading: stop names and headsigns.
Realtime quality Not yet published: GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.

Show your grade

Put a live badge on your agency site or feed README. It updates daily and links back to this scorecard.

[![Radford Transit GTFS data quality grade: F](https://gtfsscorecard.org/data/artifacts/radford-transit/badge.svg)](https://gtfsscorecard.org/agency/radford-transit/)

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/radford-transit/2026-07-09.json and never overwritten, pinning the grade, category scores, rubric version, validator version, and the scored feed's sha256 as they stood on 2026-07-09. Use it in a board packet, an NTD narrative, or a research citation instead of linking the live page, whose content will differ on your next visit.

GTFS Scorecard. (2026). Radford Transit GTFS feed-quality record, dated 2026-07-09 (grade F (54.8/100), rubric v1.1, gtfs-validator 8.0.1, feed sha256 abe014fcb75f…). https://gtfsscorecard.org/data/artifacts/radford-transit/2026-07-09.json

@misc{gtfsscorecard-radford-transit-2026-07-09,
  title        = {Radford Transit GTFS feed-quality record},
  author       = {GTFS Scorecard},
  year         = {2026},
  howpublished = {\url{https://gtfsscorecard.org/data/artifacts/radford-transit/2026-07-09.json}},
  note         = {Checked 2026-07-09; rubric v1.1; gtfs-validator 8.0.1; grade F (54.8/100)}
}

Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.