Feed status · checked 2026-10-07
Hampton Roads Transit (HRT)
Based on the feed source on file; publisher ownership is not verified
Service mode Tram + Bus + Ferry
down 0.4 since 2026-10-06
Cataloged 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.4, validator 8.0.1.
Checked for changes 32 minutes ago; last changed 108 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.
About this feed
Hampton Roads Transit (HRT)’s published feed lists 90 routes (tram / light rail, bus and ferry), 9,944 scheduled trips and 2,657 stops. Its service dates run from 2026-05-10 through 2026-10-24. The published file has not changed since our first check on 2026-06-19.
Top things to fix
Re-export with a validity window that reaches at least 60 days out.Likely your export tool
Service data runs out in 17 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.
This one is about the feed as a whole, so there is no share of it to count.
⏱ One export setting.worth about +63 points in its category
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
2657 of 2657 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 2,657 stops in the feed.
⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category
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
9944 of 9944 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the transit vehicle itself can take them.
Fixing this covers all 9,944 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-10-05.
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
- Finding
- Fix 02 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
- Finding
- Fix 03 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.
Fix 01 · Read the fix guide for scorecard_feed_expiring_soon
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.
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.
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 17 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.
Ungraded capability read
Ferry data profile
A ferry-specific view of what this GTFS feed publishes. Schedule measurements use ferry routes and trips only; fare and realtime facts are labeled as whole-feed. Unknown values are not treated as no.
- Ferry service
- 1 routes · 412 trips
- Terminal structure
- 3 ferry boarding locations; no parent-station hierarchy is published.
- Terminal access
- Not applicable: no ferry boarding location is linked to a parent station, so stop_access is not permitted here.
- Published accessibility
- Unknown: none of the 3 ferry boarding locations publish wheelchair_boarding. Unknown: none of the 412 ferry trips publish wheelchair_accessible. This reports published values, not verified physical usability.
- Bicycles
- Unknown: none of the 412 ferry trips publish bikes_allowed.
- Cars
- Unknown: none of the 412 ferry trips publish cars_allowed.
- Fares
- Whole feed: applied fare data is published using GTFS Fares v1.
- Realtime
- Whole feed: no GTFS-Realtime endpoints are configured in this scorecard.
Descriptive only. This profile does not change the grade or verify vessels, terminal facilities, vehicle carriage, fares, or accessibility in the real world. Field meanings follow the GTFS Schedule reference.
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.
Score by category
The MobilityData validator flagged 6 kinds of issue across 3191 instances (0 error, 3170 warning, 21 informational).
Service data runs out in 17 day(s). Publish an updated feed soon or riders will lose trip planning.
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.
2 accessibility depth signals
23 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (003, 004, 012, 013, 014, 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.
2610 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("SAINT PAULS & CHARLOTTE", "SAINT PAULS & PLUME", "WATERSIDE & COMMERCIAL", 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.
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.
This feed has 2657 stops.
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.
- 001 (black)
- 002 (gray)
- 003 (orange)
- 004 (pink)
- 005 (blue)
- 006 (blue)
- 008 (green)
- 009 (green)
- 011 (blue)
- 012 (teal)
- 013 (teal)
- 014 (green)
- 015 (green)
- 018 (teal)
- 020 (red)
- 021 (gray)
- 022 (purple)
- 023 (purple)
- 024 (brown)
- 025 (white)
- 026 (gray)
- 027 (red)
- 029 (pink)
- 030 (orange)
- 031 (pink)
- 033 (pink)
- 035 (orange)
- 036 (yellow)
- 041 (yellow)
- 044 (red)
- 045 (pink)
- 047 (blue)
- 050 (purple)
- 057 (white)
- 058 (black)
- 090 (gray)
- 101 (gray)
- 102 (yellow)
- 103 (red)
- 104 (blue)
- 105 (green)
- 106 (green)
- 107 (blue)
- 108 (green)
- 109 (teal)
- 110 (teal)
- 111 (green)
- 112 (green)
- 114 (teal)
- 115 (red)
- 118 (purple)
- 405 (gray)
- 414 (red)
- 430 (orange)
- 800 (pink)
- 921 (red)
- 960 (yellow)
- 961 (yellow)
- 964 (white)
- 966 (green)
- 967 (pink)
- 972 (blue)
- 980 (purple)
- 981 (teal)
| Route | Type | Line color |
|---|---|---|
| 001 GRANBY ST | Bus | black |
| 002 HAMPTON BLVD | Bus | gray |
| 003 CHESAPEAKE BLVD | Bus | orange |
| 004 CHURCH ST | Bus | pink |
| 005 WILLOUGHBY | Bus | blue |
| 006 SOUTH NORFOLK | Bus | blue |
| 008 TIDEWATER DRIVE | Bus | green |
| 009 SEWELLS POINT RD | Bus | green |
| 011 COLONIAL AVE | Bus | blue |
| 012 INDIAN RIVER RD | Bus | teal |
| 013 CAMPOSTELLA RD | Bus | teal |
| 014 BATTLEFIELD BLVD | Bus | green |
| 015 MILITARY HWY | Bus | green |
| 018 BALLENTINE BLVD | Bus | teal |
| 020 757X - VIRGINIA BEACH BLVD | Bus | red |
| 021 LITTLE CREEK RD | Bus | gray |
| 022 WESLEYAN & HAYGOOD RD | Bus | purple |
| 023 PRINCESS ANNE RD | Bus | purple |
| 024 KEMPSVILLE RD | Bus | brown |
| 025 NEWTOWN RD | Bus | white |
| 026 LYNNHAVEN MALL/TCC VB | Bus | gray |
| 027 NORTHAMPTON BLVD | Bus | red |
| 029 GREAT NECK/LYNNHAVEN PKWY | Bus | pink |
| 030 ATLANTIC AVENUE TROLLEY | Bus | orange |
| 031 AQUARIUM & CAMPGROUND SHUTTLE | Bus | pink |
| 033 GENERAL BOOTH BLVD | Bus | pink |
| 035 BAY FRONT & OCEANFRONT SHUTTLE | Bus | orange |
| 036 HOLLAND RD | Bus | yellow |
| 041 CRADOCK | Bus | yellow |
| 043 PARKVIEW | Bus | white (no shape in feed) |
| 044 MIDTOWN | Bus | red |
| 045 PORTSMOUTH BLVD | Bus | pink |
| 047 HIGH ST | Bus | blue |
| 050 ACADEMY PARK | Bus | purple |
| 057 DEEP CREEK | Bus | white |
| 058 BAINBRIDGE BLVD | Bus | black |
| 090 ELIZABETH RIVER FERRY | Ferry | gray |
| 101 KECOUGHTAN | Bus | gray |
| 102 QUEEN STREET | Bus | yellow |
| 103 SHELL RD | Bus | red |
| 104 MARSHALL AVENUE | Bus | blue |
| 105 BRIARFIELD RD | Bus | green |
| 106 WARWICK BOULEVARD | Bus | green |
| 107 DENBIGH BOULEVARD | Bus | blue |
| 108 WARWICK/LEE HALL | Bus | green |
| 109 BUCKROE | Bus | teal |
| 110 VIRGINIA PENINSULA COMMUNITY COLLEGE | Bus | teal |
| 111 PATRICK HENRY MALL | Bus | green |
| 112 757X - JEFFERSON AVE | Bus | green |
| 114 757X - MERCURY BOULEVARD | Bus | teal |
| 115 FOX HILL | Bus | red |
| 118 NEIL ARMSTRONG PARKWAY | Bus | purple |
| 201 SNOW - GRANBY ST | Bus | yellow (no shape in feed) |
| 202 SNOW - HAMPTON BLVD | Bus | yellow (no shape in feed) |
| 203 SNOW - CHESAPEAKE BLVD | Bus | yellow (no shape in feed) |
| 206 SNOW - SOUTH NORFOLK | Bus | yellow (no shape in feed) |
| 208 SNOW - TIDEWATER Dr | Bus | yellow (no shape in feed) |
| 209 SNOW - FIRST COLONIAL SNOW | Bus | yellow (no shape in feed) |
| 210 SNOW - INDEPENDENCE SNOW | Bus | yellow (no shape in feed) |
| 212 SNOW - INDIAN RIVER RD | Bus | yellow (no shape in feed) |
| 213 SNOW - CAMPOSTELLA RD | Bus | yellow (no shape in feed) |
| 214 SNOW - BATTLEFIELD BLVD | Bus | yellow (no shape in feed) |
| 215 SNOW - MILITARY HWY | Bus | yellow (no shape in feed) |
| 220 SNOW - 757 EXPRESS VIRGINIA BEACH BLVD | Bus | yellow (no shape in feed) |
| 221 SNOW - LITTLE CREEK ROAD | Bus | yellow (no shape in feed) |
| 223 SNOW - PRINCESS ANNE RD | Bus | yellow (no shape in feed) |
| 245 SNOW - PORTSMOUTH BLVD | Bus | yellow (no shape in feed) |
| 247 SNOW - HIGH ST | Bus | yellow (no shape in feed) |
| 257 SNOW - CAMELOT | Bus | yellow (no shape in feed) |
| 261 SNOW - 757 EXPRESS / NNTC / HTC / DNTC | Bus | yellow (no shape in feed) |
| 403 BUCKROE SHOPPING CENTER | Bus | white (no shape in feed) |
| 405 W. OAKS/COL.MALL | Bus | gray |
| 414 NEWPORT NEWS TRANSIT CENTER - OAKLAND INDUSTRIAL | Bus | red |
| 415 SYE-DENBIGH FPL TO WEST AVE | Bus | pink (no shape in feed) |
| 430 DENBIGH FRINGE | Bus | orange |
| 501 SNOW - KECOUGHTAN RD | Bus | yellow (no shape in feed) |
| 506 SNOW - WARWICK BLVD | Bus | yellow (no shape in feed) |
| 512 SNOW - 757 EXPRESS JEFFERSON AVE | Bus | yellow (no shape in feed) |
| 513 SNOW - ABERDEEN | Bus | yellow (no shape in feed) |
| 514 SNOW - 757 EXPRESS MERCURY BLVD | Bus | yellow (no shape in feed) |
| 800 LIGHT RAIL TIDE | Tram / light rail | pink |
| 921 WILLIAMSBURG | Bus | red |
| 960 757X - VIRGINIA BEACH to NORFOLK | Bus | yellow |
| 961 757X - NORFOLK TO NNTC | Bus | yellow |
| 964 SMITHFIELD | Bus | white |
| 966 757X - SILVERLEAF - NN SHIPBUILDING | Bus | green |
| 967 757X - NNTC TO INDIAN RIVER PARK & RIDE | Bus | pink |
| 972 757X - TCC to NN SHIPYARD | Bus | blue |
| 980 757X - AMAZON | Bus | purple |
| 981 757X - AMAZON | Bus | teal |
List every stop
- SAINT PAULS & CHARLOTTE
- SAINT PAULS & PLUME
- WATERSIDE & COMMERCIAL
- MONTICELLO & BRAMBLETON
- MONTICELLO & STARKE
- MONTICELLO & PRINCESS ANNE
- MONTICELLO & 18TH
- 26TH & ARMISTEAD
- MONTICELLO & 29TH
- GRANBY & 33RD
- GRANBY & 38TH
- GRANBY & DELAWARE
- GRANBY & 42ND
- GRANBY & WILLOW WOOD
- GRANBY & SEVERN
- GRANBY & KINGSLEY
- GRANBY & DUMONT
- GRANBY & SIR OLIVER
- GRANBY & SEEKEL
- GRANBY & FORSYTHE
- GRANBY & FIFE
- GRANBY & SUBURBAN
- WARDS CORNER TRANSFER
- GRANBY & BAYVIEW
- GRANBY & CHESTER
- GRANBY & RANDALL
- GRANBY & BATTERSEA
- GRANBY & GOVERNMENT
- GRANBY & DUFFYS
- OCEAN VIEW & HAMMETT
- OCEAN VIEW & NORFOLK
- OCEAN VIEW & ELNORA
- OCEAN VIEW & ATLANS
- OCEAN VIEW & BEACH VIEW
- OCEAN VIEW & STURGIS
- OCEAN VIEW & BEAUMONT
- OCEAN VIEW & GROVE
- OCEAN VIEW & CAPE VIEW
- OCEAN VIEW & 1ST BAY
- OCEAN VIEW & 3RD BAY
- OCEAN VIEW & 7TH BAY
- OCEAN VIEW & 10TH BAY
- OCEAN VIEW & 14TH BAY
- OCEAN VIEW & 16TH BAY
- OCEAN VIEW & 20TH BAY
- SHORE & PLEASANT
- SHORE & DUNNING
- JOINT EXP BASE LITTLE CREEK
- SHORE & FLOWERFIELD
- SHORE & HEUTTE
- SHORE & DIAMOND SPRINGS
- SHORE & LAKE SMITH
- SHORE & KIMBALL
- SHORE & LAKE SHORES
- SHORE & JACK FROST
- SHORE & GELA
- SHORE & WELLINGS
- SHORE & PLEASURE HOUSE
- PLEASURE HOUSE & VICTORY
- PLEASURE HOUSE & FIRST COURT
- PLEASURE HOUSE & INDEPENDENCE
- INDEPENDENCE & EWELL
- INDEPENDENCE & PAUL REVERE
- INDEPENDENCE & HAYGOOD
- INDEPENDENCE & WITCHDUCK
- INDEPENDENCE & PEMBROKE
- INDEPENDENCE & JERICHO
- INDEPENDENCE & HINSDALE
- CORPORATION & CONSTITUTION
- SHORE & WINDWARD
- NIMMO & UPTON
- ELSON GREEN & UPTON
- INDEPENDENCE & HINSDALE
- INDEPENDENCE & CONSTITUTION
- INDEPENDENCE & HESSIAN
- INDEPENDENCE & PEMBROKE
- INDEPENDENCE & WITCHDUCK
- INDEPENDENCE & WISHART
- INDEPENDENCE & WAKEFIELD
- INDEPENDENCE & SEAL
- INDEPENDENCE & TULIP
- PLEASURE HOUSE & ANDREW JACKSON
- SHORE & GELA
- SHORE & JACK FROST
- SHORE & LAKE SHORES
- SHORE & KIMBALL
- SHORE & LAKE SMITH
- SHORE & DIAMOND SPRINGS
- SHORE & FLOWERFIELD
- SHORE & DUNNING
- OCEAN VIEW & 19TH BAY
- OCEAN VIEW & 14TH BAY
- OCEAN VIEW & 10TH BAY
- OCEAN VIEW & 6TH BAY
- OCEAN VIEW & 2ND BAY
- OCEAN VIEW & CAPEVIEW
- OCEAN VIEW & GROVE
- OCEAN VIEW & WILLOW
- OCEAN VIEW & STURGIS
- OCEAN VIEW & BEACH VIEW
- OCEAN VIEW & NORFOLK
- GRANBY & GOVERNMENT
- GRANBY & OSBORNE
- GRANBY & LEICESTER
- GRANBY & CHESTER
- GRANBY & LANDALE
- GRANBY & BAYVIEW
- GRANBY & LITTLE CREEK
- GRANBY & NORTH SHORE
- GRANBY & WARREN
- GRANBY & OXFORD
- GRANBY & CARLISLE
- GRANBY & WHITING
- GRANBY & KINGSLEY
- GRANBY & SEVERN
- GRANBY & WILLOW WOOD
- GRANBY & CONNECTICUT
- GRANBY & 35TH
- MONTICELLO & 29th
- MONTICELLO & 25TH
- MONTICELLO & 19TH
- MONTICELLO & 15TH
- MONTICELLO & PRINCESS ANNE
- WOODLAKE & OLD GREENBRIAR
- OLD GREENBRIAR & JUNIPER
- OLD GREENBRIAR & JUNIPER
- OLNEY & COLONIAL
- OLNEY & STOCKLEY GARDENS
- OLNEY & NORFOLK GENERAL
- HAMPTON & PRINCESS ANNE
- HAMPTON & SPOTSWOOD
- HAMPTON & 27TH
- HAMPTON & 37TH
- HAMPTON & 41ST
- HAMPTON & 45TH
- HAMPTON & 49TH
- HAMPTON & BOLLING
- HAMPTON & ROCKBRIDGE
- HAMPTON & SURRY
- HAMPTON & LEXAN
- HAMPTON & ESCADRILLE
- HAMPTON & HELENA
- HAMPTON & LITTLE CREEK
- HAMPTON & STAFF COLLEGE
- HAMPTON & BAKER
- HAMPTON & BEECHWOOD
- HAMMOND & ADMIRAL TAUSSIG
- HAMPTON & B
- HAMPTON & MAPLESHADE
- HAMPTON & BEECHWOOD
- HAMPTON & GLENDALE
- HAMPTON & HELMICK
- HAMPTON & BAKER
- HAMPTON & STAFF COLLEGE
- HAMPTON & LITTLE CREEK
- HAMPTON & RUNNYMEDE
- HAMPTON & NORTH SHORE
- HAMPTON & LEXAN
- HAMPTON & SURREY
- HAMPTON & ROCKBRIDGE
- HAMPTON & BOLLING
- HAMPTON & 45TH
- HAMPTON & 41ST
- HAMPTON & 25TH
- HAMPTON & WOODROW
- COLLEY & RALEIGH
- OLNEY & MOWBRAY ARCH
- OLNEY & CHRYSLER MUSEUM
- HAMPTON & SPOTSWOOD
- ELSON GREEN & UPTON
- NIMMO & UPTON
- 26TH & GAZEL
- 26TH & WAVERLY
- LAFAYETTE & DUPONT
- LAFAYETTE & BELLEVUE
- LAFAYETTE & LORRAINE
- LAFAYETTE & BAPAUME
- CHESAPEAKE & CROMWELL
- CHESAPEAKE & ROBINHOOD
- CHESAPEAKE & CURIE
- CHESAPEAKE & BUCKINGHAM
- CHESAPEAKE & LENOIR
- CHESAPEAKE & NORVIEW
- CHESAPEAKE & GREEN
- CHESAPEAKE & STRAND
- CHESAPEAKE & ROSEFIELD
- EVELYN BUTTS & AVENUE J
- CHESAPEAKE & LITTLE CREEK
- CHESAPEAKE & ELK
- CHESAPEAKE & SHEPPARD
- CHESAPEAKE & FRANK
- CHESAPEAKE & FISHERMANS
- CHESAPEAKE & BAYVIEW
- CHESAPEAKE & DUNE
- CHESAPEAKE & CHESTER
- CHESAPEAKE & DUDLEY
- HAMPTON & RUNNYMEDE
- CHESAPEAKE & LEICESTER
- CHESAPEAKE & FARRELL
- CHESAPEAKE & EARL
- CHESAPEAKE & BAYVIEW
- CHESAPEAKE & FISHERMANS
- CHESAPEAKE & SHEPPARD
- CHESAPEAKE & BURKSDALE
- CHESAPEAKE & DOVERCOURT
- CHESAPEAKE & LITTLE CREEK
- EVELYN BUTTS & AVENUE J
- CHESAPEAKE & AVE I
- CHESAPEAKE & JOHNSTONS
- CHESAPEAKE & KITRELL
- CHESAPEAKE & DUNDALE
- CHESAPEAKE & PICADILLY
- CHESAPEAKE & STRAND
- CHESAPEAKE & GREEN
- CHESAPEAKE & NORVIEW
- CHESAPEAKE & CRAVEN
- CHESAPEAKE & NANSEMOND
- CHESAPEAKE & WAYNE CREEK
- CHESAPEAKE & NOTTAWAY
- CHESAPEAKE & ROBIN HOOD
- LAFAYETTE & MARNE
- LAFAYETTE & LENS
- LAFAYETTE & BREST
- LAFAYETTE & DUNKIRK
- LAFAYETTE & TIDEWATER
- LAFAYETTE & VERSAILLES
- LAFAYETTE & ORLEANS
- 27TH & LEO
- 27TH & FAWN
- MONTICELLO & 26TH
- SAINT PAULS & WOOD
- CHURCH & OLNEY
- TIDEWATER & PRINCESS ANNE
- CHURCH & GOFF
- CHURCH & B
- 20TH & GRANBY
- 21ST & OMOHUNDRO
- 21ST & LLEWELLYN
- 21ST & DEBREE
- 21ST & MANTEO
- 38TH & BLUESTONE
- COLLEY & 35TH
- COLLEY & 26TH
- COLLEY & GRAYDON
- COLLEY & RALEIGH
- COLLEY & GRAYDON
- COLLEY & 26TH
- COLLEY & 35TH
- 38TH & BOWDENS FERRY
- 21ST & COLONIAL
- and 2407 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 2 checks — down 0.4 since 2026-10-06.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-10-06 | 44.8 | first check |
| 2026-10-07 | 44.4 | down 0.4 |
What changed since your last check
- Correctness no change
- Freshness down 1.7
- 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.
| Checked | Published file | Service dates through | Grade at the time |
|---|---|---|---|
| 2026-10-06 to 2026-10-07 (2 checks) | d62c2542fd28 | 2026-10-24 | Current rubric: see the trend above |
| 2026-08-06 to 2026-09-13 (4 checks) | d62c2542fd28 | 2026-10-24 | F, 54.4 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-06-19 to 2026-07-10 (21 checks) | d62c2542fd28 | 2026-10-24 | D, 62.3 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade |
What changed in this feed
Overall score fell 0.4 points since 2026-10-06.
Same feed file as 2026-10-06; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops and export changes in a reader, with no sign-up.
Everything we checked
12 findings, ordered by severity.
Show every finding
- Warning9944 instances
9944 of 9944 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible stops, riders need to know the transit vehicle 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)
- Warning9944 instances
9944 of 9944 trips have no headsign, the text that tells riders where the transit vehicle 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)
- Warning2749 instances
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)
- Warning2657 instances
2657 of 2657 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)
- Warning412 instances
Missing bike allowance (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_bike_allowance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: missing_bike_allowance · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning7 instances
Some service calendars in the feed have already ended.
Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)
Finding code: expired_calendar · Read the fix guide for expired_calendar · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt lists no contact email and no contact URL.
Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.
Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)
Finding code: missing_feed_contact_email_and_url · Read the fix guide for missing_feed_contact_email_and_url · 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
Service data runs out in 17 day(s).
When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.
Fix: Re-export with a validity window that reaches at least 60 days out. (One export setting.)
Finding code: scorecard_feed_expiring_soon · Read the fix guide for scorecard_feed_expiring_soon · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info2640 instances
About 2640 stop names are written in ALL CAPS.
Mixed-case names are easier to read in apps and are read more naturally by screen readers.
Fix: Rename stops to mixed case where the language has letter case (for example, 'Central Station'). (Often a bulk fix in your scheduling software.)
Finding code: scorecard_stop_names_all_caps · Read the fix guide for scorecard_stop_names_all_caps · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info21 instances
The feed has a stretch of two weeks or more with no service running.
A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.
Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)
Finding code: big_gap_in_service · Read the fix guide for big_gap_in_service · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: scorecard_no_feed_contact · Read the fix guide for scorecard_no_feed_contact · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
NTD GTFS readiness Needs attention
This feed is close to NTD-ready. Service data runs out in 17 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 17 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 9944 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 17 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 17 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 17 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 69 / 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 28 / 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 23 / 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.
For programs that support several agencies
This scorecard and the board one-pager for Hampton Roads Transit (HRT) are free, and they stay free. If you support several agencies, as a state program, a technical-assistance center, a feed vendor, or a consultancy, you can buy the program report bundle. It puts this agency's board report in one archive with the reports for the other agencies you support, and each cover carries your program's name, logo, and accent color.
The report for Hampton Roads Transit (HRT) uses the same numbers as this page: grade F (44.4 out of 100) as of the check on 2026-10-07, its category scores, its top fixes, and its score at each check.
One bundle, up to 25 agencies: $149, paid once, delivered within 2 business days or refunded. Other plans, including a monthly refresh, are on the bundle page.
See a sample bundle report: a real agency's current grade, with placeholder branding.
A purchase buys no influence over grades, methodology, or which agencies are listed. The grade on this page comes from the check on 2026-10-07, scored with rubric v1.4 and MobilityData gtfs-validator 8.0.1. Based on the feed source on file; publisher ownership is not verified. Read how the grade is calculated.
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.
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/hampton-roads-transit-hrt/2026-10-07.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-10-07. 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.