Feed status · checked 2026-11-21

Blacksburg Transit

Based on the feed source on file; publisher ownership is not verified

Service mode Bus

60.1 / 100

down 0.4 since 2026-11-20

Cataloged in Virginia.

Expires in 19 daysAccessibility gapsRealtime not yet published

The grade is not a count of validator errors. It also weighs freshness and rider information. How the grade works

Checked 2026-11-05: the http download from www.bt4uclassic.org was cut off mid-transfer, so runs scored an expired Mobility Database copy. Over https the same path serves the current feed (Last-Modified 2026-11-02, service through 2026-12-30).

Top things to fix

Fix 01

Correct feed_end_date in feed_info.txt. Set it to 2026-12-30, the last day in your calendar, or to the last day your schedule is reliable.Likely your export tool

feed_info.txt says this feed ends on 2026-12-10. Your service calendar runs to 2026-12-30. The GTFS standard tells apps to trust a feed only up to its end date. So apps may stop showing your service on the earlier date, even though the calendar goes on.

This one is about the feed as a whole, so there is no share of it to count.

⏱ One field in feed_info.txt, often an export setting.worth about +61 points in its category

Fix 02

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

297 of 297 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.

Fixing this covers all 297 stops in the feed.

⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category

Fix 03

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

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

Fixing this covers all 3,844 trips in the feed.

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

Riders and need behind these fixes

  • This feed carries no National Transit Database ID, so annual rider-trips are not known for it.
  • Virginia as a whole measures lower on transit need. That is a statewide reading, not one for this feed's service area. Source: US Census ACS 5-year 2022, statewide overlay, as of 2026-11-02.

These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.

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.

Finding
Fix 01 in Top things to fix: its feed evidence and the requested change.
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. Fix 01 · Read the fix guide for scorecard_feed_end_date_before_calendar

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    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. See this feed's finding-clearance log.

  2. Fix 02 · Read the fix guide for scorecard_wheelchair_boarding_unknown

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    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. See this feed's finding-clearance log.

  3. Fix 03 · Read the fix guide for scorecard_wheelchair_accessible_unknown

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    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. See this feed's finding-clearance log.

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 19 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 your vendor a fix request

You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.

Send the agency a note

Supporting this agency? Copy this and email it to them. It names what lapsed, why it matters to riders, and the one setting to change.

About this feed

Looking for times or routes? This page checks the data file that trip planners use. For schedules, use the agency's own website or a trip planner.

Blacksburg Transit’s published feed lists 24 bus routes, 3,844 scheduled trips and 297 stops. Its service dates run from 2026-11-13 through 2026-12-10. The published file last changed on 2026-11-16.

Score by category

Correctness87.5 / 100

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

Freshness31.7 / 100

Your feed_info end date, 2026-12-10, is earlier than your service calendar, which runs to 2026-12-30. The feed is read as ending on that earlier date, in 19 day(s).

Rider experience44.5 / 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

  • 7 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (CRB, PRG, CRC, PHB, HWC, and more).

    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.

  • 208 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("West Campus/Grove Sbnd", "Main/Collegiate Ct Sbnd", "Main/Faculty Sbnd", 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 297 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.

  • BLU (blue)
  • BMR (pink)
  • CAS (black)
  • CRB (red)
  • CRC (green)
  • GRN (brown)
  • HDG (brown)
  • HWA (teal)
  • HWB (teal)
  • HWC (purple)
  • HXP (teal)
  • HXS (teal)
  • NMG (red)
  • PHB (green)
  • PHD (pink)
  • PRG (purple)
  • SMA (brown)
  • SME (teal)
  • SMS (teal)
  • TCP (orange)
  • TCR (orange)
  • TTH (red)
  • TTS (orange)
  • UCB (brown)
Routes in Blacksburg Transit's feed
RouteTypeLine color
BLU Explorer BlueBusblue
BMR Beamer WayBuspink
CAS Campus ShuttleBusblack
CRB Carpenter BoulevardBusred
CRC Corporate Research CenterBusgreen
GRN Explorer GreenBusbrown
HDG Harding AvenueBusbrown
HWA Hethwood ABusteal
HWB Hethwood BBusteal
HWC Hethwood CombinedBuspurple
HXP Hokie ExpressBusteal
HXS Hokie Express StangerBusteal
NMG North Main GivensBusred
PHB Patrick Henry BBusgreen
PHD Patrick Henry DriveBuspink
PRG Progress StreetBuspurple
SMA South Main AirportBusbrown
SME South Main EllettBusteal
SMS South Main SouthparkBusteal
TCP Toms Creek ProgressBusorange
TCR Toms Creek RoadBusorange
TTH Two Town Trolley HospitalBusred
TTS Two Town Trolley Spradlin FarmsBusorange
UCB University City BlvdBusbrown
List every stop
  • Newman Library
  • Old Security Bldg
  • Kelly Hall
  • Torgersen Hall
  • Wright House
  • Litton Reaves Hall
  • Overflow Lot Wbnd
  • Oak Lane North
  • Oak Lane South
  • Overflow Lot Ebnd
  • I Lot/Cage Sbnd
  • Food Science Bldg
  • McComas Hall
  • Cassell Coliseum
  • Tennis Courts
  • Harper Hall
  • Softball Field
  • Lot 1 at Beamer Way
  • Oak Lane Nbnd
  • Bioinfomatics Bldg
  • Life Sciences 1 Bldg
  • Duck Pond/Smithfield Sbnd
  • McBryde Hall
  • East Eggleston Hall
  • Vawter Hall
  • Miles Hall
  • Pritchard Hall
  • Student Services Building
  • Price Hall
  • Hahn Hall
  • CID LLC
  • West Campus/Grove Sbnd
  • Lane Stadium at Sterrett
  • Lane Stadium
  • English Field
  • Vet Med
  • Duck Pond/Smithfield Nbnd
  • Prices Fork/Old Glade Wbnd
  • 1410 Prices Fork Rd
  • Prices Fork/Plantation Wbnd
  • Prices Fork/Huntington Wbnd
  • Hethwood Square on Hethwood
  • Tall Oaks/Hethwood Ebnd
  • Tall Oaks/Foxhunt Ebnd
  • Tall Oaks/Heather Ebnd
  • Tall Oaks/Foxtrail Sbnd
  • Stroubles Cr
  • Tall Oaks/Copper Croft Nbnd
  • Heather/Tall Oaks Nbnd
  • Heather/Plymouth Nbnd
  • Heather/Huntington Nbnd
  • Prices Fork/Huntington Ebnd
  • Prices Fork/Plantation Ebnd
  • Prices Fork/Old Glade Ebnd
  • Heather/Plymouth Sbnd
  • Carpenter Blvd/Redd Circle
  • Tall Oaks/Colonial Sbnd
  • Toms Creek/Winston Nbnd
  • Gilbert Linkous Nbnd
  • Toms Creek/Watson Nbnd
  • Toms Creek/McBryde Nbnd
  • Broce/Toms Creek Ebnd
  • Progress/Broce Nbnd
  • Progress/University Terr Nbnd
  • Progress/Patrick Henry Nbnd
  • 1575 Patrick Henry Wbnd
  • Patrick Henry/Toms Creek Wbnd
  • University City/Toms Creek Wbnd
  • Shawnee on University City Wbnd
  • Shawnee on University City Sbnd
  • University City/Broce Sbnd
  • University City/Glade Sbnd
  • University Mall Sbnd
  • University Mall Nbnd
  • University City/Broce Nbnd
  • Shawnee on University City Nbnd
  • Shawnee on University City Ebnd
  • University City/Toms Creek Ebnd
  • Patrick Henry/Toms Creek Ebnd
  • 1575 Patrick Henry Ebnd
  • Patrick Henry/Progress Ebnd
  • Progress/Hunt Club Sbnd
  • Progress/University Terr Sbnd
  • Progress/Broce Sbnd
  • Toms Creek/McBryde Sbnd
  • Toms Creek/Watson Sbnd
  • Gilbert Linkous Sbnd
  • Toms Creek/Hunt Club Nbnd
  • Toms Creek/Hunt Club Sbnd
  • Progress/Watson Nbnd
  • Progress/Watson Sbnd
  • Main/Progress Nbnd
  • Main/Montgomery Nbnd
  • Lucas/Main Ebnd
  • Lucas/Giles Ebnd
  • Giles/Northview Nbnd
  • Giles/Heights Nbnd
  • Giles/Patrick Henry Nbnd
  • Patrick Henry/Giles Wbnd
  • Patrick Henry/Main Wbnd
  • 1500 North Main Nbnd
  • Main/Giles Nbnd
  • Main/Red Maple Nbnd
  • Givens/Main Wbnd
  • Whipple/Givens Sbnd
  • Seneca Circle
  • Seneca/Patrick Henry Sbnd
  • Main/Patrick Henry Sbnd
  • 1200 North Main Sbnd
  • Main/Northview Sbnd
  • Main/Lucas Sbnd
  • Main/Montgomery Sbnd
  • Main/Collegiate Ct Sbnd
  • Main/Lucas Nbnd
  • Main/Northview Nbnd
  • 1200 North Main Nbnd
  • Main/Patrick Henry Nbnd
  • Whipple/Courtney Sbnd
  • 1500 North Main Sbnd
  • Main/Turner Nbnd
  • Patrick Henry/Mary Jane Ebnd
  • Patrick Henry/Seneca Ebnd
  • Whipple/Main Sbnd
  • Givens/Whipple Ebnd
  • Givens/Yale Ebnd
  • Patrick Henry/Mary Jane Wbnd
  • Main/Givens Nbnd
  • Main/Faculty Sbnd
  • Main/Faculty Nbnd
  • Roanoke/Church Ebnd
  • Roanoke/Wharton Ebnd
  • Roanoke/Rutledge Ebnd
  • Roanoke/Woolwine Ebnd
  • Harding/Silverleaf Ebnd
  • Harding/Patrick Henry Ebnd
  • Harding/Apperson Ebnd
  • Harding/Vista Ebnd
  • Harding/Roanoke Ebnd
  • Ascot/Harding Ebnd
  • Ascot/Hampton
  • Ascot/Harding Wbnd
  • Harding/Rucker Wbnd
  • Harding/Sutton Wbnd
  • Harding/Apperson Wbnd
  • Harding/Silverleaf Wbnd
  • Roanoke/Woolwine Wbnd
  • Roanoke/Rutledge Wbnd
  • Roanoke/Wharton Wbnd
  • Roanoke/Penn Wbnd
  • Main/Roanoke Sbnd
  • Blacksburg Municipal Building
  • Main/Eakin Sbnd
  • Main/Airport Sbnd
  • Main/Faystone Sbnd
  • Gables Shopping Center
  • Main/Landsdowne Sbnd
  • Fairfax/Ellett Ebnd
  • Fairfax/New Kent Ebnd
  • New Kent/Loudon Ebnd
  • New Kent/Sussex Ebnd
  • Grissom/Nellies Cave Nbnd
  • Marlington/Grissom Wbnd
  • Marlington/Emerald Wbnd
  • Marlington/Grayland Wbnd
  • Main/Landsdowne Nbnd
  • Main/Ardmore Nbnd
  • Blacksburg Square
  • Main/Cohee Nbnd
  • Main/Sunset Nbnd
  • Main/Graves Nbnd
  • Main/Hemlock Nbnd
  • Main/Eakin Nbnd
  • Main/Clay Nbnd
  • Main St Post Office
  • Main/Hemlock Sbnd
  • Industrial Park/Transportation Res Ebnd
  • Prosperity/Industrial Park Nbnd
  • Professional Park Nbnd
  • Main/Cedar Pointe Nbnd
  • Main/S Hill Nbnd
  • Fairfax Circle
  • Main/S Hill Sbnd
  • Main/Cedar Pointe Sbnd
  • Main/South Park Sbnd
  • Main/King Sbnd
  • Blacksburg Transit
  • Commerce/Industrial Park Sbnd
  • Industrial Park/Prosperity Wbnd
  • Country Club/Main Wbnd
  • Country Club/Draper Wbnd
  • Country Club/Airport Wbnd
  • Airport/Fairview Sbnd
  • Hubbard/Kennedy Ebnd
  • Professional Park/Southpark Ebnd
  • Pratt Dr/Garvin Bldg Sbnd
  • Pratt/Kraft Ebnd
  • Airport
  • Pratt Dr/Andrews Bldg Sbnd
  • Kraft/Tech Center Dr Sbnd
  • Pratt/Kraft Wbnd
  • Pratt/Garvin Bldg Nbnd
  • Pratt/Andrews Bldg Nbnd
  • Research Ctr/Rimrock Sbnd
  • Research Ctr/Rimrock Nbnd
  • Research Ctr/N Knollwood Nbnd
  • Kraft/Moss Bldg Sbnd
  • Research Ctr/S Knollwood Nbnd
  • Beamer/Southgate Nbnd
  • Research Ctr/Innovation Nbnd
  • Innovation/Smoot Ebnd
  • Innovation/Smoot Wbnd
  • Chicken Hill/Southgate Sbnd
  • Smoot/Innovation Sbnd
  • Kraft/Pratt Nbnd
  • Kraft/Research Ctr Dr Nbnd
  • Research Ctr/Sheliah Sbnd
  • Research Ctr/S Knollwood Sbnd
  • Uptown Mall
  • NRV Theatre
  • Walmart
  • LewisGale Hospital Montgomery
  • Montgomery County Govt Center
  • Republic/Salem Nbnd
  • Depot/Cambria Wbnd
  • Aquatic Center
  • Depot/New Wbnd
  • Montgomery County Courthouse
  • Roanoke/Evans Ebnd
  • Recreation Center
  • Simmons/Hammes Nbnd
  • Exit 118 Park and Ride
  • Roanoke/Hungate Wbnd
  • Roanoke/East Wbnd
  • Roanoke/Craig Wbnd
  • Roanoke/Evans Wbnd
  • Christiansburg Town Hall
  • Roanoke/Roberts Ebnd
  • Radford/College Ebnd
  • Electric Way/Fisher St Wbnd
  • Simpson Rd/Village Ln Wbnd
  • Electric Way/Fisher St Ebnd
  • Lucas/Brown Ebnd
  • North Franklin/Church Nbnd
  • Montgomery/Cambria Ebnd
  • Cambria/Church Nbnd
  • Cambria/Progress Nbnd
  • Cambria/Tyler Nbnd
  • Central/Cambria Wbnd
  • Central/North Franklin Wbnd
  • North Franklin/Church Sbnd
  • and 47 more (see the full list on the map or in the GeoJSON)

Over time

Overall score across the last 13 checks — down 0.4 since 2026-11-20.

2026-11-09: 56.72026-11-10: 56.32026-11-11: 55.92026-11-12: 55.52026-11-13: 55.12026-11-14: 54.72026-11-15: 54.22026-11-16: 62.22026-11-17: 61.82026-11-18: 61.42026-11-19: 60.92026-11-20: 60.52026-11-21: 60.1
Show the numbers
Overall score by check, with the change from the previous check
CheckScoreChange
2026-11-0956.7 first check
2026-11-1056.3 down 0.4
2026-11-1155.9 down 0.4
2026-11-1255.5 down 0.4
2026-11-1355.1 down 0.4
2026-11-1454.7 down 0.4
2026-11-1554.2 down 0.5
2026-11-1662.2 up 8.0
2026-11-1761.8 down 0.4
2026-11-1861.4 down 0.4
2026-11-1960.9 down 0.5
2026-11-2060.5 down 0.4
2026-11-2160.1 down 0.4

What changed since your last check

  • Correctness no change
  • Freshness down 1.6
  • Rider experience no change

Feed history

Every check on record for this feed, grouped by the published file, newest first. A new file means the published zip changed. Grades from earlier rubric versions are shown with their rubric and are not comparable with today’s grade or the trend above.

Feed history by published file
CheckedPublished fileService dates throughGrade at the time
2026-11-16 to 2026-11-21 (6 checks)121d4a658f692026-12-10Current rubric: see the trend above
2026-11-09 to 2026-11-15 (7 checks)07fa2ba6c6f32026-11-20Current rubric: see the trend above
2026-10-02 to 2026-11-06 (35 checks)0bc49aabb9782026-07-31F, 52 under rubric 1.4, an earlier scoring contract; not comparable with today’s grade
2026-07-25 to 2026-10-01 (65 checks)0bc49aabb9782026-07-31F, 52 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-07-13 to 2026-07-24 (10 checks)0bc49aabb9782026-07-31F, 52 under rubric 1.2, an earlier scoring contract; not comparable with today’s grade
2026-06-19 to 2026-07-12 (24 checks)0bc49aabb9782026-07-31F, 56.1 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade

What changed over time

On 2026-11-09 this feed started at grade F. On 2026-11-16 the grade moved from F to D. As of 2026-11-21 it holds grade D.

A plain-language history of this feed, newest first.

  • 2026-11-16 Grade went F to D, freshness rose 32 points.

Everything we checked

9 findings, ordered by severity.

Show every finding
  • Warning3844 instances

    3844 of 3844 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 for scorecard_wheelchair_accessible_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)

  • Warning297 instances

    297 of 297 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 for scorecard_wheelchair_boarding_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)

  • Warning119 instances

    119 of 3844 trips have no headsign, the text that tells riders where the bus is going. A trip counts when it has trip_headsign or a stop_headsign at every stop.

    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 for scorecard_missing_headsigns · See GTFS Best Practices (opens GTFS Best Practices on an external site)

  • Warning1 instance

    This feed's service calendar runs out within the next 30 days.

    If a new feed isn't published before it ends, trip planners will drop your agency and riders will see no service.

    Fix: Schedule a feed re-export now so the new calendar is live well before the current one ends. (Usually a re-export from your scheduling software.)

    Finding code: feed_expiration_date30_days · Read the fix guide for feed_expiration_date30_days · 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.)

    Finding code: mixed_case_recommended_field · Read the fix guide for mixed_case_recommended_field · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning1 instance

    Same name and description for route (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'same_name_and_description_for_route' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Finding code: same_name_and_description_for_route · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning1 instance

    feed_info.txt says this feed ends on 2026-12-10. Your service calendar runs to 2026-12-30.

    The GTFS standard tells apps to trust a feed only up to its end date. So apps may stop showing your service on the earlier date, even though the calendar goes on.

    Fix: Correct feed_end_date in feed_info.txt. Set it to 2026-12-30, the last day in your calendar, or to the last day your schedule is reliable. (One field in feed_info.txt, often an export setting.)

    Finding code: scorecard_feed_end_date_before_calendar · Read the fix guide for scorecard_feed_end_date_before_calendar · See GTFS Schedule reference (opens the GTFS Schedule reference 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.)

    Finding code: scorecard_no_fare_data · Read the fix guide for scorecard_no_fare_data · See GTFS Best Practices (opens GTFS Best Practices on an external site)

  • Info2 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 for service_window_outside_feed_period · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

How we measured this

Checked for changes 18 hours ago; last changed 5 days ago.

Measured 3 of 4 score categories from the feed URL on file (publisher not verified).

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 configured feed URL. Publisher ownership of that URL is not verified.

Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.

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

NTD GTFS readiness Needs attention

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

Two requirements remain for this feed to earn the conformance mark. Service data runs out in 19 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 19 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.

At risk for the Google and Apple Maps four-week coverage bar. This feed has 18 days of service left. Maps needs at least four weeks (28 days) of upcoming service, so your agency will fall out of trip planners soon. Re-export with a longer calendar.

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 88 / 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 32 / 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 44 / 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.

Part of the Virginia portfolio: the same scorecards for every feed we track in that group, on one free page.

Similar feeds in Virginia

Other scorecards in Virginia, starting with the same kind of service at a similar size. Listed for comparison, not ranked.

Show your grade

Put this badge on your agency site or feed README. It updates after each completed scoring check, shows the date of that check, and links back to this scorecard. When there is no current score it says so instead of showing an old one.

Blacksburg Transit: GTFS feed quality grade D, 60.1 of 100, checked 2026-11-21. GTFS 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/blacksburg-transit/2026-11-21.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-11-21. 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.