← Back to the full scorecard

Board packet · transit data quality · checked 2026-11-09

Virginia Railway Express (VRE)

Grade F · 35.3 / 100 · partial: freshness not measured

The scoring methodology changed since the prior check; the trend restarts here without an improvement or regression claim.

Scored from a Mobility Database mirror copy downloaded on 2026-10-02, because the feed URL on file could not be downloaded. Service dates in that copy end 2024-11-29. It may not match the feed the agency publishes today.

What this grade measures

The quality of the schedule data in the feed scored here for trip-planning apps: whether riders using Google Maps, Apple Maps, or Transit see current, correct, and complete information. It measures the data feed, not service quality or operations.

Progress this period

No newly cleared items this period. The score and trend above reflect the mirror copy described above, which may not match the feed the agency publishes today.

What needs attention next

Three improvements, in priority order, each sized so the board can see what it is approving:

  1. Check that https://www.vre.org/gtfs/google_transit.zip still serves your current feed. If the feed moved, publish the new address.

    The feed URL on file, https://www.vre.org/gtfs/google_transit.zip, could not be downloaded: the server answered with an error instead of the file. Trip planners download the feed from that address too. The grade here was measured on an older Mobility Database copy whose service ended 2024-11-29, so freshness is not graded until the current feed can be downloaded.

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

    Estimated effort: Usually a server or hosting setting, not a change to the feed itself.

  2. Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.

    The trip updates realtime feed failed during sampling. When this feed is down, riders see scheduled times presented as if they were live.

    This was measured over a realtime sampling window, so it has no feed-wide share.

    Estimated effort: Usually a vendor support ticket.

  3. Check the vehicle positions endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.

    The vehicle positions realtime feed failed during sampling. When this feed is down, riders see scheduled times presented as if they were live.

    This was measured over a realtime sampling window, so it has no feed-wide share.

    Estimated effort: Usually a vendor support ticket.

Riders and need behind these fixes

  • No ridership snapshot was on hand when this was built, so annual rider-trips are not known.
  • 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.

Feed evidence
The feed URL on file, https://www.vre.org/gtfs/google_transit.zip, could not be downloaded: the server answered with an error instead of the file.
Next action
Check that https://www.vre.org/gtfs/google_transit.zip still serves your current feed. If the feed moved, publish the new address.
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

Produced by the GTFS Scorecard, an open-source data quality tool. A data-quality read to support the board conversation, not an official compliance determination. Live scorecard: https://gtfsscorecard.org/agency/virginia-railway-express-vre/. Rubric v1.4, validator 8.0.1.