← All agencies

Feed status · checked 2026-08-01

Fairfax Connector

Based on the feed this agency publishes

Service mode Bus

61.3 / 100

unchanged since 2026-07-31

Catalogued in Virginia.

Covers 791 daysAccessibility gapsRealtime 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 32 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

Review the rule documentation for 'block_trips_with_overlapping_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

Block trips with overlapping stop times (flagged by the MobilityData validator). See the linked rule for what this affects.

⏱ Varies.worth about +24 points in its category

Fix 02

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

2894 of 3119 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 +23 points in its category

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
Block trips with overlapping stop times (flagged by the MobilityData validator).
Next action
Review the rule documentation for 'block_trips_with_overlapping_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
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. Review the rule documentation for 'block_trips_with_overlapping_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

    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. Self-check a feed before you publish.

  2. 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. 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. Self-check a feed before you publish.

  3. Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). · Read the fix guide

    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. 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 791 days.
Published accessibility data
Accessibility information is stated for 7.2% of stops and 93.8% 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 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.

Score by category

Correctness44.8 / 100

The MobilityData validator flagged 9 kinds of issue across 3826 instances (674 error, 3138 warning, 14 informational).

Freshness100.0 / 100

Service data covers the next 791 days.

Rider experience53.5 / 100

7% of stops state wheelchair accessibility (5% marked accessible, 2% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.

Accessibility39.7 / 100

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

2 accessibility depth signals

  • 56 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (152, 159, 161, 162, 171, 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.

  • 2940 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("RICHMOND HWY @ BACKLICK RD", "RICHMOND HWY @ SOUTHGATE DR", "RICHMOND HWY @ COLLARD ST", 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 3119 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.

  • 101 (teal)
  • 109 (gray)
  • 151 (yellow)
  • 152 (gray)
  • 159 (gray)
  • 161 (teal)
  • 162 (teal)
  • 171 (orange)
  • 231 (gray)
  • 232 (gray)
  • 301 (teal)
  • 305 (teal)
  • 306 (green)
  • 308 (pink)
  • 310 (red)
  • 321 (purple)
  • 322 (purple)
  • 334 (pink)
  • 335 (gray)
  • 340 (orange)
  • 341 (green)
  • 350 (teal)
  • 351 (yellow)
  • 352 (yellow)
  • 353 (teal)
  • 371 (yellow)
  • 393 (teal)
  • 394 (blue)
  • 395 (pink)
  • 396 (brown)
  • 401 (teal)
  • 402 (teal)
  • 423 (purple)
  • 427 (purple)
  • 432 (teal)
  • 461 (brown)
  • 462 (gray)
  • 463 (white)
  • 467 (teal)
  • 494 (gray)
  • 495 (gray)
  • 507 (red)
  • 553 (red)
  • 557 (gray)
  • 558 (pink)
  • 559 (pink)
  • 574 (pink)
  • 598 (white)
  • 605 (gray)
  • 610 (white)
  • 615 (pink)
  • 625 (teal)
  • 630 (red)
  • 642 (yellow)
  • 651 (pink)
  • 652 (yellow)
  • 660 (gray)
  • 662 (white)
  • 663 (pink)
  • 670 (green)
  • 671 (pink)
  • 672 (gray)
  • 697 (pink)
  • 698 (red)
  • 699 (blue)
  • 703 (teal)
  • 715 (gray)
  • 721 (pink)
  • 798 (gray)
  • 803 (teal)
  • 834 (orange)
  • 835 (green)
  • 901 (red)
  • 921 (purple)
  • 924 (gray)
  • 937 (teal)
  • 950 (gray)
  • 951 (purple)
  • 952 (teal)
  • 954 (teal)
  • 983 (green)
  • 9999A (orange)
  • 9999B (green)
  • 9999C (brown)
  • RIBS1 (yellow)
  • RIBS2 (teal)
  • RIBS3 (gray)
  • RIBS4 (teal)
  • RIBS5 (pink)
  • STRGW (white)
Routes in Fairfax Connector's feed
RouteTypeLine color
101 Fort Hunt - Mount VernonBusteal
109 Rose HillBusgray
151 Engleside - Mt VernonBusyellow
152 Groveton - Mt VernonBusgray
159 Engleside Limited-StopBusgray
161 Hybla Valley Counter-ClockwiseBusteal
162 Hybla Valley ClockwiseBusteal
171 Richmond HwyBusorange
231 Kingstowne Counter-ClockwiseBusgray
232 Kingstowne ClockwiseBusgray
301 Telegraph RdBusteal
305 Newington Forest - Silverbrook RoadBusteal
306 GMU - PentagonBusgreen
308 Franconia - Mt. Vernon Hosp.Buspink
310 Franconia-Rolling Valley LineBusred
321 Springfield Counter-ClockwiseBuspurple
322 Springfield ClockwiseBuspurple
334 DLA - NewingtonBuspink
335 Fort Belvoir ExpressBusgray
340 Patriot Ridge - SaratogaBusorange
341 Boston Blvd - SaratogaBusgreen
350 TAGS Springfield CirculatorBusteal
351 TAGS Springfield TSABusyellow
352 TAGS Springfield TSA lunchBusyellow
353 TAGS Springfield Circ Metro ParkBusteal
371 Lorton-SpringfieldBusyellow
393 Saratoga-Pentagon-Mark CenterBusteal
394 Saratoga - Pentagon ExpressBusblue
395 Gambrill - Pentagon ExpressBuspink
396 Backlick-Pentagon ExpressBusbrown
401 Backlick - Gallows Rd NorthboundBusteal
402 Backlick - Gallows Rd SouthboundBusteal
423 Central Tysons - Tysons Corner MetrBuspurple
427 Spring Hill Metro- Farm CreditBuspurple
432 Old Courthouse - BeulahBusteal
461 VIENNA-OAKTONBusbrown
462 Dunn Loring - Navy Federal - TysonsBusgray
463 Maple Avenue - TysonsBuswhite
467 Dunn Loring - TysonsBusteal
480 Wolf Trap Special ShuttleBusteal (no shape in feed)
494 Springfield - TysonsBusgray
495 Burke Center VRE - TysonsBusgray
507 Sunrise Valley - Sunset HillsBusred
553 Kingstream - Herndon - Fox MIllBusred
557 Reston South - SoapstoneBusgray
558 Center Harbor - WiehleBuspink
559 Reston TC - WiehleBuspink
574 Reston Town Center - TysonsBuspink
598 Reston S - PentagonBuswhite
605 Reston - Monument -Fair Oaks HospBusgray
610 GMU - CentrevilleBuswhite
615 Monument -Fair Oaks HospBuspink
625 Random Hills - Pender DrBusteal
630 Centreville - Monument -Busred
642 Aubrey Patent - WestfieldsBusyellow
651 Chantilly - Monument Dt.Buspink
652 Chantilly - Stringfellow P 7 RBusyellow
660 Centreville PnR - Tysons ExpBusgray
662 Centreville PnR - ViennaBuswhite
663 Stringfellow Rd. - ViennaBuspink
670 Chantilly - Franconia Limited StopBusgreen
671 Chantilly - Dunn Loring Limited StoBuspink
672 Chantilly - Dunn Loring Limited StoBusgray
697 Stringfellow Rd - D St SW DCBuspink
698 Stringfellow Rd. - PentagonBusred
699 Monument Dr - DOWNTOWN D.C.Busblue
703 Pimmit HIllsBusteal
715 East Falls Church - LangleyBusgray
721 Chain Bridge Road - McleanBuspink
798 Tysons - BethesdaBusgray
803 Annandale RoadBusteal
834 Pentagon - AnnandaleBusorange
835 Braeburn Dr - PentagonBusgreen
901 Herndon Metro -CentrevilleBusred
921 Herndon CirculatorBuspurple
924 Dranesville Rd - Franklin FarmBusgray
937 Coppermine - Elden - Herndon MetroBusteal
950 Herndon Metro - Reston Town CenterBusgray
951 Wiehle Reston E- Innovation CenterBuspurple
952 Sunset HillsBusteal
954 Sterling - Herndon MetroBusteal
983 Dulles Airport- Udvar HazyBusgreen
9999A Herndon TestBusorange
9999B Huntington TestBusgreen
9999C West Ox TestBusbrown
RIBS1 Lake Anne - Hunters WoodsBusyellow
RIBS2 Reston - South Lakes - Herndon MBusteal
RIBS3 Hunters Woods - Lake AnneBusgray
RIBS4 Reston Town Center - North PointBusteal
RIBS5 Herndon- Reston Town CenterBuspink
STRGW Strategic West OxBuswhite
List every stop
  • RICHMOND HWY @ FRANKLIN ST
  • ARLINGTON DR @ RICHMOND HWY
  • LOISDALE RD @ LOIS DR
  • LORTON RD @ LORTON STATION BLVD
  • LOISDALE RD @ LOISDALE CT
  • LOCKHEED BLVD @ SAUL RD
  • LORTON RD @ SANGER ST
  • LORTON RD @ TIMARAND DR
  • LEESBURG PIKE @ ATWOOD RD
  • LEESBURG PIKE @ BEULAH RD
  • LEESBURG PIKE @ CARPERS FARM WAY
  • ARMSTRONG ST @ UNIVERSITY DR
  • LEESBURG PIKE @ COLVIN RUN RD W
  • LEESBURG PIKE @ COLVIN RUN RD E
  • LEESBURG PIKE @ DELTA GLEN CT
  • LEESBURG PIKE @ FORESTVILLE DR
  • LEESBURG PIKE @ LEWINSVILLE RD
  • LEESBURG PIKE @ LEWINSVILLE RD
  • LEESBURG PIKE @ LYONS ST
  • ARLINGTON DR @ WINDBREAK DR
  • LEESBURG PIKE @ MIDDLETON RIDGE RD
  • LAKE PLEASANT DR @ SAINT DENNIS DR
  • LEESBURG PIKE @ TYSONS CORNER CTR
  • LEESBURG PIKE @ TOWLSTON RD
  • LEESBURG PIKE @ TOWLSTON RD
  • LEESBURG PIKE @ WOLFTRAP RUN RD
  • LEESBURG PIKE @ WOLFTRAP RUN RD
  • LITTLE RIVER TPKE @ BROOKSIDE DR
  • LITTLE RIVER TPKE @ CHOWAN AVE
  • LITTLE RIVER TURNPIKE @ MARKHAM ST
  • LITTLE RIVER TURNPIKE @ MARKHAM ST
  • LITTLE RIVER TURNPIKE @ MEDFORD DR
  • LITTLE RIVER TPKE @ DUKE ST
  • LITTLE RIVER TPKE@ ANNANDALE RD
  • LITTLE RIVER TURNPIKE @ HUMMER RD
  • LITTLE RIVER TPKE @ VIRGINIA ST
  • BACKLICK RD @ AUBURN ST
  • LITTLE RIVER TURNPIKE @ WOODLAND RD
  • LORTON STATION BLVD @ GRAYSONS MILL
  • LORTON STATION BLVD @ GRAYSONS MILL
  • LORTON STATION BLVD @ GRANDWIND DR
  • LORTON STATION BLVD @ LORTON RD
  • LORTON STATION BLVD @ OLD BEECH CT
  • LORTON STN BLVD @ PERCY SIMMS DR
  • LORTON STN BLVD @ PERCY SIMMS DR
  • MAPLE AVE @ BEULAH RD NE
  • MAPLE AVE @ BRANCH RD
  • BACKLICK RD @ BACKLICK CT
  • MAPLE AVE @ CENTER ST
  • MAPLE AVE @ CENTER ST
  • MAPLE AVE @ EAST ST
  • MAPLE AVE @ EAST ST
  • MAPLE AVE @ FOLLIN LA
  • MAPLE AVE@ GLYNDON ST
  • MAPLE AVE @ LAWYERS RD
  • MALCOLM RD @ NUTLEY ST
  • MALCOLM RD @ ORCHARD ST
  • MALCOLM RD @ OAK VALE CT
  • BACKLICK RD @ BACKLICK CT
  • MAPLE AVE @ PARK ST
  • MAPLE AVE @ PARK ST
  • MAPLE AVE @ GLYNDON ST
  • MANCHESTER BLVD @ ROCK RIDGE LA
  • MANCHESTER BLVD@ SILVER LAKE BLVD
  • MULBERRY BOTTOM LN @ LAURAL VALLEY
  • MARY BALDWIN DR @ SMITHWAY DR
  • MARY BALDWIN DR @ SMITHWAY DR
  • MEMORIAL ST @ SOUTH KINGS HWY
  • MEMORIAL ST @ SOUTH KINGS HWY
  • MCNAIR FARMS DR @ COPPERMINE RD
  • MCNAIR FARMS DR @ MASONS FERRY DR
  • MANCHESTER LAKES DR @ MANCHESTER BL
  • MANCHESTER LAKES @ OLD BRENTFORD CT
  • MANCHESTER LAKES @ SCHOONMAKER CT
  • BACKLICK RD @ BEVERLY ST
  • MT VERNON MEM HWY @ CHERRYTREE DR
  • MT VERNON MEM HWY @ CHERRYTREE DR
  • MOUNT VERNON MEMORIAL HWY @ FOREST
  • MOUNT VERNON MEMORIAL HWY @ FOREST
  • MT VERN MEM HWY @ FERRY LANDING RD
  • MT VERNON MEM HWY @ GRIST MILL RD
  • MT VERNON MEM HWY @ GRIST MILL RD
  • MT VERNON MEM HWY @ MT VERNON RD
  • MT VERNON MEM HWY @ MT VERNON RD
  • MOUNT VERNON MEMORIAL HWY @ OLD MIL
  • BACKLICK RD @ BRADDOCK RD
  • MT VERNON MEM HWY @ OLD MILL RD
  • MOUNT VERNON MEMORIAL HWY @ PATTON
  • MT VERNON MEM HWY @ PATTON BLVD
  • MOUNT VERNON MEMORIAL HWY @ RICHMON
  • MOUNT VERNON MEMORIAL HWY @ RICHMON
  • MT VERNON MEM HWY @ SOUTHWOOD DR
  • MT VERNON MEM HWY @ SOUTHWOOD DR
  • MONUMENT DR @ FAIRFAX CORNER AVE
  • MONUMENT DR @ FAIRFAX CORNER AVE
  • MONUMENT DR @ FAIR LAKES PROMENADE
  • MT VERNON HWY @ ALBEE LA
  • BACKLICK RD @ BRADDOCK RD
  • MONUMENT DR @ FAIR LAKES PROMENADE
  • MONUMENT DR @ FAIR RIDGE DR
  • MONUMENT DR @ MONUMENT HILL WAY
  • MONUMENT DR @ MONUMENT WAY
  • MONUMENT DR @ POLO DR
  • MONUMENT DR @ PARK VISTA BLVD
  • MT VERNON HWY @ ALBEE LA
  • BACKLICK RD @ CINDY LA
  • MOUNT VERNON HWY @ BATTERSEA LN (S)
  • MOUNT VERNON HWY @ BATTERSEA LN (S)
  • MT VERNON HWY @ CUNNINGHAM DR
  • MOUNT VERNON MEMORIAL HWY @ GRIST M
  • MOUNT VERNON MEMOIRIAL HWY @ GRIST
  • MORNING VIEW LA @ ISLAND CREEK CT
  • MORNING VIEW LA @ JOHN THOMAS DR
  • MT VERN MEM HWY @ MT VERNON HWY W
  • MT VERN MEM HWY @ MT VERNON HWY E
  • MT VERNON HWY @ SUNNY VIEW DR
  • BACKLICK RD @ CABIN JOHN RD
  • MORNING VIEW LA @ TASSIA DR
  • MORNING VIEW LA @ THOMAS GRANT DR
  • NEW DOMINION PKWY @ FOUNTAIN DR
  • NEW DOMINION PKWY @ RESTON PKWY
  • NEWINGTON FRST AVE@CURVING CREEK CT
  • NEWINGTON FRST AVE@CURVING CREEK CT
  • BACKLICK RD @ CABIN JOHN RD
  • NEWINGTON FRST AVE@FALLING LEAF RD
  • NEWINGTON FIRST AVE @ SUMMER BREEZE
  • NEWINGTON FRST AVE@TREASURE TREE CT
  • NEWINGTON FRST AVE @ WILLOWDALE CT
  • NEW GUINEA RD @ COLONY VIEW DR
  • NORTH KINGS HWY @ FAIRHAVEN AVE
  • NORTH KINGS HWY @ FAIRHAVEN AVE
  • BACKLICK RD @ CUMBERLAND AVE
  • NORTH KINGS HWY @ FORT DR
  • NORTH KINGS HWY @ FORT DR
  • N KINGS HWY @ 6000 N KINGS HWY
  • NORTH KINGS HWY @ JAMAICA DR
  • NORTH KINGS HWY @ POAG ST
  • NORTH KINGS HWY @ SCHOOL ST
  • NORTON RD @ KINGS CROSS RD
  • NORTON RD @ KINGS CROSS RD
  • NORTHUMBERLAND RD @ LAKE PLEASANT D
  • N SHORE DR @ NORTHGATE SQ
  • BACKLICK RD @ EDGEBROOK DR
  • NORTHUMBERLAND RD @ ROLLING RD
  • N SHORE DR @ BECONTREE LA
  • N SHORE DR @ CAMERON CRESCENT DR
  • N SHORE DR @ LAKE ANNE VILLAGE CTR
  • N SHORE DR @ CLUBHOUSE RD
  • N SHORE DR @ N SHORE DR
  • N SHORE DR @ CHARTER OAK CT
  • N SHORE DR @ CHARTER OAK CT
  • N SHORE DR @ FAIRWAY DR
  • N SHORE DR @ FAIRWAY DR
  • BACKLICK RD @ JAYHAWK ST
  • N SHORE DR @ FOREST EDGE DR
  • N SHORE DR @ GREENMONT CT
  • N SHORE DR @ GREENMONT CT
  • N SHORE DR @ GOLF VIEW CT
  • N SHORE DR @ HICKORY CL
  • N SHORE DR @ IVY OAK SQ N
  • N SHORE DR @ IVY OAK SQ
  • N SHORE DR @ IVY OAK SQ S
  • N SHORE DR @ LINKS DR E
  • N SHORE DR @ LINKS DR E
  • BACKLICK RD @ ESSEX AVE
  • N SHORE DR @ LINKS DR W
  • N SHORE DR @ LINKS DR W
  • N SHORE DR @ MOORINGS DR
  • INOVA MT VERNON HOSPITAL
  • N SHORE DR @ MAPLE RIDGE RD
  • N SHORE DR @ WASHINGTON PLZ W
  • N SHORE DR @ NORTHGATE SQ
  • N SHORE DR @ CLUBHOUSE RD
  • N SHORE DR @ TEMPORARY RD
  • N SHORE DR @ OUTLET RD
  • BACKLICK RD @ FLOYD AVE
  • N SHORE DR @ WEDGE DR
  • N SHORE DR @ RING RD
  • N SHORE DR @ RING RD
  • N SHORE DR @ LAKE ANNE VILLAGE CTR
  • N SHORE DR @ WATERVIEW CL
  • N SHORE DR @ WEDGE DR
  • N SHORE DR @ WIEHLE AVE
  • N SHORE DR @ WIEHLE AVE
  • BACKLICK@FRANCONIA SPRINGFIELD PKWY
  • N SHORE DR @ FELLOWSHIP SQ
  • N SHORE DR @ WASHINGTON PLZ
  • LAKE ANNE FELLOWSHIP HOUSE
  • NORTH SHORE DR @ WAINWRIGHT DR (N)
  • N SHORE DR @ WAINWRIGHT DR N
  • NORTH SHORE DR @ WAINWRIGHT DR (SOU
  • NORTH SHORE DR @ WAINWRIGHT DR (SOU
  • NUTLEY ST @ COURTHOUSE RD
  • NUTLEY ST @ COURTHOUSE RD
  • NUTLEY ST @ KINGSLEY RD
  • MOUNT VERNON HWY @ BATTERSEA LN (N)
  • NUTLEY ST @ KINGSLEY RD
  • NUTLEY ST @ ROLAND ST
  • NUTLEY ST @ ROLAND ST
  • NUTLEY ST @ TAPAWINGO RD
  • NUTLEY ST @ TAPAWINGO RD
  • OLD KEENE MILL RD @ AINSWORTH AVE
  • OLD KEENE MILL RD @ AINSWORTH AVE
  • OLD KEENE MILL RD @ BARDU AVE
  • OLD KEENE MILL RD @ BYRON AVE
  • OLD KEENE MILL RD @ CARRLEIGH PKWY
  • BACKLICK RD @ GALESVILLE PL
  • OLD KEENE MILL RD @ CARRLEIGH PKWY
  • OLD KEENE MILL RD @ COMMERCE ST
  • OLD KEENE MILL RD @ ENGLISH IVY CT
  • OLD KEENE MILL RD @ FIELD MASTER DR
  • OLD KEENE MILL RD @ GREELEY BLVD
  • OLD KEENE MILL RD @ GREELEY BLVD
  • OLD KEENE MILL RD @ HARWOOD PL
  • OLD KEENE MILL RD @ HARWOOD PL
  • OLD KEENE MILL RD @ HANOVER AVE
  • OLD KEENE MILL RD @ WESTMORE DR E
  • BACKLICK RD @ HECHINGER DR
  • OLD KEENE MILL RD @ HUNTSMAN BLVD
  • OLD KEENE MILL RD@HUNTER VILLAGE DR
  • OLD KEENE MILL RD @ JANSEN DR
  • OLD KEENE MILL RD @ JANSEN DR
  • OLD KEENE MILL RD @ KEENE DR
  • OLD KEENE MILL RD @ MILLWOOD DR
  • OLD KEENE MILL RD @ ROLLING RD
  • OLD KEENE MILL RD @ KEENE MILL CTR
  • OLD KEENE MILL RD @ ROLLING RD
  • BACKLICK RD @ HIGHLAND ST
  • OLD KEENE MILL RD @ TIVERTON DR
  • OLD KEENE MILL RD @ WESTMORE DR W
  • OLD KEENE MILL RD @ WYNGATE DR
  • OX TR @ JOSEPH SIEWICK
  • OX TR @ WEST OX RD
  • THE PARKWAY @ AUSTIN AVE
  • BACKLICK RD @ INDUSTRIAL RD
  • PARK AVE @ BALLOU ST
  • PARK AVE @ BRANCH DR
  • PARK AVE @ BRANCH DR
  • THE PARKWAY @ DORSET DR
  • THE PARKWAY @ DORSET DR
  • PARK AVE @ DRANESVILLE RD
  • THE PARKWAY @ GENTELE CT
  • PARK AVE @ GRANT ST
  • PARK AVE @ GRANT ST
  • PARCHER AVE @ HUSTON PL
  • BACKLICK RD @ JAYHAWK ST
  • PARCHER AVE @ SPRINGER DR W
  • THE PARKWAY @ MEMORIAL ST
  • THE PARKWAY @ PROSPECT TER
  • THE PARKWAY @ PROSPECT TER
  • and 2869 more (see the full list on the map or in the GeoJSON)

Over time

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

2026-07-25: 61.32026-07-30: 61.32026-07-31: 61.32026-08-01: 61.3
Show the numbers
Overall score by check, with the change from the previous check
CheckScoreChange
2026-07-2561.3 first check
2026-07-3061.3 no change
2026-07-3161.3 no change
2026-08-0161.3 no change

What changed since your last check

  • Correctness no change
  • Freshness no change
  • Rider experience no change

What changed in this feed

Overall grade and score held steady 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

13 findings, ordered by severity.

Show every finding
  • Error674 instances

    Block trips with overlapping stop times (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'block_trips_with_overlapping_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Finding code: block_trips_with_overlapping_stop_times · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning3094 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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning2894 instances

    2894 of 3119 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)

  • Warning593 instances

    593 of 9620 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)

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

  • 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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning1 instance

    Some files leave out fields that GTFS asks for but does not require.

    Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.

    Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)

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

  • Warning1 instance

    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)

  • Warning1 instance

    The feed contains route shapes no trip uses.

    Harmless to riders, but it bloats the feed and suggests stale export data.

    Fix: Turn on 'remove unused shapes' (or the like) in your export tool. (One setting.)

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

  • Info3100 instances

    About 3100 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 · See GTFS Best Practices (opens GTFS Best Practices on an external site)

  • Info11 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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Info3 instances

    Service extends far in the future (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'service_extends_far_in_the_future' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Finding code: service_extends_far_in_the_future · 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).

    Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.

    Fix: Add feed_contact_email to feed_info.txt. (One field.)

    Finding code: scorecard_no_feed_contact · Read the fix guide · 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. 1 validator error to resolve.

Published Ready
Published at a public URL.
Valid Needs attention
1 validator error to resolve.
Current Ready
Service data covers the next 791 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 9620 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

This feed is close to the conformance mark. 1 validator error to resolve. States wheelchair access on 7% of stops and 94% of trips; the mark needs 90% of each.

Valid Not yet
1 validator error to resolve.
Current Met
Service data covers the next 791 days.
Accessible Not yet
States wheelchair access on 7% of stops and 94% 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.

  • 1 of 3119 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 791 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 674 validator errors, the other thing Maps checks at onboarding; the findings below name each fix.

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 45 / 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 54 / 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.

Fairfax Connector 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/fairfax-connector/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.