Prep for a call: printable one-page brief · For your board packet: printable one-pager · Fix log: every issue this feed has cleared · Compare with another agency · Watch this feed: get an email before it expires
Feed status · checked 2026-07-09
Frederick County TransIT
Based on the feed this agency publishes
down 6.3 since 2026-07-08
Ahead of 36% of all tracked agencies and 34% of mid-size agencies. Operates in Maryland.
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.1, validator 8.0.1.
Checked for changes 15 minutes ago; last changed 15 minutes ago.
Measured 4 of 4 score categories from the agency's own feed.
How we measured this
Confidence in this measurement: high.
- All four score categories were measured this run.
- Realtime was sampled in one bounded window of 6 snapshots.
- 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
Review the rule documentation for 'stop_time_with_arrival_before_previous_departure_time' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Stop time with arrival before previous departure time (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +12 points
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 +12 points
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
Check the service alerts endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
The service alerts realtime feed failed during sampling. When this feed is down, riders see scheduled times presented as if they were live.
⏱ Usually a vendor support ticket.worth about +8 points
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.
Close the loop on each fix. Read the guide, make the change in your tool, and let the next run verify it — the scorecard shows the fix; the agency publishes it.
Review the rule documentation for 'stop_time_with_arrival_before_previous_departure_time' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Make the change. This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. See this feed's dated fix log.
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. This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. See this feed's dated fix log.
Check the service alerts endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. · Read the fix guide
Make the change. This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. See this feed's dated fix log.
Send Passio a fix request
This feed is generated by your Passio system. Copy this and send it to your Passio contact; the fixes apply to the route and stop data behind your AVL setup. Each fix names the validator notice and a guide link.
Score by category
The MobilityData validator flagged 10 kinds of issue across 70 instances (3 error, 56 warning, 11 informational).
Service data covers the next 30 days.
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 not published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
5 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (40, 60, 61, EFS, ETS).
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.
16 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Bentz Street at Dill Avenue/4th Street", "Broadband Drive at Progress Drive (Riverside Corporate Park/Wells Fargo)", "Church St at CVS", 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.
Sampled 6 times: 2 of 3 feeds healthy; 0.0% of scheduled trips had live predictions.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 10 (yellow)
- 20 (green)
- 40 (red)
- 50 (yellow)
- 51 (blue)
- 60 (teal)
- 61 (orange)
- 65 (teal)
- 80 (purple)
- ETS (gray)
- BJS (green)
- POR (brown)
- WLK (brown)
- 85 (gray)
- EFS (pink)
- NFS (purple)
- 15 (teal)
| Route | Type | Line color |
|---|---|---|
| 10 10 Connector | Bus | yellow |
| 20 20 Connector | Bus | green |
| 40 40 Connector | Bus | red |
| 50 50 Connector | Bus | yellow |
| 51 51 Connector | Bus | blue |
| 60 60 Connector | Bus | teal |
| 61 61 Connector | Bus | orange |
| 65 65 Connector | Bus | teal |
| 80 80 Connector | Bus | purple |
| ETS Emmitsburg Thurmont Shuttle | Bus | gray |
| BJS Brunswick Jefferson Shuttle | Bus | green |
| POR Point of Rocks Meet-the-MARC Shuttle | Bus | brown |
| WLK Walkersville Meet-the-MARC Shuttle | Bus | brown |
| 85 Route 85 Shuttle | Bus | gray |
| EFS East Frederick Shuttle | Bus | pink |
| NFS North Frederick Shuttle | Bus | purple |
| 15 15 Connector | Bus | teal |
This feed has 392 stops.
List every stop
- Waverley Transfer Facility
- Frederick Towne Mall at Boscov's South Entrance
- Golden Mile Marketplace at Big Lots
- Golden Mile Marketplace at McCain Drive
- McCain Drive at David Lane Park
- McCain Drive at Hillcrest Drive
- Hillcrest Drive at Riggs Court
- Hillcrest Drive at Seneca Drive
- Seneca Drive at Himes Avenue
- Himes Avenue at Coralberry Court
- Himes Avenue at Bradley Court
- Ballenger Creek Plaza Shopping Center
- Farmbrook Drive at Glenrock Drive
- Farmbrook Drive at Farmhouse Drive
- Farmbrook Drive at Farmbrook Court
- Farmbrook Drive at Hames Court
- Farmbrook Drive at Crestwood Boulevard
- Crestwood Boulevard at Crabapple Drive
- Crestwood Boulevard at New Design Road
- New Design Road at Arbor Drive
- Kingsbrook Crossing Shopping Center
- Corporate Drive at New Design Road
- Francis Scott Key Mall
- Clarion Inn Frederick Event Center
- New Technology Way at Spectrum Drive eb
- Spectrum Drive at Garner Hotel
- Spectrum Drive at Golden Corral
- Spectrum Drive at M&T
- 5255 Westview Drive
- Crestwood Boulevard at Bank Court
- Crestwood Boulevard at Foxcroft Drive
- Walmart (Guilford)
- Kohl's (shelter)
- Crestwood Boulevard at Burning Bush Drive (East)
- Crestwood Boulevard at Burning Bush Drive (West)
- Crestwood Boulevard at Ballenger Creek Pike (West)
- Cawley Drive at shelter
- Ballenger Center Drive at Ballenger Creek Pike
- Solarex Court
- Himes Avenue at Primus Court
- Himes Avenue at Coralberry Court
- Himes Avenue at Seneca Drive
- Seneca Drive at Hillcrest Drive
- Hillcrest Drive at Hill Street
- Hillcrest Drive at McCain Drive
- McCain Drive at Lauren Court South
- McCain Drive at Orchard Way
- Transit Center - MARC Train Station
- South Carroll Street at East All Saints Street
- Clarke Place at South Market Street
- South Market Street at The Arc (shelter)
- Industry Lane south of Guilford Drive (after left turn)
- Industry Lane at Grove Road
- Grove Road at Route 85
- Grove Road at Route 85 (McDonalds)
- Target at Genstar Drive
- New Technology Way at Spectrum Drive wb
- Grove Road at Industry Lane
- Industry Lane at Guilford Drive
- Route 355/South Market Street at Noland
- East South Street at Carroll Street X
- Frederick Towne Mall at Meet-the-MARC stop on Waverley
- Waverley Drive at steps to strip mall
- Key Parkway across from Elmwood Terrace Apartments
- Key Parkway at Hickory Hill Apartments
- Key Parkway at Old Camp Road
- Old Camp Road at Stonegate Park
- West Patrick Street at Norva Avenue
- West Patrick Street at James Street
- West South Street at Thomas Avenue
- West South Street at Center Street
- South Street at South Market Street
- North Market Street at 4th Street
- Square Corner (East Patrick Street at North Market Street)
- North Market Street at 3rd Street
- North Market Street at 6th Street
- West 7th Street at Motter Avenue/Bentz Street
- West 7th Street at Toll House Avenue- Hospital
- West 7th Street at Taney Avenue
- Military Road at Fort Detrick
- Old Farm Drive at Old Farm Station Shopping Center
- Walnut Ridge Shopping Center at Food Lion
- Tuscanney Drive at Greenspring Place
- Tuscanney Drive at Greenleaf Drive East
- Greenleaf Drive East at Christophers Crossing
- Whittier Drive at Somerford
- Whittier Drive across from Wetherburne Way
- Greenleaf Drive East at Tuscanney Drive
- Tuscanney Drive at Carroll Creek View Court
- Tuscanney Drive at Rosemont Avenue- CVS
- Rosemont Avenue at Rocky Springs Road
- Rosemont Avenue at Citizens Nursing Home
- Rosemont Avenue at Pizza Hut
- Baughman's Lane at Carroll Park Manor
- Key Pkwy at Bel Aire La Westbound
- Key Parkway west of Willowdale Drive
- Key Parkway at Baker Place Apartments
- North McCain Drive at north entrance to Home Depot
- Baughman's Lane at Belle Aire Farm
- Baughman's Lane at Rock Creek Park
- West Patrick Street at Bentz Street
- West Patrick Street at Jefferson Street
- West Patrick Street at College Terrace
- West Patrick Street at Kline Boulevard
- Frederick County Square
- Westridge Plaza at H Mart
- Frederick Shoppers World at Dollar General
- Willowdale Drive at Route 40
- Hillcrest Drive at Thornhill Place East
- Hillcrest Drive at Hillcrest Shopping Center South Entrance
- Hillcrest Drive at Route 40
- Transit Center - East Street Shelter
- East Patrick Street at Wisner Street
- East Patrick Street at Fairground Center
- East Patrick Street at Hamilton Avenue
- East Patrick Street at East Gate Plaza
- 75 Monocacy Boulevard- Royal Farms
- East South Street at Franklin Street
- Hillcrest Drive at Consett Place
- Hillcrest Drive at Tilman Place North
- Waverley Drive at Key Parkway
- Key Parkway at Elmwood Terrace Apartments East
- Key Parkway at McCain Drive
- Key Parkway at Willowdale Drive
- Key Parkway at Westridge Plaza (rear)
- Key Pkwy at Bel Aire La Eastbound
- Park Ridge Drive across from Creekside Apartments
- Bel Aire Lane at Schaffer Drive
- Schaffer Drive at Willowdale Drive
- Willowdale Drive at Thames Drive
- Montevue Lane at SriSai Bio Pharmeceutical
- Frederick County Health Department (shelter)
- Baughman's Lane at Walgreens
- Norva Avenue at Wyngate Drive (southbound)
- Prospect Plaza (southbound)
- Prospect Boulevard at Festival at Frederick Shopping Center South Entrance
- Center Street at Fieldpointe Boulevard
- Center Street at White Oak Place
- Center Street at Carrollton Drive
- Center Street at Madison Street
- Center Street at West South Street
- North Market Street at 8th Street
- North Market Street at YMCA
- 10th Street at Motter Avenue
- 14th Street at Motter Avenue
- Motter Avenue at Rose Hill Plaza
- Opossumtown Pike at Deervalley Drive
- Opossumtown Pike at Amber Drive shelter
- Frederick Community College shelter
- Amber Drive at Carriage Way
- Amber Drive at Hillmeade Square
- Hayward Road at Thomas Johnson Drive
- 61 Thomas Johnson Drive
- 67 Thomas Johnson Drive- North Amber Center
- 87 Thomas Johnson Drive
- 141 Thomas Johnson Drive- SRI
- 175 Thomas Johnson Drive- Columbia Bank
- Heather Ridge Drive at Country Hill Apartments (westbound)
- Heather Ridge Drive at 550 Heather Ridge Drive
- Taney Avenue at Heather Ridge Drive
- Taney Village Apartments
- Frederick Shopping Center North
- Frederick Shopping Center South- Giant Eagle
- Fairview Avenue at College Park Plaza (The Common Market)
- 9th Street at Toll House Avenue
- Motter Avenue at West 9th Street
- Motter Avenue at 7th Street
- Bentz Street at Dill Avenue/4th Street
- Bentz Street at 2nd Street
- Church Street at North Market Street
- Church Street at East Street
- Madison Street at Stine's Lane
- Madison Street at Center Street
- Center Street at Scholls Lane
- Center Street at Catoctin Avenue
- Center Street at Prospect Boulevard
- Prospect Boulevard at Carrollton Drive
- Prospect Boulevard at Festival at Frederick Shopping Center
- Prospect Boulevard at Jefferson Street
- Prospect Plaza (northbound)
- Norva Avenue at Wyngate Drive (northbound)
- Norva Avenue at West Patrick Street
- Taney Avenue at 8th Street- McDonalds
- Taney Avenue at Potomac Commons (across from Wilson Place)
- Taney Avenue at Applegate Apartments
- Taney Avenue at Frederick Senior Center
- Heather Ridge Drive at 501 Heather Ridge Drive
- Heather Ridge Drive at Country Hill Apartments (eastbound)
- Motter Avenue at 14th Street
- East 7th Street at East Street
- Spectrum Drive at Lowe's Lane
- Crestwood Boulevard at Edenton Ct
- Ballenger Center Drive at Cawley Drive
- South Carroll Street at Clarke Place
- Grove Road at Route 355
- Spectrum Drive at Route 85 - Sheetz
- Grove Road at Route 85 (Bank of America)
- South Market Street at Mount Olivet Boulevard
- West South Street at Burck Street
- North McCain Drive at Route 40
- West Patrick Street at College Avenue
- Hillcrest Drive at Pendleton Drive
- Amber Drive at Hayward Road
- Taney Avenue at Wilson Place
- 9th Street at Motter Avenue
- East Street at 9th Street
- 8th Street at North Market Street
- Baughman's Lane at Waterford Drive
- Baughman's Lane across from Carroll Park Manor
- Military Road at Meade Avenue
- Military Road at 7th Street
- 7th Street at Wilson Place
- Hayward Road (after left turn from Thomas Johnson Drive)
- Amber Drive at Millstream Drive
- Opossumtown Pike at Thomas Johnson Drive (near Stauffer Funeral Home)
- Montevue Lane across from Frederick County Health Department
- Willowdale Drive at Savage Road
- East Street at Peters Lane
- East Street at Delaware Road (Monocacy Village Shopping Center)
- 16th Street at Northampton Manor
- 16th Street at Carey Place
- 16th Street at Dogwood Drive
- 16th Street at Schifferstadt Boulevard
- Schifferstadt Boulevard at Turning Point Court
- North Market Street at Triangle Motors
- 194 Stauffer Court- Sheetz
- Broadband Drive at Progress Drive (Riverside Corporate Park/Wells Fargo)
- Shops at Monocacy (stop sign across from Little Gym)
- Shops at Monocacy at Kingfisher Drive
- Wheyfield Drive across from Wills Alley (Dearbought)
- Latham Drive at Wheyfield Drive (Dearbought)
- Stauffer Road at Dream Place (Discovery)
- Discovery Boulevard across from daycare center (Discovery)
- Discovery Boulevard at Adventure Avenue (Discovery)
- Walkers Village Shopping Center- Safeway
- Frederick Street at Main Street (downtown Walkersville)
- FCPS Food and Nutrition Services (57 West Frederick Street)
- Frederick Street at Firehouse/High School (downtown Walkersville)
- Waterside Drive at River Run Road (Waterside)
- Waterside Drive at Village Square Road (Worman's Mill)
- Waterside Drive at Caulfield Court- Worman's Mill
- Monocacy Boulevard at Frederick Health Village
- Monocacy Boulevard at Mill Pond Road
- North Market Street at Worman's Mill Court
- Schifferstadt Boulevard at Insley Circle
- Schifferstadt Boulevard at East 16th Street
- 16th Street at Dogwood Drive (southbound)
- 16th Street across from Carey Place
- 16th Street at East Street (across from Northampton)
- East Street at Peters Lane (Southbound)
- and 142 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 20 checks — down 6.3 since 2026-07-08.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-06-19 | 59.4 | first check |
| 2026-06-20 | 67.0 | up 7.6 |
| 2026-06-21 | 66.2 | down 0.8 |
| 2026-06-22 | 67.2 | up 1.0 |
| 2026-06-23 | 67.9 | up 0.7 |
| 2026-06-24 | 67.9 | no change |
| 2026-06-25 | 65.6 | down 2.3 |
| 2026-06-26 | 67.9 | up 2.3 |
| 2026-06-27 | 65.7 | down 2.2 |
| 2026-06-28 | 60.6 | down 5.1 |
| 2026-06-29 | 67.1 | up 6.5 |
| 2026-06-30 | 53.7 | down 13.4 |
| 2026-07-01 | 66.9 | up 13.2 |
| 2026-07-02 | 58.0 | down 8.9 |
| 2026-07-04 | 53.7 | down 4.3 |
| 2026-07-05 | 59.9 | up 6.2 |
| 2026-07-06 | 59.9 | no change |
| 2026-07-07 | 60.3 | up 0.4 |
| 2026-07-08 | 57.0 | down 3.3 |
| 2026-07-09 | 50.7 | down 6.3 |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
- Realtime quality down 31.9
What changed in this feed
Overall score fell 6.3 points since 2026-07-08.
The feed file was re-published since 2026-07-08.
Changed counts
- down 1 of 1 trips scheduled during the sampling window had no live predictions. (4 → 1) (scorecard_rt_trip_coverage)
Resolved since 2026-07-08 (1 finding)
- Some live predictions disagree with the schedule by more than 30 minutes. (scorecard_rt_predictions_implausible)
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
What changed over time
On 2026-06-19 this feed started at grade F. On 2026-06-20 the grade moved from F to D. On 2026-06-30 the grade moved from D to F. On 2026-07-01 the grade moved from F to D. As of 2026-07-09 it holds grade F.
A plain-language history of this feed, newest first.
- 2026-07-09 Score fell 6 points, realtime fell 32 points.
- 2026-07-08 Grade went D to F, correctness fell 8 points.
- 2026-07-07 Grade went F to D.
- 2026-07-05 Score rose 6 points, realtime rose 34 points.
- 2026-07-04 Score fell 4 points, realtime fell 22 points.
- 2026-07-02 Grade went D to F, realtime fell 17 points.
- 2026-07-01 Grade went F to D, correctness rose 36 points.
- 2026-06-30 Grade went D to F, correctness fell 36 points.
- 2026-06-29 Score rose 6 points, realtime rose 40 points.
- 2026-06-28 Score fell 5 points, realtime fell 25 points.
- 2026-06-20 Grade went F to D, realtime rose 38 points.
Everything we checked
- Error2 instances
Stop time with arrival before previous departure time (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'stop_time_with_arrival_before_previous_departure_time' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: stop_time_with_arrival_before_previous_departure_time · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error1 instance
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.)
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
Validator rule: block_trips_with_overlapping_stop_times · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error1 instance
The service alerts realtime feed failed during sampling.
When this feed is down, riders see scheduled times presented as if they were live.
Fix: Check the service alerts endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. (Usually a vendor support ticket.)
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
Validator rule: scorecard_rt_service_alerts_unreachable · Read the fix guide · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)
- Warning392 instances
392 of 392 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.)
Validator rule: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning109 instances
109 of 835 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 (most small-agency fleets are 100% accessible, so this is often a single default). (Often one default setting in your export.)
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning37 instances
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.)
Agencies here usually clear this within about 1 week (based on 11 observed fixes).
Validator rule: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning10 instances
Route long name contains short name (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'route_long_name_contains_short_name' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: route_long_name_contains_short_name · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning4 instances
Some scheduled trips move faster between stops than a bus can.
Usually a typo'd stop time; riders get arrival times no bus can meet.
Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)
Agencies here usually clear this within about 2 weeks (based on 6 observed fixes).
Validator rule: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning3 instances
Stop too far from shape using user distance (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'stop_too_far_from_shape_using_user_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 6 observed fixes).
Validator rule: stop_too_far_from_shape_using_user_distance · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some stops sit far from the route line they belong to.
Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)
Agencies here usually clear this within about 2 weeks (based on 6 observed fixes).
Validator rule: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Stops match shape out of order (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'stops_match_shape_out_of_order' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 6 observed fixes).
Validator rule: stops_match_shape_out_of_order · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
The feed contains no fare information.
Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
Fix: Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. (A small file for most flat-fare systems.)
Validator rule: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning1 instance
1 of 835 trips have no headsign.
Riders at the stop can't tell which direction a bus is going.
Fix: Populate trip_headsign to match what the bus displays. (Usually a bulk edit in your scheduling software.)
Validator rule: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning1 instance
1 of 1 trips scheduled during the sampling window had no live predictions.
Riders on those trips get schedule data dressed up as realtime. Caltrans expects every operating trip in TripUpdates.
Fix: Check with your AVL vendor that every vehicle assignment flows into TripUpdates, including school-day and tripper runs. (A vendor data-mapping question.)
Agencies here usually clear this within about 1 week (based on 82 observed fixes).
Validator rule: scorecard_rt_trip_coverage · Read the fix guide · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)
- Info6 instances
Big gap in service (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'big_gap_in_service' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 13 observed fixes).
Validator rule: big_gap_in_service · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info5 instances
Service window outside feed period (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'service_window_outside_feed_period' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 17 observed fixes).
Validator rule: service_window_outside_feed_period · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
NTD certification readiness Needs attention
This feed is close to NTD-ready. 2 validator errors to resolve. Service data runs out in 30 days; renew before you certify.
- Published Ready
- Published at a public URL.
- Valid Needs attention
- 2 validator errors to resolve.
- Current Needs attention
- Service data runs out in 30 days; renew before you certify.
- agency_id matches your NTD ID Not checked yet
- Setting your GTFS agency_id to your five-digit NTD ID is an optional way to line a feed up with its National Transit Database record. FTA links the two on your P-50 form, so it is not a required feed change. We don't have your NTD ID on file, so this is not checked yet.
- shapes.txt covers your trips Ready
- All 835 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 and confirm it once a year. This box is a heads-up on whether yours looks ready; it is not the official sign-off.
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). Aligning agency_id with your NTD ID lets the feed line up with your NTD record; the July 2025 final rule links the two on the P-50 form rather than requiring that feed change, and 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. 2 validator errors to resolve. Service data runs out in 30 days; renew to qualify. States wheelchair access on 0% of stops and 87% of trips; the mark needs 90% of each.
- Valid Not yet
- 2 validator errors to resolve.
- Current Not yet
- Service data runs out in 30 days; renew to qualify.
- Accessible Not yet
- States wheelchair access on 0% of stops and 87% 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.
- 37 of 392 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.
Realtime reliability
The realtime feed responded on 100.0% of 105 checks over the last 16 days, with 3s median lag.
Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.
Clears the Google and Apple Maps four-week coverage bar. This feed has 540 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 3 validator errors, the other thing Maps checks at onboarding; the findings below name each fix.
How this agency maps to the standards
A data-quality lens, not a compliance determination. Each category shows this feed's score and the standards it relates to: the FTA National Transit Database GTFS requirement, the MobilityData grading scheme, and the Google Transit gate. Read the full standards crosswalk.
- Correctness 47 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading: stop locations, route names and colors. Google Transit: a feed must pass validation to stay in Maps.
- Freshness 50 / 100
- The FTA National Transit Database expectation of a valid, current feed. Google Transit: an expired calendar drops the agency from Maps.
- Rider experience 58 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading: stop names and headsigns.
- Realtime quality 49 / 100
- GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.
Show your grade
Put a live badge on your agency site or feed README. It updates daily and links back to this 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/frederick-county-transit-2432/2026-07-09.json and never overwritten, pinning the grade, category scores, rubric version, validator version, and the scored feed's sha256 as they stood on 2026-07-09. Use it in a board packet, an NTD narrative, 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.