Call-prep brief · 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.
For this call: lead with the grade and the three fixes below, then confirm the feed is current and the NTD details line up. Each fix is framed as a next step, not a failure.
What changed since the last check
The scoring methodology changed since the prior check. Category deltas restart with this scorecard.
Top three things to fix
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.
Effort: Usually a server or hosting setting, not a change to the feed itself.
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.
Effort: Usually a vendor support ticket.
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.
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
- Feed evidence
- The trip updates realtime feed failed during sampling.
- Next action
- Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
- 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
- Feed evidence
- The vehicle positions realtime feed failed during sampling.
- Next action
- Check the vehicle positions endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
- 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
NTD GTFS readiness: Not ready
Resolve this before you certify on the D-10. 1 validator error to resolve. No service end date could be read, so currency is unknown.
- Published Ready
- Published at a public URL.
- Valid Needs attention
- 1 validator error to resolve.
- Current Not ready
- No service end date could be read, so currency is unknown.
- 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 NTD ID (optional): Different (allowed). Your feed's agency_id is 1; your National Transit Database ID is 30073. A feed that serves several agencies (a shared regional feed) can legitimately carry more than one agency_id. The values do not need to equal the five-digit NTD ID, so this difference is allowed and carries no score. Confirm that P-50 crosswalks agency_id 1 to NTD ID 30073, and keep the feed value stable. Do not change it solely to make the two values equal.
Key facts
- Feed URL
- https://www.vre.org/gtfs/google_transit.zip
- Last checked
- 2026-11-09
- Service window
- Expiry date not stated in the feed.
- Location
- Virginia
Part of the Virginia portfolio: see where this agency sits among the other feeds in that group before the call.
A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.4, validator 8.0.1.