GTFS Scorecard
← All agencies

Feed status · checked 2026-08-01

Radford Transit

Based on the feed this agency publishes

Service mode Bus

78.2 / 100

unchanged since 2026-07-31

Catalogued in Virginia.

Covers 184 daysAccessibility gapsFlexible serviceRealtime not yet published

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 9 hours ago; last changed 24 days 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

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

Fix 02

Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.Likely your export tool

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

⏱ A default or per-trip field in your export.worth about +15 points in its category

Fix 03

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.

⏱ A small file for most flat-fare systems.worth about +15 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
120 of 120 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
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.

  1. 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.

  2. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. · 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.

  3. 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. · 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 184 days.
Published accessibility data
Accessibility information is stated for 0% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
Fare information
No fare information is published in the feed.
Realtime information
Realtime-feed availability and live-arrival coverage are not known from this scorecard.

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

Correctness94.0 / 100

The MobilityData validator flagged 4 kinds of issue across 52 instances (0 error, 5 warning, 47 informational).

Freshness100.0 / 100

Service data covers the next 184 days.

Rider experience38.8 / 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.

2 accessibility depth signals

  • 5 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (40, 41, 50, 30, 40).

    Consider: Adjust route_color or route_text_color so each pair clears 4.5:1. Often switching the text between black and white is enough.

  • 73 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Wilson St/Davis St", "Wadsworth St/Sheppard Ave NB", "Wadsworth St/Roosevelt Ave NB", and more).

    Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.

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.

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.

This feed has 120 stops.

Skip to route and stop data

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.

  • 60 (teal)
  • 50 (teal)
  • 41 (purple)
  • 40 (purple)
  • 40 (purple)
  • 35 (green)
  • 30 (brown)
  • 25 (orange)
  • 20 (yellow)
  • 15 (yellow)
  • 11 (purple)
  • 10 (red)
  • 10 (red)
Routes in Radford Transit's feed
RouteTypeLine color
100 NRCCBusteal (no shape in feed)
60 South Beech ExpressBusteal
50 Highlander CircleBusteal
41 NRV ConnectBuspurple
40 NRV Connect Late NightBuspurple
40 NRV ConnectBuspurple
35 New River RapidBusgreen
30 New River RapidBusbrown
25 New River RapidBusorange
20 New River RapidBusyellow
15 University ExpressBusyellow
11 University ExpressBuspurple
10 University Express SundayBusred
10 University ExpressBusred
List every stop
  • Wilson St/Davis St
  • Willow Woods Apts Exit
  • Willow Woods Apts
  • Walmart
  • Walker Hall
  • Waldron Hall
  • Wadsworth St/Sheppard Ave NB
  • Wadsworth St/Roosevelt Ave NB
  • Wadsworth St/Heather Glen Dr NB
  • Wadsworth St/8th St NB
  • University Dr Bridge
  • Tyler Ave/Milton Ln
  • Tyler Ave/Auburn Ave
  • The HUB
  • Tall Oaks Crossing
  • Staples St/Rock Rd SB
  • Staples St/PT Travis Ave SB
  • Staples St/12th St SB
  • Squires Student Center
  • Riverbend Apts
  • Ridgewood Lane
  • Regal Cinemas
  • Rec Center
  • Randolph St/8th St NB
  • Randolph St/7th St
  • Quality Inn
  • Preston St/Lyle St SB
  • Preston St/7th St SB
  • Preston St/4th St SB
  • Preston St/12th St SB
  • Park Rd/Sundell Dr WB
  • NRV Mall
  • NRCC Dublin Campus
  • New River Dr
  • Muse Hall
  • Moffett Hall
  • Miller St Exit
  • Main St/Virginia St WB
  • Main St/Virginia St EB
  • Main St/Staples St EB
  • Main St/Robertson St EB
  • Main St/Randolph St EB
  • Main St/Public Library EB
  • Main St/Preston St EB
  • Main St/Madison St
  • Main St/Kent St WB
  • Main St/Denby St EB
  • Main St/CVS WB
  • Main St/Custis St EB
  • Main St/Cowan St EB
  • Main St/Carter St EB
  • Main St/Burlington St
  • Main St/Ardmore St NB
  • Lot CC/Shelter Sun
  • Lot A
  • Kyle Hall (COBE)
  • Kroger
  • Jeffries Dr
  • Jefferson and Main
  • Greenhill Apartments
  • Golden Bowl WB
  • Golden Bowl EB
  • George St (to Rec Center)
  • George St (Rec Center exit)
  • Fulk Dr
  • First and Main
  • Fairfax Station
  • Fairfax St/Wilson St
  • Draper Hall
  • Downtown Christiansburg EB
  • Deli Mart EB
  • Copper Beech
  • Clement St/Whitehall St
  • Chrstnsbrg Bnd Mllr St
  • CHBS
  • Calhoun St/Wilson St
  • Calhoun St/Madison St
  • Burlington St/Fairfax St
  • Burlington St/Clement St
  • Burlington Lot
  • Bburg Municipal Building
  • Auburn Ave/Villa Trailer Park
  • Auburn Ave/Tyler Ave
  • Armstrong
  • Allen Ave/Wadsworth St
  • 6th St/Scott St NB
  • 3rd Ave/Fairfax St NB
  • 3rd Ave/Downey St NB
  • 2nd St/Highland Ave
  • 2nd Ave/Lawrence St
  • Lot CC Stadium Gates
  • University Dr / Lot CC
  • Dedmon Center Upper
  • Dedmon Center Riverside
  • University Dr/Pulaski Ave
  • Lot FF
  • Greenhill Clubhouse
  • Food Lion Plaza
  • Aubum Ave/Cedar Ridge Dr
  • Main St. / Randolph St. WB
  • Wadsworth St/2nd St
  • Wadsworth St/6th St
  • 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
  • Radford Bnd Mllr St
  • Downtown Christiansburg WB
  • Dudley's Landing
  • Veterans Field
  • Shelter 1
  • Main St/Wirt St WB
  • Multi-Modal Transfer
  • Calhoun St
  • Lawrence St/2nd Ave
  • Miller St Entrance
  • Artis Shelter

Over time

Overall score across the last 4 checks — unchanged since 2026-07-31.

2026-07-25: 78.32026-07-30: 78.22026-07-31: 78.22026-08-01: 78.2
Show the numbers
CheckScoreChange
2026-07-2578.3 first check
2026-07-3078.2 down 0.1
2026-07-3178.2 no change
2026-08-0178.2 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-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

9 findings, ordered by severity.

Show every finding
  • Warning336 instances

    336 of 336 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. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. (A default or per-trip field in your export.)

    Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference

  • Warning136 instances

    136 of 336 trips lack rider-facing destination or direction text.

    When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.

    Fix: Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign. (Usually one value per route pattern in your scheduling source.)

    Finding code: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices

  • Warning120 instances

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

  • Warning5 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

  • 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.)

    Finding code: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices

  • 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

  • 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

  • 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

  • Info5 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

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 184 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 336 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 0% of stops and 0% of trips; the mark needs 90% of each.

Valid Met
Passes validation with no errors.
Current Met
Service data covers the next 184 days.
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.

  • 5 of 120 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 184 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 94 / 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 39 / 100
GTFS Best Practices for rider-facing fields. MobilityData grading covers 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 badge on your agency site or feed README. It updates after each completed scoring check and links back to this scorecard.

Radford Transit GTFS data quality grade: C

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-2415/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.