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
Transit Authority of Northern Kentucky (TANK)
Based on the feed this agency publishes
unchanged since 2026-07-08
Ahead of 6% of all tracked agencies and 5% of mid-size agencies. Operates in Kentucky.
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 14 minutes ago; last changed 2 days ago; last fetch returned HTTP 404.
Measured 4 of 4 score categories from the Mobility Database's mirror copy of the feed.
How we measured this
Confidence in this measurement: medium.
- All four score categories were measured this run.
- Realtime was sampled in one bounded window of 9 snapshots.
- 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 921 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).
Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
The trip updates 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 11 observed fixes).
Check the vehicle positions endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
The vehicle positions 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 9 observed fixes).
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. Make this change in whatever tool produces your feed, then re-export.
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.
Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
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.
Check the vehicle positions endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
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
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 10 kinds of issue across 188 instances (0 error, 188 warning, 0 informational).
Service data ended 921 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.
Sampled 9 times outside service hours: 0 of 3 feeds healthy.
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.
- 1 (green)
- 12 (green)
- 16 (green)
- 17X (blue)
- 22X (blue)
- NKU Shuttle (white)
- 25 (green)
- 25X (blue)
- 2X (blue)
- 3 (green)
- 30X (blue)
- 32X (blue)
- Holmes HS #3 PM (white)
- Southbank Shuttle (yellow)
- 39X (blue)
- 40X (blue)
- Newport HS #2 AM (white)
- 42X (blue)
- Holmes HS #2 PM (white)
- Holmes HS #2 AM (white)
- Holmes HS #5 PM (white)
- 5 (green)
- Newport HS #1 PM (white)
- Newport HS #2 PM (white)
- Holmes HS #1 AM (white)
- Holmes HS #6 PM (white)
- Holmes HS #5 AM (white)
- 61 (green)
- Holmes HS #8 AM (white)
- 7 (green)
- Holmes HS #7 PM (white)
- Holmes HS #9 PM (white)
- 8 (green)
- Holmes HS #4 PM (white)
- KCJ (white)
| Route | Type | Line color |
|---|---|---|
| 1 Dixie Hwy/Florence | Bus | green |
| 12 Bellevue/Dayton | Bus | green |
| 16 West Newport/Fort Thomas | Bus | green |
| 17X Buttermilk Pike Express | Bus | blue |
| 1850 Notre Dame Academy PM | Bus | white (no shape in feed) |
| 22X Mt. Zion Rd Express | Bus | blue |
| NKU Shuttle | Bus | white |
| 25 NKU/Alexandria | Bus | green |
| 25X Alexandria Express | Bus | blue |
| 2X Airporter | Bus | blue |
| 3 Ludlow/Bromley | Bus | green |
| 30X Fort Wright/Lake Park Dr Express | Bus | blue |
| 32X Burlington Express | Bus | blue |
| Holmes HS #3 PM Holmes #3 PM | Bus | white |
| Southbank Shuttle | Bus | yellow |
| 39X Petersburg Rd/South Hebron Express | Bus | blue |
| 40X Worldwide Blvd/North Hebron Express | Bus | blue |
| Newport HS #1 AM | Bus | white (no shape in feed) |
| Newport HS #2 AM | Bus | white |
| 42X Florence Hub/Industrial Rd Express | Bus | blue |
| Holmes HS #2 PM | Bus | white |
| Holmes HS #2 AM | Bus | white |
| Holmes HS #5 PM | Bus | white |
| 5 Holman Ave/Fort Wright | Bus | green |
| Newport HS #1 PM | Bus | white |
| Newport HS #2 PM | Bus | white |
| Holmes HS #1 AM | Bus | white |
| Holmes HS #6 PM | Bus | white |
| Holmes HS #5 AM | Bus | white |
| 61 Covington Health Connection | Bus | green |
| Holmes HS #8 AM | Bus | white |
| 7 Madison Ave/Latonia | Bus | green |
| Holmes HS #7 PM | Bus | white |
| Holmes HS #9 PM | Bus | white |
| 8 Eastern Ave/Crestview Hills | Bus | green |
| Holmes HS #4 PM | Bus | white |
| KCJ Kenton County Jail | Bus | white |
This feed has 856 stops.
List every stop
- 11th at Saratoga
- Winston at 43rd
- Mall at Plaza
- Mall at Cayton
- Mall at Village at the Mall
- Merchants at Doering
- Doering at Florence Walmart
- Ted Bushelman at Doering
- Meijer at Woodspoint
- Spiral at Meijer
- Spiral at Turfway Commons
- Spiral at Beckfield College
- Thoroughbred at Turfway
- Hansel at Richman
- St Elizabeth Florence
- Steeple Chase at Turfway
- Turfway at Burlington
- Turfway at Crown Court Apts
- Turfway at Lloyd
- Dixie at Turfway
- Dixie at Turfway
- Turfway at Drexel
- Turfway at Curtis
- Steeple Chase at Turfway
- St Elizabeth Florence
- Hansel at Richman
- Thoroughbred at Turfway
- Spiral at Beckfield College
- Spiral at Turfway Commons
- Spiral at Meijer
- Meijer at Woodspoint
- Ted Bushelman at Doering
- Doering at Florence Walmart
- Merchant at Doering
- Mall at Village at the Mall
- Mall at Florence Square
- Mall at Cayton
- Mall at Plaza
- Florence Hub
- Donaldson at Airfield
- CVG Airport Terminal
- Donaldson at Mineola
- Lincoln at Spence
- Donaldson at Point Pleasant
- Spence at Kenton
- Donaldson at Point Pleasant
- Donaldson at Mineola
- Donaldson at Airfield
- Wendell Ford at Amazon Prime Air
- DHL North Lot
- CVG Centre
- Scott at 16th
- Scott at 17th
- Scott at 19th
- Scott at 20th
- Southern at Church
- Summer Hill at 19th
- Mt. Zion Park and Ride
- Mt Zion Park and Ride
- Washington at 10th
- Burlington at Kenner
- Burlington at Woodspoint
- Burlington at Zig Zag
- Burlington at Houston
- Burlington at Boone Aire
- Burlington at Greenview
- Burlington at Ridge
- Burlington at Zig Zag
- Burlington at Hopeful Church
- Burlington at Centennial
- Burlington at Service
- Burlington Park and Ride
- Amazon GSE Building
- North Bend at Coral
- North Bend at Barbara
- Langley at Hargrave
- 3680 Langley
- 3720 Langley
- 2431 Wright
- Wright at North Bend
- Conner at North Bend
- North Bend at Litton
- Limaburg at Cougar
- Limaburg Park and Ride
- Petersburg at Limaburg
- Petersburg at Ernst
- Petersburg at Hart
- Petersburg at Merrie
- Petersburg at Victory
- Petersburg at Elijah Creek
- Petersburg at Aviation
- Petersburg at Ridgedale
- Petersburg at Progress
- Petersburg at Terminal
- North Bend at Global
- North Bend at Worldwide
- Worldwide at North Bend
- 1190 Worldwide
- 1605 Worldwide
- 1155 Worldwide
- 1605 Worldwide
- 1180 Worldwide
- 1545 Worldwide
- 1200 Worldwide
- 1405 Worldwide
- 1500 Worldwide
- 1155 Worldwide
- 1600 Worldwide
- South Park at Sanctuary
- 1770 Worldwide
- 2266 South Park
- South Park at International
- International at Meridian
- 2030 Meridian
- North Bend at South Park
- North Bend at Global
- North Bend Park and Ride
- Main at Dixie
- Main at Banklick
- Main at Christian
- Dixie at Valley
- Mall at Mall Road Center
- Dixie at Circle
- US 42 at Sycamore
- Dixie at Riehl
- US 42 at Lacresta
- Dixie at Pinehurst
- US 42 at Freedom
- Dixie at New Buffington
- Industrial at Safeway
- 7970 Dixie
- Industrial at Carole
- Dixie at Industrial
- Empire at Industrial
- Empire at Dixie
- Empire at Schwan's
- Empire at Dixon
- Empire at Bluegrass
- Empire at Empire Connector
- Empire at Empire Connector
- Empire at Bluegrass
- Empire at Dixon
- Empire at Duro Bag
- Empire at Dixie
- Empire at Industrial
- Dixie at Industrial
- Industrial at Carole
- Dixie at New Buffington
- Industrial at Hillcrest
- Dixie at Pinehurst
- US 42 at Dream
- Dixie at Roger
- US 42 at Lacresta
- Dixie at St Jude
- US 42 at Diane
- Dixie at Shenandoah
- Mall at Mall Road Shopping Center
- Main at Christian
- Main at Banklick
- Turfway at Dixie
- 9th at Central
- 9th at Patterson
- 9th at Washington
- New Price at CVG Fire Dept
- Benham at 4th
- 4th at Kenton
- 4th at Boone
- York at 5th
- 4th at Main
- 6th at Monmouth
- Clay at 5th
- 6th at Saratoga
- Clay at 6th
- 6th at Berry
- 6th at Washington
- 6th at Dayton
- 6th at Overton
- 6th at McKinney
- 6th at Monroe
- 6th at Ervin
- 6th at Park
- 6th at Vine
- 6th at Maple
- 6th at Walnut
- 6th at Linden
- 6th at O Fallon
- 6th at Oak
- Fairfield at Foote
- Riviera at Bellevue Plaza
- Fairfield at Taylor
- Riviera at Fairfield
- Fairfield at Patchen
- Fairfield at Riviera
- Riviera at Fairfield
- Fairfield at Berry
- Riviera at Bellevue Plaza
- Fairfield at Taylor
- 6th at Oak
- Fairfield at Ward
- 6th at Linden
- 6th at O Fallon
- 6th at Maple
- 6th at Walnut
- 6th at Park
- 6th at Vine
- 6th at Monroe
- 6th at Ervin
- 6th at Overton
- 6th at McKinney
- 6th at Dayton
- 6th at Washington
- 6th at Berry
- 6th at Saratoga
- 6th at Clay
- Monmouth at 5th
- 6th at Main
- 3rd at Newport on the Levee
- 5th at Boone
- 5th at Kenton
- 5th at Benham
- 5th at Clark
- Clark at 4th
- 2nd at Benham
- Grand at Churchill
- Grand at Grand Towers Apts
- Carothers at Pavilion
- 4th at Columbia
- Carothers at Newport Plaza
- Central at 5th
- Monmouth at Carothers
- Central at 6th
- 11th at John
- 6th at Isabella
- 11th at York
- Isabella at 7th
- 11th at Columbia
- Isabella at 8th
- 11th at Isabella
- Isabella at 9th
- Isabella at 10th
- Isabella at 10th
- Isabella at 9th
- 11th at Central
- Isabella at 8th
- 11th at Columbia
- Isabella at 7th
- 11th at York
- Isabella at 6th
- 11th at John
- 5th at Central
- and 606 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 21 checks — unchanged since 2026-07-08.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-06-19 | 30.6 | first check |
| 2026-06-20 | 30.6 | no change |
| 2026-06-21 | 30.6 | no change |
| 2026-06-22 | 30.6 | no change |
| 2026-06-23 | 30.6 | no change |
| 2026-06-24 | 30.6 | no change |
| 2026-06-25 | 30.6 | no change |
| 2026-06-26 | 30.6 | no change |
| 2026-06-27 | 30.6 | no change |
| 2026-06-28 | 30.6 | no change |
| 2026-06-29 | 30.6 | no change |
| 2026-06-30 | 30.6 | no change |
| 2026-07-01 | 30.6 | no change |
| 2026-07-02 | 30.6 | no change |
| 2026-07-03 | 30.6 | no change |
| 2026-07-04 | 30.6 | no change |
| 2026-07-05 | 30.6 | no change |
| 2026-07-06 | 30.6 | no change |
| 2026-07-07 | 30.6 | no change |
| 2026-07-08 | 30.6 | no change |
| 2026-07-09 | 30.6 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
- Realtime quality 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 921 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)
- Error1 instance
The trip updates realtime feed failed during sampling.
When this feed is down, riders see scheduled times presented as if they were live.
Fix: Check the trip updates 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 11 observed fixes).
Validator rule: scorecard_rt_trip_updates_unreachable · Read the fix guide · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)
- Error1 instance
The vehicle positions realtime feed failed during sampling.
When this feed is down, riders see scheduled times presented as if they were live.
Fix: Check the vehicle positions 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 9 observed fixes).
Validator rule: scorecard_rt_vehicle_positions_unreachable · Read the fix guide · See GTFS-Realtime reference (opens the GTFS-Realtime reference 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)
- Warning856 instances
856 of 856 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)
- Warning106 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)
- Warning37 instances
Same route and agency url (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'same_route_and_agency_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: same_route_and_agency_url · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning16 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)
- Warning16 instances
Route short name too long (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'route_short_name_too_long' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: route_short_name_too_long · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning5 instances
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)
- Warning3 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)
- Warning2 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.)
Validator rule: mixed_case_recommended_field · Read the fix guide · 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.)
Agencies here usually clear this within about 1 week (based on 16 observed fixes).
Validator rule: feed_expiration_date7_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Missing feed contact email and url (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_feed_contact_email_and_url' 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: 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.)
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
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)
- 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.
48 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Winston at 43rd", "St Elizabeth Florence", "St Elizabeth Florence", 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 921 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 921 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 2031 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 921 days ago. States wheelchair access on 0% of stops and 100% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Not yet
- Service data expired 921 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.
Realtime reliability
The realtime feed responded on 0.0% of 106 checks over the last 16 days, with lag not reported by the feed.
Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.
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 50 / 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 0 / 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/transit-authority-of-northern-kentucky-tank/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.