Feed status · checked 2026-11-21

Hampton Roads Transit (HRT)

Based on the feed source on file; publisher ownership is not verified

Service mode Tram + Bus + Ferry

65.0 / 100

unchanged since 2026-11-20

Cataloged in Virginia.

Covers 182 daysAccessibility gapsRealtime not yet published

The grade is not a count of validator errors. It also weighs freshness and rider information. How the grade works

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

2670 of 2670 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,670 stops in the feed.

⏱ 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

14012 of 14012 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 14,012 trips in the feed.

⏱ A default or per-trip field in your export.worth about +15 points in its category

Fix 03

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.

14012 of 14012 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.

Fixing this covers all 14,012 trips in the feed.

⏱ Usually one value per route pattern in your scheduling source.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-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.

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
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. Fix 01 · 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.

  2. Fix 02 · 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.

  3. Fix 03 · Read the fix guide for scorecard_missing_headsigns

    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 182 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 · 134 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 134 ferry trips publish wheelchair_accessible. This reports published values, not verified physical usability.
Bicycles
Unknown: none of the 134 ferry trips publish bikes_allowed.
Cars
Unknown: none of the 134 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.

About this feed

Looking for times or routes? This page checks the data file that trip planners use. For schedules, use the agency's own website or a trip planner.

Hampton Roads Transit (HRT)’s published feed lists 84 routes (tram / light rail, bus and ferry), 14,012 scheduled trips and 2,670 stops. Its service dates run from 2026-10-25 through 2027-05-22. The published file last changed on 2026-10-28.

Score by category

Correctness75.2 / 100

The MobilityData validator flagged 5 kinds of issue across 2841 instances (0 error, 2824 warning, 17 informational).

Freshness100.0 / 100

Service data covers the next 182 days.

Rider experience22.6 / 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

  • 21 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.

  • 2626 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.

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

  • 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)
  • 033 (pink)
  • 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)
  • 201 (yellow)
  • 202 (yellow)
  • 203 (yellow)
  • 206 (yellow)
  • 208 (yellow)
  • 209 (yellow)
  • 210 (yellow)
  • 212 (yellow)
  • 213 (yellow)
  • 214 (yellow)
  • 215 (yellow)
  • 220 (yellow)
  • 221 (yellow)
  • 223 (yellow)
  • 245 (yellow)
  • 247 (yellow)
  • 257 (yellow)
  • 261 (yellow)
  • 405 (gray)
  • 414 (red)
  • 430 (orange)
  • 501 (yellow)
  • 506 (yellow)
  • 512 (yellow)
  • 513 (yellow)
  • 514 (yellow)
  • 800 (pink)
  • 921 (red)
  • 960 (yellow)
  • 961 (yellow)
  • 964 (white)
  • 966 (green)
  • 967 (pink)
  • 972 (blue)
  • 980 (purple)
  • 981 (brown)
Routes in Hampton Roads Transit (HRT)'s feed
RouteTypeLine color
001 Granby StBusblack
002 Hampton BlvdBusgray
003 Chesapeake BlvdBusorange
004 Church StBuspink
005 WilloughbyBusblue
006 South NorfolkBusblue
008 Tidewater DrBusgreen
009 Sewells Point RdBusgreen
011 Colonial AveBusblue
012 Indian River RdBusteal
013 Campostella RdBusteal
014 Battlefield BlvdBusgreen
015 MILITARY HWYBusgreen
018 Ballentine BlvdBusteal
020 757 EXPRESS VIRGINIA BEACH BLVDBusred
021 Little Creek RdBusgray
022 Haygood RdBuspurple
023 PRINCESS ANNE RDBuspurple
024 Kempsville RdBusbrown
025 NEWTOWN RD / PRINCESS ANNE RDBuswhite
026 Lynnhaven PkwyBusgray
027 Diamond Springs RdBusred
029 Great Neck RdBuspink
033 General Booth BlvdBuspink
036 Holland RdBusyellow
041 CradockBusyellow
044 MidtownBusred
045 Portsmouth BlvdBuspink
047 High StBusblue
050 County St / Victory CrossingBuspurple
057 CamelotBuswhite
058 Bainbridge BlvdBusblack
090 FerryFerrygray
101 Kecoughtan RdBusgray
102 Queen StBusyellow
103 Shell RdBusred
104 Marshall AveBusblue
105 Briarfield RdBusgreen
106 Warwick BlvdBusgreen
107 Denbigh BlvdBusblue
108 Warwick Blvd / Lee HallBusgreen
109 Pembroke AveBusteal
110 Virginia Peninsula Community CollegeBusteal
111 Patrick Henry MallBusgreen
112 757 Express Jefferson AveBusgreen
114 757 Express Mercury BlvdBusteal
115 Fox Hill RdBusred
118 Neil Armstrong PkwyBuspurple
201 SNOW GRANBY STBusyellow
202 SNOW HAMPTON BLVDBusyellow
203 SNOW CHESAPEAKE BLVDBusyellow
206 SNOW SOUTH NORFOLKBusyellow
208 SNOW TIDEWATER DrBusyellow
209 FIRST COLONIAL SNOWBusyellow
210 INDEPENDENCE SNOWBusyellow
212 SNOW INDIAN RIVER RDBusyellow
213 SNOW CAMPOSTELLA RDBusyellow
214 SNOW BATTLEFIELD BLVDBusyellow
215 SNOW MILITARY HWYBusyellow
220 SNOW 757 EXPRESS VIRGINIA BEACH BLVDBusyellow
221 SNOW LITTLE CREEK ROADBusyellow
223 SNOW PRINCESS ANNE RDBusyellow
245 SNOW PORTSMOUTH BLVDBusyellow
247 SNOW HIGH STBusyellow
257 SNOW CAMELOTBusyellow
261 SNOW 757 EXPRESS / NNTC / HTC / DNTCBusyellow
405 Willow OaksBusgray
414 Oakland Industrial ParkBusred
430 Denbigh FringeBusorange
501 SNOW KECOUGHTAN RDBusyellow
506 SNOW WARWICK BLVDBusyellow
512 SNOW 757 EXPRESS JEFFERSON AVEBusyellow
513 SNOW ABERDEENBusyellow
514 SNOW 757 EXPRESS MERCURY BLVDBusyellow
800 Tide Light RailTram / light railpink
921 757 Express / NNTC / Williamsburg Transit CenterBusred
960 757 Express / DNTC / Virginia Beach OceanfrontBusyellow
961 757 Express / NNTC / HTC / DNTCBusyellow
964 757 Express / NNTC / Smithfield GwaltneyBuswhite
966 757 Express / Silverleaf Station / NNTCBusgreen
967 757 Express / Military Hwy Station / NNTCBuspink
972 757 Express / TCC Virginia Beach / NNTCBusblue
980 757 Express / DNTC / Amz Chesapeake / Amz SuffolkBuspurple
981 757 Express / DNTC / Ballentine St / TCC / Amz VBBusbrown
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
  • INDEPENDENCE & JEANNE
  • CORPORATION & CONSTITUTION
  • SHORE & WINDWARD
  • NIMMO & UPTON
  • ELSON GREEN & UPTON
  • INDEPENDENCE & BROAD
  • 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 & GRAYDON(SNOW)
  • 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
  • REDGATE & COLLEY
  • 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 & DUNDALE SNOW
  • CHESAPEAKE & ROSEFIELD
  • CHESAPEAKE & JERNIGAN SNOW
  • EVELYN T BUTTS & LITTLE CREEK
  • 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 T BUTTS & LITTLE CREEK
  • CHESAPEAKE & AVE I
  • CHESAPEAKE & JOHNSTONS
  • CHESAPEAKE & CLEMENTS SNOW
  • 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
  • and 2420 more (see the full list on the map or in the GeoJSON)

Over time

Overall score across the last 13 checks — unchanged since 2026-11-20.

2026-11-09: 65.02026-11-10: 65.02026-11-11: 65.02026-11-12: 65.02026-11-13: 65.02026-11-14: 65.02026-11-15: 65.02026-11-16: 65.02026-11-17: 65.02026-11-18: 65.02026-11-19: 65.02026-11-20: 65.02026-11-21: 65.0
Show the numbers
Overall score by check, with the change from the previous check
CheckScoreChange
2026-11-0965.0 first check
2026-11-1065.0 no change
2026-11-1165.0 no change
2026-11-1265.0 no change
2026-11-1365.0 no change
2026-11-1465.0 no change
2026-11-1565.0 no change
2026-11-1665.0 no change
2026-11-1765.0 no change
2026-11-1865.0 no change
2026-11-1965.0 no change
2026-11-2065.0 no change
2026-11-2165.0 no change

What changed since your last check

  • Correctness no change
  • Freshness no change
  • 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.

Feed history by published file
CheckedPublished fileService dates throughGrade at the time
2026-11-09 to 2026-11-21 (13 checks)e8d1cfdf6e522027-05-22Current rubric: see the trend above
2026-10-28 to 2026-11-06 (10 checks)e8d1cfdf6e522027-05-22D, 65 under rubric 1.4, an earlier scoring contract; not comparable with today’s grade
2026-10-16 to 2026-10-27 (12 checks)bf733abbfa052027-05-22F, 51.6 under rubric 1.4, an earlier scoring contract; not comparable with today’s grade
2026-10-02 to 2026-10-15 (14 checks)d62c2542fd282026-10-24F, 41.1 under rubric 1.4, an earlier scoring contract; not comparable with today’s grade
2026-07-25 to 2026-10-01 (65 checks)d62c2542fd282026-10-24F, 46.9 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-07-17 to 2026-07-24 (6 checks)d62c2542fd282026-10-24D, 62.3 under rubric 1.2, an earlier scoring contract; not comparable with today’s grade
2026-07-16f37db8d020d22024-10-26F, 28.9 under rubric 1.2, an earlier scoring contract; not comparable with today’s grade
2026-07-14 to 2026-07-15 (2 checks)d62c2542fd282026-10-24D, 62.3 under rubric 1.2, an earlier scoring contract; not comparable with today’s grade
2026-06-19 to 2026-07-13 (25 checks)d62c2542fd282026-10-24D, 62.3 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade

Everything we checked

10 findings, ordered by severity.

Show every finding
  • Warning14012 instances

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

  • Warning14012 instances

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

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

  • Warning2670 instances

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

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

  • Warning4 instances

    Some service calendars have no days of the week switched on.

    Trips tied to these calendars never run; they are dead data that can mask real schedule problems.

    Fix: Delete the empty calendars or set their service days. (A few minutes in your scheduling software.)

    Finding code: service_has_no_active_day_of_the_week · Read the fix guide for service_has_no_active_day_of_the_week · 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)

  • Info2656 instances

    About 2656 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)

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

How we measured this

Checked for changes 18 hours ago; last changed 36 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.

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.5, validator 8.0.1.

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 182 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 Ready
All 14012 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

One requirement remains for this feed to earn 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 182 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.

Clears the Google and Apple Maps four-week coverage bar. This feed has 181 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 75 / 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 100 / 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.

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.

Hampton Roads Transit (HRT): GTFS feed quality grade D, 65.0 of 100, checked 2026-11-21. GTFS 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/hampton-roads-transit-hrt/2026-11-21.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-11-21. 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.