← All agencies

Feed status · checked 2026-08-01

Virginia Regional Transit Flex

Based on the feed this agency publishes

Service mode Bus

66.4 / 100

down 0.4 since 2026-07-31

Catalogued in Virginia.

Covers 31 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 1 days ago; last changed 9 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

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

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

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
251 of 251 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. 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 31 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
Fare information is published using GTFS Fares v1.
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

Correctness81.8 / 100

The MobilityData validator flagged 6 kinds of issue across 93 instances (0 error, 55 warning, 38 informational).

Freshness51.7 / 100

Service data covers the next 31 days.

Rider experience56.7 / 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 published.

Accessibility0 / 100

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

2 accessibility depth signals

  • 3 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (ShenGO, Front Royal Trolley, Circuit Rider Gray).

    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.

  • 70 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Main St. Phamacy", "Newton & Montevista Ave", "CVS-Radney Rd", 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.

FaresLegacy fares

Fares are applied to trips.

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

  • Town of Orange Trolley (yellow)
  • Orange/Culpeper Connector (yellow)
  • Circuit Rider Blue-Green (blue)
  • Circuit Rider Gray (gray)
  • Purcellville Connector (pink)
  • Culpeper Trolley (red)
  • Foothills Express (teal)
  • Front Royal Trolley (red)
  • Corridor Connector (green)
  • Culpeper Express (green)
  • ShenGO (green)
Routes in Virginia Regional Transit Flex's feed
RouteTypeLine color
Town of Orange TrolleyBusyellow
Orange/Culpeper ConnectorBusyellow
Circuit Rider Blue-GreenBusblue
Circuit Rider GrayBusgray
Purcellville ConnectorBuspink
Culpeper TrolleyBusred
Foothills ExpressBusteal
Front Royal TrolleyBusred
Corridor ConnectorBusgreen
Loudoun On-DemandBusgreen (no shape in feed)
Culpeper On-DemandBusgreen (no shape in feed)
Fauquier On-DemandBusgreen (no shape in feed)
Clarke On-DemandBusgreen (no shape in feed)
Culpeper ExpressBusgreen
ShenGOBusgreen
List every stop
  • Main St. Phamacy
  • Newton & Montevista Ave
  • Bellview Senior Apartments
  • Maple Ridge Apartments
  • Heritage Hills
  • Oakbrook Terrace Apartments
  • Dogwood Village
  • CVS-Radney Rd
  • UVA Physicians
  • Orange Park & Ride
  • Washington Street
  • Colonial Square Shopping Center
  • Twyman Street
  • W Main St & Caroline St
  • E Main St & N Madison Rd
  • Jefferson St & S. Madison Rd
  • Selma Rd. & Jefferson St.
  • Orange Depot
  • Round Hill Apartments
  • East Gate Apts Gordonsville
  • Depot Street Gordonsville
  • Cobb St. Gordonsville
  • Gordonsville Town Hall
  • East St. Gordonsville
  • Orange Village Shopping Ctr
  • Carver Agricultural Research Center
  • Culpeper Hospital
  • Falmouth/Aviary
  • Walmart-Warrenton
  • Warrenton Community Center
  • Fauqier Family Shelter
  • Post Office
  • Leeds Square
  • Falmouth/Taylor
  • Fauquier Food Bank & Thrift Store
  • Moffett Manor Apartments
  • Fauquier Health Hospital S. Entrance
  • Town Center
  • Haiti St.
  • Oak Springs Plaza Giant Food
  • Village Center Safeway
  • The Oaks Apartments
  • Warrenton Manor Apartments
  • Warrenton Center/Joann Fabrics
  • Plaza Shopping Center Salon
  • Subway
  • Warrenton Middle School
  • Holiday Ct & Medical Center
  • 5th and Main
  • Hub-Keith St
  • Free Clinic & Medical Ctr
  • Piedmont Medical Center
  • N Rock Shopping Center
  • Jackson Street Apts
  • Laurel Ridge Community College
  • Fauquier High School
  • Warrenton Aquatic & Recreation Center
  • Purcellville Park & Ride
  • Loudoun Valley Community Center
  • Giant Food Purcellville
  • Harmony Church-Hamilton
  • Across from Post Office-Hamilton
  • Loudoun County Government Center
  • Patrick Henry College
  • Maple Avenue Apartments
  • Culpeper United Methodist Church
  • Powell Wellness
  • Microtel-Culpeper
  • Fauquier Social Services
  • Piedmont St & Commerce St
  • Weis Markets-Culpeper Town Square
  • Popeye's-James Madison Hwy
  • Walmart-Culpeper
  • Target-Culpeper
  • Lowe's-Culpeper
  • Dominion Square
  • Belle Ave
  • Commons Apartments
  • Belle Ave & Hitt Ct
  • Carter Bank
  • Sycamore St & N Main St- 7/11
  • Wendy's-Colonel Jameson Blvd
  • Mountain Run Apartments
  • Yowell Meadow Park
  • W Davis St & N Main St
  • Commerce St
  • 7-Eleven
  • KFC-Main St between Oak View and Elm
  • Friendship Heights Apartments
  • Red Roof Inn-Culpeper
  • DaVita Dialysis
  • Mountain View Apartments
  • Weis Market/Meadowbrook
  • Safeway/Southgate
  • Leaflin Lane
  • Culpeper DHS
  • Kids Central
  • UVA Imaging
  • Culpeper Station
  • Madison - Food Lion
  • Ruckersville - Walmart
  • Charlottesville Station
  • UVA Hospital
  • UVA Fountaine Center
  • Charlottesville City Bus Hub
  • Front Royal Visitors Center
  • Skate Park
  • Kerfoot Ave & Brown Ave
  • Northwest Community Services
  • Samuels Public Library/Royal Arms Apartments
  • Royal Plaza/Rural King (Martin's)
  • South St / Pine St
  • S Royal Ave & S Laurel St
  • Warren County District Court
  • Gateway Plaza
  • RSW Regional Jail
  • Family Dollar Distribution
  • Weston Foods
  • Shadows Dr & Hospitality Dr
  • Valley Health
  • Warren Co Gov't Center
  • Parks Dept/Youth Center
  • Senior Center
  • Warren Memorial Hospital
  • Family Store
  • Skyline Vista Apartments
  • Warren County Community Center
  • Randolph Macon Academy
  • Rockland Road / Axalta
  • Skyline High School
  • Warren County High School
  • Laurel Ridge Community College - Middletown
  • Warren County Health Department
  • Valley Health Urgent Care
  • Front Royal Walmart
  • Front Royal Target
  • Appalachian Trail Crossing
  • 16th St Bus Shelter
  • Subway - Front Royal
  • Royal Theater
  • Bowling Alley
  • Royal Theater
  • Front Royal Visitors Center
  • Walgreens - Culpeper
  • 7 Eleven (E Main St)
  • Love Outreach Food Pantry
  • Byrd St & Jefferson St
  • W. Main & Peliso Ave WB
  • Central Virginia Regional Jail
  • W. Main & Peliso Ave SB
  • Lindsay Dr Apts
  • Comfort Inn & Suites
  • Orange Family Physicians
  • Journey Church
  • DMV Select
  • W Main St & Caroline St
  • Dominos on N. Madison
  • Iron Pipe Alewerks
  • Roses
  • Round Hill Inn
  • Spicers Mill Apts
  • Kean Rd
  • North St & Spicers Mill Rd
  • Berry St
  • Spicers Mill Rd & Belleview Ave
  • Belleview Park
  • Montevista Ave & Harper Dr
  • Montevista Ave & Peliso Ave
  • N. Main St 7-Eleven
  • Food Lion
  • Gordonsville Library
  • Gordonsville Post Office
  • Mill St & Cobb St
  • Lucketts Alley & East St
  • Browntown Rd & Cox Mill Rd
  • Salvation Army
  • Academy Hill Apts
  • Highland Commons Apts
  • Brookside Rehab & Nursing Center
  • Rip Van Winkle Motel
  • Red Roof Inn - Warrenton
  • Dialysis Center
  • Green Street
  • Fauquier Health Hospital N. Entrance
  • Clarke County
  • Nature's Touch
  • Fantasyland Park
  • Ferguson's
  • Plaza Shopping Center
  • Fauquier County Health Department
  • Fauquier Health Medical Center
  • Depot
  • Koon's
  • Culpeper County Field House
  • UVA Primary
  • The Arbors
  • Northridge
  • Belle Court
  • Brandy Knoll
  • Med Express
  • Three Flags
  • The Culpeper
  • Path Recreation & Fitness Center
  • Hampton Inn
  • Culpeper Library
  • Culpeper Dept. of Social Services
  • Free Clinic Of Culpeper
  • Culpeper Post Office
  • Fairfax St.
  • Memorial Park
  • Waters Place
  • Smithsonian
  • N. Shenandoah Ave & West 9th St.
  • RIGID
  • Purcellville Town Hall
  • Walmart - Woodstock
  • CVS (South Ox Road & Warren Drive)
  • Food Lion/Goodwill/Burke’s Outlet - Woodstock
  • Shenandoah Memorial Hospital - Door 24
  • Valley Vista
  • Valley Vista
  • Downtown Woodstock
  • Downtown Woodstock
  • Shenandoah County DSS/Courthouse - Woodstock
  • Brother’s Pizza & Subs - Maurertown
  • Valley View Motel - Strasburg
  • Massanutten Manor - Strasburg
  • Forrest Glen Apartments - Strasburg
  • Strasburg Pharmacy
  • Queen Street Diner - Strasburg
  • Budget Inn - Strasburg
  • Entrance to Heishman Trailer Park - Maurertown
  • 601 N. Main Street (Near County Gov’t Center)
  • Shenandoah Memorial Hospital - Door 5
  • Downtown - Edinburg
  • Rose Drive & Kadies Lane - Edinburg
  • Edinburg Mill - Edinburg
  • Food Lion - Mt. Jackson
  • Main Street & Nelson Street - Mt. Jackson
  • Library – Mt. Jackson
  • Fire & Rescue – Mt. Jackson
  • North Apartments - New Market
  • John Seiver Road (Across from New Market Poultry)
  • Community Park - New Market
  • New Market Poultry - New Market
  • Budget Inn - New Market
  • Main Street - Mt. Jackson
  • Main Street & Bridge Street – Mt. Jackson
  • Circle K - Mt. Jackson
  • Edinburg Mill - Edinburg
  • and 1 more (see the full list on the map or in the GeoJSON)

Over time

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

2026-07-25: 69.32026-07-30: 67.22026-07-31: 66.82026-08-01: 66.4
Show the numbers
Overall score by check, with the change from the previous check
CheckScoreChange
2026-07-2569.3 first check
2026-07-3067.2 down 2.1
2026-07-3166.8 down 0.4
2026-08-0166.4 down 0.4

What changed since your last check

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

What changed in this feed

Overall score fell 0.4 points 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
  • Warning261 instances

    261 of 261 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 (opens the GTFS Schedule reference on an external site)

  • Warning251 instances

    251 of 251 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)

  • Warning56 instances

    56 of 261 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 (opens GTFS Best Practices on an external site)

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

  • Warning19 instances

    On some trips the stop distances run a little past the end of the route line.

    The stop and shape distance values don't quite line up, so any math that uses them can drift.

    Fix: Re-generate shape_dist_traveled on export so stop and shape distances use the same units. (Usually an export-tool fix, not hand editing.)

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

  • Warning4 instances

    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)

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

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

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

  • Info1 instance

    This feed includes flexible (demand-responsive) service, and riders are told how to book it.

    Dial-a-ride and zone service are described for trip planners, not just fixed routes.

    Fix: No action needed. (None.)

    Finding code: scorecard_flex_service

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 31 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 Needs attention
252 of 261 trips have a shape; 9 do not. Fill in shapes.txt and trips.shape_id for the remaining trips so every trip has a path. Reduced, Rural, and Tribal NTD reporters need full coverage by Report Year 2026.

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

  • 32 of 251 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 91 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 82 / 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 52 / 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 57 / 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.

Virginia Regional Transit Flex GTFS data quality grade: D

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/virginia-regional-transit-2445/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.