Feed status · checked 2026-08-01
Butler County Regional Transit Authority
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in Ohio.
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 80 minutes ago; last changed 41 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
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 1904 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
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
529 of 529 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 +25 points in its category
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.Likely your export tool
394 of 394 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
⏱ A default or per-trip field in your export.worth about +15 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 1904 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
- 529 of 529 stops don't say whether a wheelchair user can board there.
- Next action
- Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
- 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
- 394 of 394 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
- 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.
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.
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. · 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 was 1904 days ago.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- No fare information is published in the feed.
- 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 7 kinds of issue across 62 instances (0 error, 62 warning, 0 informational).
Service data ended 1904 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 not published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
7 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (U1, GDL, GDL SA, U1W, R4, 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.
393 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Central & Hanover SB", "Campus & Walnut SB", "Kroger at Oxford State Rd", 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.
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 529 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.
- R3 (green)
- PR (yellow)
- U3XAM (yellow)
- U3XPM (yellow)
- U3 (black)
- U3 WND (black)
- R2 (pink)
- R4 (orange)
- R6 (purple)
- U1 (orange)
- U1W (orange)
- U1W WND (orange)
- U4D WND (teal)
- U4 (teal)
- BL (teal)
- BL SA (teal)
- GDL (orange)
- GDL SA (orange)
- GRL (green)
- GRL SA (green)
- RL (red)
- RL (red)
- R1 (yellow)
| Route | Type | Line color |
|---|---|---|
| R3 Hamilton/Oxford Connector | Bus | green |
| PR Park & Ride | Bus | yellow |
| U3XAM U3 Express AM | Bus | yellow |
| U3XPM U3 Express PM | Bus | yellow |
| U3 Tollgate Loop | Bus | black |
| U3 WND U3 Tollgate Loop Weekend | Bus | black |
| R2 Oxford/Middletown Shuttle | Bus | pink |
| R4 Tri-County Shuttle | Bus | orange |
| R6 Job Connector | Bus | purple |
| U1 Campus Core | Bus | orange |
| U1W Campus Core w/Wal-Mart Flyer | Bus | orange |
| U1W WND U1W Campus Core w/Wal-Mart Flyer Weekend | Bus | orange |
| U4D WND U4D Western Campus/North Loop w/Ditmer Flyer Sunday | Bus | teal |
| U4 Western Campus/North Loop | Bus | teal |
| BL Blue Line | Bus | teal |
| BL SA Blue Line Saturday | Bus | teal |
| GDL Gold Line | Bus | orange |
| GDL SA Gold Line Saturday | Bus | orange |
| GRL Green Line | Bus | green |
| GRL SA Green Line Saturday | Bus | green |
| RL Red Line | Bus | red |
| RL Red Line Saturday | Bus | red |
| R1 Hamilton/Middletown Shuttle | Bus | yellow |
List every stop
- High & 7th WB
- Pershing & 2nd WB
- Front & Wilson NB
- County Courthouse
- Front & Chestnut SB
- 2nd & Hanover
- Port Union & LeSaint EB
- SR-747 & Devitt SB
- Tyson Foods
- Port Union & LeSaint WB
- Washington & 2nd WB
- High & East EB
- Front & Chestnut NB
- Miami Station B
- Kohl's Distribution Center Southbound
- High & Locust
- High & Erie WB
- High & Fair EB
- Chestnut Field Park & Ride
- Chestnut & Beech
- Sutphin St at Arlington Ave
- High & Fair WB
- Sutphin St at Sherman Ave EB
- Sutphin St at Sherman Ave WB
- Chestnut Place Apts.
- Market Street Station - Area A
- Miami Station D
- High & Hancock EB
- Grand Ave at Euclid St (Westtbound)
- Grand Ave at Jackson Ln
- High & University WB
- Sycamore & Tallawanda
- Grand Ave at Highview St (Eastbound)
- Campus & Chestnut SB
- Breiel Blvd at Roosevelt Blvd
- Breiel at Patrick Square
- Kemper & Hanover WB
- Town Blvd at PNC Bank
- King Library
- Kroger
- Trenton Park & Ride WB
- Main & Withrow NB
- Sycamore & College
- Laws Hall
- 9th & Main NB
- Manchester Ave at Grimes St
- Manchester Ave at Leibee St
- Manchester Ave at Iglehart St
- Manchester Ave at Clark St
- Meijer/W. Hamilton Park & Ride - to Hamilton
- Main & Brookwood EB
- Vora Technology Park Northbound
- Fairfield Crossing Park & Ride WB
- Main and Oxford State (Speedway) SB
- Main and Oxford State (Dad's Restaurant) NB
- Main St at Moose Lodge
- Main St at Diamond Loop
- Market Street Station - Area B
- Main St at Main Bar
- Main St at Pinta Ave (Northbound)
- Main St at Granada Ave
- Main St at Dollar General
- Main at Elm Grove Apts
- Main St at Cable Auto Sales
- Main St and Lafayette Ave
- Lafayette Ave and Trailbridge Apts
- Lafayette Ave and Trailbridge Apts Office
- Lafayette Ave and Minnesota St
- Minnesota St at Douglas Park
- Main St at Eighteenth Ave
- Minnesota St at Eighteenth Ave
- Minnesota St at Seventeenth Ave
- Minnesota St at Sixteenth Ave
- Main St at Sixteenth Ave
- Minnesota St at Fifteenth Ave
- McGuffey Hall
- Minnesota St at Fourteenth Ave
- Main St at Fourteenth Ave
- Woodside Blvd at Garden Ave
- Main St at Eleventh Ave
- Primary Health Solutions
- Main St at Windsor Ave
- Yankee Rd at Hanover Ave
- Miami U. - Hamilton SB
- Main St at Seventh Ave
- Main St at Sixth Ave
- Yankee Rd at Fifth Ave
- Main St at Fifth Ave
- Yankee Rd at Fourth Ave
- Broad St at Girard Ave
- Main St at Sorg Mansion
- Broad St at Middletown Public Library
- First Ave and Broad St Northbound
- Main St at Fifth/Third Bank
- MTS Transit Station
- Verity and Vail
- Main St at Manchester St
- Verity Pkwy at Manchester Ave
- Verity Pkwy at Post Office
- Main St at City Building
- Reinartz Blvd at Police Station
- Verity Pkwy at Senior High Rise
- Morris Hall
- Charles St at North Ave
- Charles St at Columbia Ave
- Charles St at Reinartz Blvd
- Charles St and Clayton
- Charles St at Van Ave
- Tytus Ave at Beech St
- Elwood St at Tytus Ave
- Tytus Ave at Auburn St
- Tytus Ave at Catalpa
- Tytus Ave at Wilmore St
- Tytus Ave at Chase Bank
- Tytus Ave and Nelbar St
- Tytus Ave and Enoch St
- Tytus Ave at Princeton St
- Tytus Ave at Eldora St
- Tytus Ave at Ohio Ave
- Jewell Ave at Lowell St
- Jewell Ave at Bryant St
- Jewell Ave at Whittier St
- Jewell Ave at Hawthorne
- Jewell Ave at Longfellow St
- Jewell Ave at Browning St
- Shelley St at Tytus Ave
- Tytus Ave at Byron St
- Tytus Ave at Longfellow St
- Tytus Ave at Hawthorne
- Tytus Ave at Whittier St
- Tytus Ave at Verity Pkwy
- Wilbraham Ave at Royal Pines Apts
- Wilbraham Ave Midway
- Wilbraham Ave at Winona St (East End)
- Northland & Tri-County WB
- Wilbraham Ave at Winona St (West End)
- Wilbraham Ave at Germantown Rd
- Wilbraham Ave at Wilmore St
- Wilbraham Ave at Malvern St
- Wilbraham Ave at Elwood St
- Elwood St at Erie Ave
- Elwood St at Verity Pkwy
- MTS Transit Station A
- Central Ave at Alley
- Northland & Tri-County EB
- Central Ave at Central Pastry
- Central Ave at Leibee St.
- Central Ave at Grimes St.
- First Ave at Moore St
- Central Ave at Dollar General
- Central Ave at McKinley (Eastbound)
- Forest Park Park & Ride Westbound
- Hamilton Enterprise Park/Bethesda EB
- Engles Corner EB
- Western Lodge
- Market St at McDonalds Restaurant
- Pleasant & Fairview SB
- First Ave at Clinton St SB
- First Ave at Curtis St SB
- Princeton Square Apts. SB
- Curtis St and Girard Ave
- Curtis St.
- Curtis St and Woodlawn Ave
- Curtis St at Parkview Ave
- Yankee Rd at Curtis St
- Yankee Rd at 14th Ave
- Yankee Rd at Kunz Ave
- Yankee Rd at Young St
- Baltimore St at Yankee Rd
- Baltimore St at Smith Ave
- Rec. Center
- Baltimore St at Lafayette Ave
- Lafayette Ave at Cherry St
- Lafayette Ave at Finley St
- Lafayette Ave at Yankee Rd
- Yankee Rd at Meadow Ave
- Yankee Rd at Pershing Ave
- Yankee Rd at Glenn Ave
- Yankee Rd First Church of God
- Nas-Car Drive Through
- Mohawk St and Waneta Ave
- S. Campus Garage
- Mohawk St at Oneka Ave
- Yankee Rd at Oneka St
- Yankee Rd at Lawn Ave
- 14th Ave at Railroad Crossing
- Baltimore St at 14th Ave
- Baltimore St at Jacoby Ave
- Baltimore St at Forest Ave
- Baltimore St and Fairmount Ave
- Baltimore St at Fairfield Ave
- Baltimore St at Girard St
- Baltimore St at First Ave
- First Ave at Baltimore
- First Ave at Garfield St
- First Ave at Grimes St
- Crawford St at First Ave (Gold)
- Crawford St at Arlington
- Crawford St at Logan Ave
- Crawford St at Sherman Ave
- Crawford St at Woodlawn Ave
- Spring & Main EB
- Crawford St at Grand Ave
- Grand Ave at Moore St.
- Grand Ave at Wilson St.
- Grand Ave at Cleveland St.
- Wicoff St. at Queen Ave
- Wicoff St. at Hill Ave
- Goldman St at Highland St.
- Goldman St at Florence St.
- Goldman St. at Orchard
- Meander Thrift Store
- Roosevelt Blvd at Kensington
- Roosevelt Blvd at Jackson Ln.
- Roosevelt Blvd at Bonita Dr.
- Shady Creek Apts
- Roosevelt Blvd at Eaton Ave
- Speedway at Breiel and Roosevelt Blvd
- Chatham Village Appts
- Bonita at Emerald Green Apts
- Bonita at Spring Grove Ln.
- Bonita Dr at Ct. Edmun
- Bonita Dr at Burbank Ave
- Burbank Ave at Ellis way
- Burbank Ave at Waynebrook St.
- Burbank Ave at Lamberton St.
- Burbank Ave at Sheffield St.
- Burbank Ave at Winton St.
- Burbank Ave at Brentwood St.
- Burbank Ave at Carolina St.
- Burbank Ave at Highland St.
- Highland St at Selden Ave
- SR-4 at Liberty-Fairfield NB
- Highland St. at Goldman Ave
- University Blvd at Woodlawn Ave
- University Ave at Logan Ave
- University Blvd at Waite St
- Manchester Ave at Webster St
- Manchester Ave at UDF
- SR-73 & Wayne-Madison EB
- University Blvd at Needler's Market
- University Blvd at Park Ln
- University Blvd at Miami University Dr
- Miami University - Middletown
- Manchester School
- Breiel Blvd at Summit Dr
- Breiel Blvd at Rosedale Rd
- State & 3rd EB
- Breiel Blvd at Mallory Dr
- Central Ave at Breiel Blvd Inbound
- and 279 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 | 36.8 | first check |
| 2026-07-30 | 36.8 | no change |
| 2026-07-31 | 36.8 | no change |
| 2026-08-01 | 36.8 | 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
14 findings, ordered by severity.
Show every finding
- Error1 instance
Service data ended 1904 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)
- Warning529 instances
529 of 529 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)
- Warning394 instances
394 of 394 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)
- Warning394 instances
394 of 394 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
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)
- Warning23 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)
- Warning5 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.)
Finding code: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning5 instances
On some trips the stops fall along the route line in a different order than the schedule lists.
Trip planners can draw the bus doubling back or skipping ahead, which confuses riders reading the map.
Fix: Check the stop order and the shape direction in your scheduling software; the shape is often drawn backwards. (A few minutes per flagged trip.)
Finding code: stops_match_shape_out_of_order · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning3 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)
- Warning1 instance
A file GTFS asks for (usually feed_info.txt) is missing.
feed_info.txt tells apps who publishes the feed and when it expires; without it nobody is warned before data goes stale.
Fix: Add feed_info.txt with publisher name, URL, language, and feed_start_date/feed_end_date. (One small file, set once in export settings.)
Finding code: missing_recommended_file · 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)
- Warning1 instance
feed_info.txt is missing its start/end dates (the file itself is absent)
Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.
Fix: Add feed_info.txt with feed_start_date and feed_end_date to your export. (Two fields, set once in export settings.)
Finding code: scorecard_missing_feed_info_dates · Read the fix guide · 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.)
Finding code: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices 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. Service data expired 1904 days ago, so FTA would find the link out of date. agency.txt has no nonblank agency_id. Every RY2026 NTD GTFS submission needs a stable value unique among the reporters represented in the feed, crosswalked to each reporter's NTD ID on the P-50 form.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Not ready
- Service data expired 1904 days ago, so FTA would find the link out of date.
- agency_id provided Not ready
- agency.txt has no nonblank agency_id. Every RY2026 NTD GTFS submission needs a stable value unique among the reporters represented in the feed, crosswalked to each reporter's NTD ID on the P-50 form.
- shapes.txt covers your trips Ready
- All 394 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. Service data expired 1904 days ago. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Not yet
- Service data expired 1904 days ago.
- Accessible Not yet
- States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.
A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 5 of 529 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.
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 68 / 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 22 / 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/butler-county-regional-transit-authority/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.