Prep for a call: printable one-page brief · For your board packet: printable one-pager · Compare with another agency · Watch this feed: get an email before it expires
Feed status · checked 2026-07-09
Athens Public Transit
Based on the feed this agency publishes
unchanged since 2026-07-08
Ahead of 35% of all tracked agencies and 33% of mid-size agencies. Operates 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.1, validator 8.0.1.
Checked for changes 4 hours ago; last fetch returned HTTP 403.
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 3112 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
Agencies here usually clear this within about 1 week (based on 18 observed fixes).
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
124 of 124 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
Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default).Likely your export tool
315 of 315 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
⏱ Often one default setting in your export.worth about +15 points
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
This feed URL points at the TransitFeeds archive, which is no longer maintained. Before any single fix, publish the feed from a live URL you control and update the listings that still point here.
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.
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. This feed URL points at the TransitFeeds archive, which is no longer maintained. Before any single fix, publish the feed from a live URL you control and update the listings that still point here.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. 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. This feed URL points at the TransitFeeds archive, which is no longer maintained. Before any single fix, publish the feed from a live URL you control and update the listings that still point here.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default). · Read the fix guide
Make the change. This feed URL points at the TransitFeeds archive, which is no longer maintained. Before any single fix, publish the feed from a live URL you control and update the listings that still point here.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
Send your vendor a fix request
This feed is served from the TransitFeeds archive, which is no longer maintained. The most useful request is publishing the current feed from a live URL, then these fixes. Each fix names 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 5 kinds of issue across 109 instances (0 error, 107 warning, 2 informational).
Service data ended 3112 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.
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.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 2 (red)
- 3 (yellow)
- 4 (purple)
- 5 (blue)
- 6 (teal)
- SL (teal)
| Route | Type | Line color |
|---|---|---|
| 2 Line 2 - Uptown/Holzer Clinic | Bus | red |
| 3 Line 3 - Andover/Market | Bus | yellow |
| 4 Line 4 - Westside/Campus/Market | Bus | purple |
| 5 Line 5 - Westside-Plains Loop - anticlockwise | Bus | blue |
| 6 Line 6 - Westside-Plains-Chauncey Loop - clockwise | Bus | teal |
| SL Summit Express Loop | Bus | teal |
This feed has 124 stops.
List every stop
- Baker Center Bus Hub
- Community Center
- O'Bleness Hospital
- 305 West Union
- West Union / Depot St
- West Union / Factory St
- West Union / Shafer
- 278 West Union
- West Union / Herrold
- West Union / Bikeway
- S.R. 682 / E 1st St
- S.R. 682 / Poston Rd
- Athens Mall
- 177 S.R. 682
- Converse / Sycamore
- Birge Dr / Bobo Ln
- County Home
- 224 Columbus Rd
- Columbus Rd / Dorr Rd
- 165 Columbus Rd
- 94 Columbus Rd
- Columbus Rd / Sunset Dr
- Lancaster / 2nd St
- Kroger
- Carpenter / Mound St
- Summit at Coates Run
- Gordy Hall
- Jeff Hill
- Alpha Xi Delta
- Walmart
- Staples
- East State / Hope Drive
- Holzer Clinic
- East State / Hope Drive
- Market on State
- 970 East State
- Court / President
- East State / Robinson
- Big Lots
- East State / Eden
- East State / Charles
- East State / Harris
- East State / May
- East State / Watt
- East State / Morris
- Carpenter / Court
- Congress / West State
- Court / Washington
- Congress / Washington
- Richland / President
- Richland / West Green Dr
- Richland / Dairy Lane
- Dairy Lane / South Park
- The Ridges - front
- The Ridges - rear
- Richland / West Green Dr
- Berkley Turnaround
- Andover Road
- Court / West State
- Richland South Y
- 518 Richland Ave
- Richland / Canterbury
- Richland / Hooper
- Richland / Courtyard
- Richland / Dairy Lane
- Richland / Summit
- Richland / Hooper
- Carriage Hill
- Richland / Canterbury
- Carpenter / Grosvenor
- 518 Richland Ave
- Richland South Y
- Clarke / Curran
- 2nd / Central
- West State / Shafer
- Shafer / West Union
- Shafer / West Green Dr
- West Green Dr - Stocker
- West Green Dr / Richland
- South Green Dr / U Terrace
- East State / Morris
- Race Street - Morton Hall
- Stewart St - Front Four
- Stewart / East Union
- Stewart / Mill St
- Palmer / Stimson
- Stimson / Grant
- Morris / May
- May / Lincoln
- Lincoln / Home St
- Home St / Lincoln
- East State / Watt
- Lincoln / May
- May / Morris
- Grant / Stimson
- Stimson / Palmer
- Mill / Stewart
- Stewart / East Union
- Stewart St - Front Four
- Race Street - Morton Hall
- U Terrace / South Green Dr
- West Green Dr - Stocker
- East State / May
- Shafer / West Green Dr
- Shafer / West Union
- Innovation Center
- West Union / Factory St
- 93 West Union St
- Carpenter / Mound St
- Lancaster / 2nd St
- Columbus Rd / Sunset Dr
- 91 Columbus Rd
- 165 Columbus Rd
- East State / Home St
- Columbus Rd / Dorr Rd
- 223 Columbus Rd
- S.R. 682 / Poston Rd
- Plains Plaza Mall
- Connett Rd / Bean Rd
- Plains Library
- 45 E 4th St
- U. Estates Boulevard
- West Union / Bikeway
- West Union / Herrold
Over time
Overall score across the last 20 checks — unchanged since 2026-07-08.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-06-19 | 50.3 | first check |
| 2026-06-20 | 50.3 | no change |
| 2026-06-21 | 50.3 | no change |
| 2026-06-22 | 50.3 | no change |
| 2026-06-23 | 50.3 | no change |
| 2026-06-24 | 50.3 | no change |
| 2026-06-25 | 50.3 | no change |
| 2026-06-26 | 50.3 | no change |
| 2026-06-27 | 50.3 | no change |
| 2026-06-28 | 50.3 | no change |
| 2026-06-29 | 50.3 | no change |
| 2026-06-30 | 50.3 | no change |
| 2026-07-01 | 50.3 | no change |
| 2026-07-02 | 50.3 | no change |
| 2026-07-04 | 50.3 | no change |
| 2026-07-05 | 50.3 | no change |
| 2026-07-06 | 50.3 | no change |
| 2026-07-07 | 50.3 | no change |
| 2026-07-08 | 50.3 | no change |
| 2026-07-09 | 50.3 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
What changed in this feed
Overall grade and score held steady since 2026-07-08.
Same feed file as 2026-07-08; 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
- Error1 instance
Service data ended 3112 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.)
Agencies here usually clear this within about 1 week (based on 18 observed fixes).
Validator rule: scorecard_feed_expired · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning315 instances
315 of 315 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)
- Warning124 instances
124 of 124 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)
- Warning99 instances
Missing timepoint value (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_timepoint_value' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: missing_timepoint_value · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning6 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.)
Agencies here usually clear this within about 1 week (based on 61 observed fixes).
Validator rule: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some files leave out fields that GTFS asks for but does not require.
Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.
Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)
Agencies here usually clear this within about 2 weeks (based on 8 observed fixes).
Validator rule: missing_recommended_field · 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.)
Agencies here usually clear this within about 1 week (based on 31 observed fixes).
Validator rule: 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.)
Agencies here usually clear this within about 1 week (based on 16 observed fixes).
Validator rule: scorecard_missing_feed_info_dates · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info2 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)
- Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
App makers and state data programs have nobody to email when they spot a problem with your feed, so problems linger.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Agencies here usually clear this within about 1 week (based on 10 observed fixes).
Validator rule: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Beyond the grade
Opportunities that do not change your grade today: fare detail, on-demand service, and deeper accessibility data.
3 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (2, 4, SL).
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.
93 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Court / President", "Court / Washington", "Court / West State", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
NTD certification readiness Not ready
Resolve this before you certify on the D-10. Service data expired 3112 days ago, so FTA would find the link out of date.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Not ready
- Service data expired 3112 days ago, so FTA would find the link out of date.
- 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 315 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. Service data expired 3112 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 3112 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.
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
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 78 / 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 0 / 100
- The FTA National Transit Database expectation of a valid, current feed. Google Transit: an expired calendar drops the agency from Maps.
- Rider experience 52 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading: 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 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/athens-public-transit/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.