Feed status · checked 2026-08-01
Fredericksburg Regional Transit
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in Virginia.
A data-quality and completeness lens to help an agency improve its GTFS feed. Not an official compliance determination from any transit program. New to this? How to read your scorecard. Interactive view of this scorecard. Rubric v1.3, validator 8.0.1.
Checked for changes 16 hours ago; last fetch returned HTTP 400.
Measured 3 of 4 score categories from the Mobility Database's mirror copy of the feed.
How we measured this
Confidence in this measurement: provisional.
- Realtime quality was not measured this run. It does not count against the grade.
- The agency's own feed URL was unreachable, so the Mobility Database's hosted mirror copy was scored instead.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.Likely your export tool
Service data ended 944 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
⏱ Usually one export setting; export on a schedule so it never lapses again.worth about +100 points in its category
Review the rule documentation for 'foreign_key_violation' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Foreign key violation (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +12 points in its category
Review the rule documentation for 'duplicate_key' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Duplicate key (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +12 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
- Service data ended 944 day(s) ago.
- Next action
- Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service 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
- Feed evidence
- Foreign key violation (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'foreign_key_violation' 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
- Feed evidence
- Duplicate key (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'duplicate_key' 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.
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. · 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.
Review the rule documentation for 'foreign_key_violation' 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.
Review the rule documentation for 'duplicate_key' 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.
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 was 944 days ago.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 100% 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.
Send the agency a note
Supporting this agency? Copy this and email it to them. It names what lapsed, why it matters to riders, and the one setting to change.
Score by category
The MobilityData validator flagged 12 kinds of issue across 47 instances (9 error, 36 warning, 2 informational).
Service data ended 944 day(s) ago. Trip planners have likely already dropped this feed.
0% of stops state wheelchair accessibility (0% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
1 accessibility depth signal
295 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Central Park Blvd. @ Funland", "Fall Hill Ave. @ Forest Village Apts.", "Train Station (Caroline 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.
Fares are applied to trips.
Not scored yet. Nothing here counts against the grade.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 320 stops.
The route and stop data is ready below. Load the map only when you want the geographic view. It uses additional data.
Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- D1 (green)
- D2 (green)
- D3 (green)
- D4 (green)
- D5 (green)
- D6 (green)
- F1 (green)
- F2 (green)
- F3 (green)
- F4 (green)
- F5 (green)
- S1 (green)
- S4 (green)
- S5 (green)
| Route | Type | Line color |
|---|---|---|
| D1 Stafford 1 | Bus | green |
| D2 Stafford 2 | Bus | green |
| D3 Stafford 3 | Bus | green |
| D4 Stafford 4 | Bus | green |
| D5 Stafford 5 | Bus | green |
| D6 Stafford 6 | Bus | green |
| F1 Fredericksburg 1 | Bus | green |
| F2 Fredericksburg 2 | Bus | green |
| F3 Fredericksburg 3 | Bus | green |
| F4 Fredericksburg 4 | Bus | green |
| F5 Fredericksburg 5 | Bus | green |
| S1 Spotsylvania 1 | Bus | green |
| S4 Spotsylvania 4 | Bus | green |
| S5 Spotsylvania 5 | Bus | green |
List every stop
- FRED Central
- Cowan Blvd. @ Madonna House
- Tidewater Trail @ Mansfield St.
- Airport Ave. / South St.
- Howard Ave. / South St.
- Howard Ave. / Mayfield Ave.
- Tyler St. / Myrick St.
- Hazel Hill Apts.
- Dixon St. / Princess Anne St.
- Dixon St. / Charles St.
- Jefferson Davis Hwy. @ Townsend Square
- Princess Anne St. / Hanover St. (City Hall)
- Princess Anne St. / George St.
- William St. / Prince Edward St.
- Amelia St. / Prince Edward St.
- Amelia St. / Douglas St.
- William St. / Kenmore Ave.
- William St. / Barton St.
- Littlepage St. / William St.
- Jackson St. @ RACSB & Health Dept.
- Stafford Ave. / Dandridge St. (NB)
- Stafford Ave. / Dandridge St. (SB)
- College Ave. / Parcell St.
- College Ave. / Rowe St.
- Monroe St. / Kenmore Ave.
- Caroline St. @ Executive Plaza / Parking Garage
- Princess Anne St. / Lewis St.
- Caroline St. / Charlotte St. (Visitors Center)
- Caroline St. / William St.
- Caroline St. @ Rappahannock Regional Library
- Princess Anne St. / Hawke St.
- Fall Hill Ave. / Stuart St.
- Tidewater Trail @ River Club Shopping Center
- Fall Hill Ave. / Germania St.
- Geico
- Fall Hill Apts. @ Clubhouse
- Kennedy Ln. @ 7/11
- Fall Hill Ave. / Woodford St.
- Fall Hill Ave. / Hanson Ave.
- Princess Anne St. / Hunter St. (Carl's Ice Cream)
- Princess Anne St. / Ford St. (Dowling Signs)
- Fall Hill Ave. @ Crestview Apts.
- Altoona Dr. @ Greenbrier Shopping Center
- Fall Hill Ave. @ Fall Hill Apts.
- Fall Hill Ave. @ Heritage Park Apts.
- Bragg Hill Dr. @ Bragg Hill Family Life Center
- Spotsylvania Crossing S/C @ K-Mart
- Fall Hill Ave. @ Fredericksburg Shopping Center
- Mary Washington Blvd. @ Snowden Office Park
- Tompkins-Martin / Ambulatory Service
- Jefferson Davis Hwy. @ Stratford Square Apts.
- Eagle Village Center @ Giant
- Trade St. @ Hospitality House / Outback
- Bragg Hill Dr. / Brighton Sq.
- Dixon St. @ Dixon Street Park
- Brittany Cmns Blvd. @ Enoch George Manor
- Jefferson Davis Hwy. / Kings Mill Dr.
- Jefferson Davis Hwy. @ Wellington Lakes Apts.
- Tidewater Trail & Church St.
- Jefferson Davis Hwy. / Loren Dr.
- Loren Dr. / Industrial Dr.
- Lee's Hill Center @ Ruby Tuesday
- The Shops at Lee's Hill @ Food Lion
- Lee's Hill Professional Center
- Spotsylvania Ave. @ Truong / Friendly's
- Falcon Dr. / Carr Dr.
- Falcon Dr. / Columbia Dr.
- Olde Greenwich Dr @ St. Vincent De Paul
- Trade St. @ Target
- Lafayette Blvd. / Falcon Dr. @ CVS
- Lafayette Blvd. / Redwood Dr.
- Lafayette Blvd. / Fleming St.
- Lafayette Blvd. / Hill St.
- Lafayette Blvd. @ Sheetz
- Thurman Brisben Center / RGI Laundry
- Lafayette Blvd. / Hillcrest Dr.
- Spotsylvania Towne Centre
- Lafayette Blvd. @ Belmans Plaza
- Lafayette Blvd. @ Wellington Woods Apts.
- Lafayette Blvd. @ Battlefield Visitor Ctr.
- Lafayette Blvd. / Littlepage St.
- Lafayette Blvd. @ Roxbury Garden Ctr.
- Lafayette Blvd. / Jackson St.
- Charlotte St. / Lee Ave.
- Central Park Blvd. @ Funland
- Meadows Apts. @ Salem Run
- Littlepage St. / Hanover St. (SB)
- Littlepage St. / Hanover St. (NB)
- Dixon St. / Bowman Dr.
- Stoney Creek Dr. / Ballantraye Dr.
- Central Park @ Lowe's
- Service Road / Hospital Dr. @ Parking Garage
- Central Park @ Kohl's
- Southpoint II @ 7/11
- Central Park @ Santa Fe Car Wash
- Central Park @ Barnes & Noble
- Central Park Blvd. / Trade St.
- Central Park @ Wal-Mart
- Central Park @ Toys 'R Us
- Central Park @ Regal Fredericksburg
- Taskforce Dr. @ Bed Bath & Beyond
- Heatherstone Office Park
- Taskforce Dr. / Shalaby Way
- Castlebridge Rd. @ Salem Run Apts.
- Salem Church Rd. / Salem Run Blvd.
- Salem Church Rd. @ Salem Church Library
- Kennedy Ln. / Roosevelt Rd. (NB)
- Kennedy Ln. / Roosevelt Rd. (SB)
- Kennedy Ln. / Eisenhower Ln. (SB)
- Kennedy Ln. / Rutherford Dr. (SB)
- Kennedy Ln. / Rutherford Dr. (NB)
- Kennedy Ln. / Eisenhower Ln. (NB)
- Salem Church Crossing / Commuter Lot
- Kennedy Ln. / Plank Rd.
- Health Center Ln. @ Cancer Center
- Kilarney Dr. / Route 3
- Kilarney Dr. / Plank Rd.
- Kilarney Dr. / McNamara Dr.
- Kilarney Dr. / Blarney St.
- Kilarney Dr. / Ohara Ct.
- Loren Dr. & Fleming St.
- Tara Dr. / Fitzpatrick Ct.
- Harrison Rd. @ Meadow Park Dr. (NB)
- Harrison Rd. @ Meadow Park Dr. (SB)
- Harrison Rd. / Piedmont Dr.
- Harrison Rd. @ CVS
- Salem Station Blvd. @ Queens Mill
- Salem Station Blvd. @ Kings Crest
- Salem Station Blvd. / Sunburst Ln.
- Salem Station Blvd. / Salem Village Dr. #2
- Salem Station Blvd. @ Avalon Apts.
- Hilltop Plaza @ Giant Food
- Salem Station Blvd. / Salem Village Dr. #1
- Leavells Rd. / Oak Grove Dr.
- Leavells Rd. / Massaponax Dr.
- Leavells Rd. / Cambridge Dr.
- Leavells Rd. / Leavells Crossing Dr.
- Hilltop Plaza Way @ Cuts for Mutts
- George Town Dr. @ Burger King
- Service Road / Leavells Rd. @ Car Wash
- Leavells Rd. / Courthouse Rd. @ 7-11
- Leavells Rd. / DeVonne Dr.
- Lee's Hill Center @ Spotsylvania Ave
- Ballantraye Dr. / Gideon Ct. (EB)
- Southpoint II @ Wal-Mart
- Ballantraye Dr. / Gideon Ct. (WB)
- Cosner's Corner Shopping Center
- Spotsylvania Pkwy. @ Spotsylvania Regional Medical Ctr.
- Chancellor Shopping Center @ Aldi
- Spotsylvania Pkwy. @ Jo-Ann Fabrics
- Central Park @ Office Depot
- Chancellor Shopping Center @ Weis Markets
- Rt. 208 @ Marshall Center
- Carl D. Silver Pkwy. @ Wegmans
- Courthouse Village
- Carol Ln. @ Pratt Medical Center
- Brittany Cmns Blvd. @ Asbury Manor
- Courtland Commons @ Food Lion
- Chatham Heights Rd. @ Rappahannock Optical
- Mary Washington Hospital (Main Entrance)
- Hardee St. / General Dr.
- R. E. Lee Dr. / Crismond Ln.
- Brock Rd. @ RACSB
- Holbart Building / Judicial Center
- Courthouse Rd. @ Git-N-Go
- Brittany Commons Blvd. @ Brittany Commons Apts.
- Falcon Dr. / Carr Dr.
- Salem Church Rd. @ Alexander Heights
- Massaponax Outlet Center
- Breezewood S/C @ Bottom Dollar
- Southpoint Plaza Way @ Burger King
- Courthouse Rd. @ Wawa
- Southpoint Centre Blvd. / Southpoint Pkwy.
- Southpoint Centre Blvd. @ DMV
- Southpoint Pkwy. @ Visitors Center
- Mills Dr. / Cosner Dr.
- Lee Hill School Rd. / Plaza View Way
- Germanna Point Dr. / Cotter Rd.
- Germanna Community College
- Germanna Point Dr. / Matti Hill Ct.
- Old Dominion Pkwy. / Lee Hill School Rd.
- Old Dominion Pkwy. @ Lee's Hill Clubhouse
- Monticello St. / Fendale Ln.
- Lee Hill School Rd. / Monticello St.
- Lee Hill School Rd. / Ashley Dawn Ct.
- Cosner Dr. @ Massaponax Medical Park
- Spotsylvania Parkway @ Pratt Medical
- Hospital Blvd. / Mills Dr.
- Hospital Blvd. @ The Havens
- Lee Hill School Rd. @ Timber Ridge
- Princess Anne St. / Wolfe St. (Post Office)
- Airport Rd. / Oldfield St. (Fairgrounds)
- Mary Washington Blvd. @ CVS
- Westwood Shopping Center @ Staples
- Aquia Towne Center
- Washington Ave. / Mary Ball St.
- Fall Hill Ave. / Virginia Ave.
- Breezewood S/C @ Dollar General
- Jackson St. @ RACSB / Health Dept.
- Spotslee Dr. / Hardee St.
- Lassen Ln. / Lafayette Blvd.
- Lee's Hill Professional Center
- William St. / Kenmore Ave.
- Fall Hill Ave. @ Forest Village Apts.
- Stafford Athletic Club
- Washington Square Center @ Wal-Mart
- Stafford Market Place @ T.J. Maxx
- Brafferton Shopping Center
- Greenspring Rd. @ Liberty Lanes Bowling
- Pike Pl. / Staffordboro Blvd.
- Aquia Business Park
- Stafford Market Place @ Center Point
- Garrisonville Rd. @ East Coast Gas Station
- Garrisonville Rd. @ Medical Center of Stafford
- Garrisonville Rd. @ DMV
- Furnace Rd. / Garrisonville Rd.
- Choptank Rd. / Vista Woods Rd.
- Vista Woods Rd. / Stevens Rd.
- Choptank Rd. / Huckstep Ave.
- Patton Dr. @ Urgent Care Center
- Kings Hwy. @ Ferry Farm Shopping Center
- Rte. 1 @ Horse Barn & Motel
- Rte. 1 @ France Farm Produce and Nursery
- Rte. 1 @ Perchwood Dr.
- Rte. 1 @ Sage Ln. (Penny Industrial Park)
- Rte. 1 @ Stafford High School
- Garrisonville Rd. @ North Stafford H.S.
- Little Whim Ln. / Pribble Ln.
- Town and County Dr. @ Giant
- Sherwood Dr. / Edwards Dr.
- Town & County Dr. / Ferry Rd.
- Sherwood Dr. / Adam Ct.
- Sherwood Dr. / Culpeper St.
- Chatham Heights Rd. / Marion St.
- Culpeper St. / Greenwood Dr.
- Deacon Rd. @ Woodlawn Shopping Center
- Butler Rd. @ YMCA
- Stafford Market Place @ Bed Bath & Beyond
- Staffordboro Dr. @ Commuter Lot
- Garrison Woods Rd. @ Cul-de-sac
- Stafford Ave. / Buckner St.
- William St. / Stafford Ave.
- Commerce St. @ Joe's Crab Shack
- Central Park @ O'Charley's
- Central Park @ Krispy Kreme
- Warrenton Rd. / Quarels Rd.
- Olde Forge Dr. / Warrenton Rd. (SB)
- Olde Forge Dr. / Warrenton Rd. (NB)
- Warrenton Rd. / McLane Dr. @ Clarion Inn
- Warrenton Rd. / Falls Run Dr.
- and 70 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.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 26.4 | first check |
| 2026-07-30 | 26.4 | no change |
| 2026-07-31 | 26.4 | no change |
| 2026-08-01 | 26.4 | 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
16 findings, ordered by severity.
Show every finding
- Error4 instances
Foreign key violation (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'foreign_key_violation' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: foreign_key_violation · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error2 instances
Duplicate key (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'duplicate_key' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: duplicate_key · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error2 instances
Invalid url (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'invalid_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: invalid_url · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error1 instance
Invalid row length (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'invalid_row_length' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: invalid_row_length · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error1 instance
Service data ended 944 day(s) ago.
When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
Fix: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. (Usually one export setting; export on a schedule so it never lapses again.)
Finding code: scorecard_feed_expired · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning322 instances
322 of 322 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)
- Warning148 instances
148 of 171 trips lack rider-facing destination or direction text.
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 · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning24 instances
Equal shape distance diff coordinates distance below threshold (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'equal_shape_distance_diff_coordinates_distance_below_threshold' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: equal_shape_distance_diff_coordinates_distance_below_threshold · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning5 instances
Some service calendars in the feed have already ended.
Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)
Finding code: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
Some trips serve fewer than two stops.
A trip with one stop can't be ridden; planners ignore it and it may signal an export problem.
Fix: Check the flagged trips in your scheduling software; remove them or restore their missing stops. (Worth a vendor question if it appears often.)
Finding code: unusable_trip · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
Unused trip (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unused_trip' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: unused_trip · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
This feed's service calendar runs out within the next 7 days.
When the calendar ends, Google Maps and other trip planners drop your agency entirely. Riders see no service at all.
Fix: Export and publish an updated GTFS feed that covers at least the next 30 days of service. (Usually a re-export from your scheduling software.)
Finding code: feed_expiration_date7_days · Read the fix guide · 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
Many of the feed's trips don't run at all in the next 7 days.
It usually means old service periods are still in the export, making the feed bigger and harder to check.
Fix: Trim past service periods the next time you export. (One setting in most export tools.)
Finding code: trip_coverage_not_active_for_next7_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info2 instances
Unsorted stop times (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unsorted_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: unsorted_stop_times · 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 Not ready
Resolve this before you certify on the D-10. 4 validator errors to resolve. Service data expired 944 days ago, so FTA would find the link out of date.
- Published Ready
- Published at a public URL.
- Valid Needs attention
- 4 validator errors to resolve.
- Current Not ready
- Service data expired 944 days ago, so FTA would find the link out of date.
- 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 171 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. 4 validator errors to resolve. Service data expired 944 days ago. States wheelchair access on 0% of stops and 100% of trips; the mark needs 90% of each.
- Valid Not yet
- 4 validator errors to resolve.
- Current Not yet
- Service data expired 944 days ago.
- Accessible Not yet
- States wheelchair access on 0% of stops and 100% 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.
- 2 of 171 trips list fewer than two stops. A trip with one stop has no leg a rider can ride; trip planners can't route anyone on it, so the service effectively does not exist. Check your scheduling export: every trip should list each stop it calls at, in order, with times.
- 5 of 322 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.
Below the Google and Apple Maps four-week coverage bar. This feed's last day of service has passed, so Google and Apple Maps will stop showing your agency. Re-export with a calendar that covers at least the next four weeks. The feed also carries 9 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 22 / 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 0 / 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.
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/fredericksburg-regional-transit/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.