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
Bristol Virginia Transit
Based on the feed this agency publishes
unchanged since 2026-07-08
Ahead of 92% of all tracked agencies and 90% of small agencies. Operates in Virginia.
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 16 minutes ago; last changed 8 hours 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
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
29 of 29 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
Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default).Likely your export tool
60 of 60 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).
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
Agencies here usually clear this within about 1 week (based on 11 observed fixes).
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.
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. 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.
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. 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.
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.
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.
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 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 4 kinds of issue across 50 instances (0 error, 7 warning, 43 informational).
Service data covers the next 207 days.
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 published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
Fares are applied to trips.
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.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- Falls/Walmart (gray)
- West Bristol (blue)
- East Bristol (red)
| Route | Type | Line color |
|---|---|---|
| Falls/Walmart | Bus | gray |
| West Bristol | Bus | blue |
| East Bristol | Bus | red |
This feed has 29 stops.
List every stop
- Food City (Euclid Ave & Bob Morrison Blvd)
- Leisure Park Towers (Piedmont Ave)
- Cabela Dr & Lee Hwy
- Food City-Bonham Rd
- Downtown Transfer Center
- Home Depot
- Walmart-Lee Hwy
- Price Less Food- Lee Hwy
- MLK Jr Blvd & W Mary St
- Dollar General-Plaza Dr & Lee Hwy
- McKinley Ave & King Mill Pike St
- Woodland Apartments on Avondale
- Kroger-Gate City Hwy
- Commonwealth Ave & Lawrence Ave
- E Valley Dr & Texas Ave
- DSS Office
- Wellmont Medical Associates/Ballad Health Family Medicine
- Ridgecrest Apartments
- Harbor Landing @ Dixie St
- Eastridge Apartments
- Hard Rock Hotel Employee Entrance
- Hard Rock Hotel Main Entrance
- Euclid Ave @ Hardee’s
- Euclid Ave @ Euclid Village
- Euclid Ave @ Grace Medical
- Oakview Ave & Hope Ln
- Lee Hwy @ Country Boy Market
- Oakview Ave & Clinton Ave
- Cumberland St & Waters Alley
Over time
Overall score across the last 20 checks — unchanged since 2026-07-08.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-06-19 | 76.9 | first check |
| 2026-06-20 | 76.5 | down 0.4 |
| 2026-06-21 | 76.1 | down 0.4 |
| 2026-06-22 | 75.7 | down 0.4 |
| 2026-06-23 | 75.2 | down 0.5 |
| 2026-06-24 | 74.8 | down 0.4 |
| 2026-06-25 | 74.4 | down 0.4 |
| 2026-06-26 | 74.0 | down 0.4 |
| 2026-06-27 | 73.6 | down 0.4 |
| 2026-06-28 | 73.2 | down 0.4 |
| 2026-06-29 | 72.8 | down 0.4 |
| 2026-06-30 | 72.3 | down 0.5 |
| 2026-07-01 | 71.9 | down 0.4 |
| 2026-07-02 | 71.5 | down 0.4 |
| 2026-07-04 | 70.7 | down 0.8 |
| 2026-07-05 | 70.2 | down 0.5 |
| 2026-07-06 | 69.8 | down 0.4 |
| 2026-07-07 | 69.4 | down 0.4 |
| 2026-07-08 | 84.0 | up 14.6 |
| 2026-07-09 | 84.0 | 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.
Same feed file as 2026-07-08; 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.
What changed over time
On 2026-06-19 this feed started at grade C. On 2026-07-06 the grade moved from C to D. On 2026-07-08 the grade moved from D to B. On 2026-07-02 feed entered the expiry window (30 days of service left). As of 2026-07-09 it holds grade B.
A plain-language history of this feed, newest first.
- 2026-07-08 Grade went D to B, freshness rose 58 points.
- 2026-07-06 Grade went C to D.
- 2026-07-02 Feed entered the expiry window (30 days of service left).
Everything we checked
- Warning60 instances
60 of 60 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)
- Warning29 instances
29 of 29 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)
- Warning7 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)
- 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.)
Validator rule: scorecard_flex_no_booking_rules · 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.)
Validator rule: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info8 instances
Unknown file (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unknown_file' 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: unknown_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
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)
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).
1 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (West Bristol).
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.
21 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Food City (Euclid Ave & Bob Morrison Blvd)", "Leisure Park Towers (Piedmont Ave)", "Cabela Dr & Lee Hwy", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
NTD certification readiness Ready
Published at a public URL, valid, and current: the three things the NTD GTFS requirement asks of a feed all hold here. Only your own D-10 certification makes 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 207 days.
- 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 60 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. 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 207 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.
- 7 of 29 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 207 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 92 / 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 100 / 100
- The FTA National Transit Database expectation of a valid, current feed. Google Transit: an expired calendar drops the agency from Maps.
- Rider experience 60 / 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.
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/bristol-virginia-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.
Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.