Feed status · checked 2026-08-01
81 Connection, CityGo, KanConnect
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in Kansas.
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 84 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 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
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.
The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
⏱ A small file for most flat-fare systems.worth about +15 points in its category
Trim leading and trailing spaces on export. The scorecard's auto-fixed copy already does this.Likely your export tool
Some values have extra spaces at the start or end. A stray space can break a match, so a stop or route may fail to link across files.
⏱ Usually one export setting.worth about +8 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
- The feed contains no fare information.
- Next action
- 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.
- 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
- Some values have extra spaces at the start or end.
- Next action
- Trim leading and trailing spaces on export. The scorecard's auto-fixed copy already does this.
- 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.
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. · 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.
Trim leading and trailing spaces on export. The scorecard's auto-fixed copy already does this.
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 97.9% of stops and 100% 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 10 kinds of issue across 7689 instances (0 error, 7688 warning, 1 informational).
Service data ended 944 day(s) ago. Trip planners have likely already dropped this feed.
98% of stops state wheelchair accessibility (98% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
98% of stops state accessibility (98% marked accessible). Reflects what the feed states, not verified physical usability.
1 accessibility depth signal
106 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("7th & Walnut", "United Building (Iron & 7th)", "Iron & Connecticut", 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 192 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.
- KCEL1 (yellow)
- KCEL2 (yellow)
- Blue Regular (blue)
- Yellow Regular (yellow)
- Red Regular (red)
- Green Regular (green)
- Purple Regular (purple)
- Blue Peak (blue)
- Blue Peak (blue)
- Green Peak (green)
- Green Peak (green)
- Purple Peak (purple)
- Red Peak (red)
- Yellow Peak (yellow)
- Purple Peak (purple)
- Red Peak (red)
- Yellow Peak (yellow)
- 81 C SB (gray)
- 81 C NB (gray)
| Route | Type | Line color |
|---|---|---|
| KCEL1 KanConnect East Link 1 | Bus | yellow |
| KCEL2 KanConnect East Link 2 | Bus | yellow |
| Blue Regular | Bus | blue |
| Yellow Regular | Bus | yellow |
| Red Regular | Bus | red |
| Green Regular | Bus | green |
| Purple Regular | Bus | purple |
| Blue Peak Blue AM Peak | Bus | blue |
| Blue Peak Blue PM Peak | Bus | blue |
| Green Peak Green AM Peak | Bus | green |
| Green Peak Green PM Peak | Bus | green |
| Purple Peak Purple AM Peak | Bus | purple |
| Red Peak Red AM Peak | Bus | red |
| Yellow Peak Yellow AM Peak | Bus | yellow |
| Purple Peak Purple PM Peak | Bus | purple |
| Red Peak Red PM Peak | Bus | red |
| Yellow Peak Yellow PM Peak | Bus | yellow |
| 81 C SB 81 Connection Southbound | Bus | gray |
| 81 C NB 81 Connection Northbound | Bus | gray |
List every stop
- 7th & Walnut
- Santa Fe & Iron (SE Corner)
- Santa Fe & Ash (Mid Block)
- OCCK Trans (340 N. Santa Fe)
- Chuck's Bar (600 N. Santa Fe)
- N Santa Fe & Woodland
- Woodland & N 4th
- Woodland & N 2nd
- N 2nd & Pacific
- Pacific & N 4th
- Pacific & N 7th
- 9th & Hamilton
- MLK Child Center
- Salvation Army
- Santa Fe & Woodland
- Santa Fe & Lincoln
- OCCK Trans (Parking Lot)
- Learning Center (Elm & 8th)
- Senior Center (9th & Park)
- Santa Fe & Ash (NW corner)
- Santa Fe & Iron (NW corner)
- Santa Fe & Mulberry (256 S. Santa Fe)
- Walnut & 4th
- Oakdale Park (North Entrance)
- Oakdale Park (TP Center)
- Kenwood Park Drive (Foot Bridge)
- Kenwood Cove (701 Kenwood Park)
- YMCA (570 YMCA Drive)
- Central Kansas Mental Health
- DCF (901 Westchester)
- Faith Drive
- Hospice of Salina
- Crawford & Marymount
- Presbyterian Manor (2601 E. Crawford)
- Fairdale & Crawford
- Crawford & Briarcliff
- Bill Burke Park
- Key Rexall (901 E. Crawford
- Mowery Clinic (Crawford & Roach)
- Elmore Center/Central High
- Crawford & 3rd
- Santa Fe & Crawford
- Salina Ortho (S. Santa Fe & Prescott)
- Salina Regional Health Ctr (Parking Garage)
- Salina Regional Health Ctr (Entrance)
- Windsor Estates (Prescott & S 3rd)
- Salina Family Healthcare (Prescott & Elmore)
- Mowery Clinic (Prescott & Roach)
- Bike Tek (Prescott & S Ohio)
- Ohio & Ellsworth (1015 E. Ellsworth)
- Ohio & Kirwin (1015 E Kirwin)
- Ohio & Cloud (1020 E. Cloud)
- Speakeasy/Planet Fitness (2030 S. Ohio)
- Comcare (2090 S. Ohio)
- Bennington State Bank (2130 S. Ohio)
- Ohio Crosswalk & 2194 Nottingham
- Ohio & Magnolia (2358 S. Ohio)
- Redeemer Lutheran Church (743 E. Magnolia)
- Magnolia & Chapel Ridge
- Central Mall (JC Penney)
- Petco/Big Lots (Mid State Plaza)
- Kohls (2580 S. 9th)
- Goodwill (2640 Planet)
- Tucson's Steakhouse (2750 S. 9th)
- Walmart (2900 S. 9th)
- Market Place Apts (2713 Market Place)
- Belmont & Key (Fire Station)
- Magnolia & Belmont
- South High School
- 2349 S. Ohio (St. Mark Lutheran Church)
- Ohio & Nottingham (2243 S. Ohio)
- Ohio & Wayne (2075 S. Ohio)
- Parkwood Plaza (Ohio & Albert)
- Dillons (Ohio & Cloud)
- First Church of the Nazarene (Ohio & Kirwin)
- Ohio & Ellsworth (1100 E. Minneapolis)
- Comcare (Ohio & Republic)
- Church of Jesus Christ (McAdams & Manchester)
- Ohio & Elmhurst
- Ohio & 1101 Greeley
- Ohio & 1100 Gypsum
- Dauer Truck Center (Ohio & E Iron)
- N Ohio Crosswalk (1101 Poplar)
- Elm & N Penn (721 E Elm)
- 617 E Elm
- Hazardous Waste (311 E Elm)
- Barlett Building (9th & Mulberry)
- United Building (Iron & 7th)
- Burger King (316 E Iron)
- Speedy Wash (514 E. Iron)
- Saline County Dialysis (700 E Iron)
- 1006 E Iron
- Iron & Connecticut
- Woodland Corporate Center (SSA)
- Iron Wood Apts (1409 E. Iron)
- Birthright (1125 E. Iron)
- 1027 E Iron
- East Iron Office Complex (645 E. Iron)
- Save A Lot (511 E Iron)
- Iron & 4th Street (On Bridge)
- Bank of Tescott (600 S. Santa Fe)
- Santa Fe Wave & Ride (Crawford to Claflin)
- KWU by Crosswalk (100 E. Claflin)
- Genesis (1814 S. 9th)
- Planet Plaza (Planet & Otto)
- Super Dillons (2350 Planet)
- Sams Club (2919 Market Place)
- Hong Kong Buffett (2515 Market Place)
- Central Mall (main entrance)
- Fountain Plaza (Planet & Otto)
- Kraft Manor Shopping Center
- KWU by Crosswalk (Claflin & Highland)
- Santa Fe Wave & Ride (Claflin to Crawford)
- Sacred Heart Cathedral (Iron & 8th)
- Phillips Park (610 W. Iron)
- S College & University (134 S. College)
- S College & Spruce (302 S College)
- S College & Morrison (500 S. College)
- S College & Prescott (548 S. College)
- Phillips & Charles (626 Phillips)
- W Crawford & Phillips (Sinclair Station)
- Sunset Dillons (1201 W. Crawford)
- W Crawford & Duvall (1412 W Crawford)
- Ambassador Hotel (1616 W Crawford)
- Braum's (Beverly & W Crawford)
- 1717 W Crawford
- Pet Life (1501 W Crawford)
- Cherokee Wave & Ride (Crawford to Republic)
- Cherokee & Redwood Drive (1613 Redwood)
- W Republic & Osage (1319 W Republic)
- Broadway & Smith (1900 S Broadway)
- Hageman & Lena (502 Lena)
- Heartland Programs (Hageman & Venus)
- Citywide Self Storage (Saturn & Tulane)
- Menards (805 Virginia Court)
- K-State Salina (Magnolia & Centennial)
- OCCK Parking Lot & Centennial
- Caseys General Store (725 W Schilling)
- Schilling & Virginia
- Solutions Outreach (Schilling & Centennial)
- Salina Area Technical College
- K-State Salina (College Center - On request)
- Choices Network (2151 Centennial)
- Republic & Cherokee
- Cherokee Wave & Ride (Republic to Crawford)
- First Bank Kansas (1333 W Crawford)
- Crawford @ R/R tracks
- Community of Christ (W Crawford & 11th)
- Morrison House (513 S 8th)
- 9th & Washington
- Crawford & 10th
- La Hacienda (641 S. Broadway)
- Ace Home Center
- Glass Services (Broadway & Walnut)
- Broadway & Ash (overpass)
- Randy's Auto (1007 North)
- North & 13th (SE Corner)
- 11th & Lincoln
- Woodland & 10th
- Church of Christ
- Econo Lodge (1846 N 9th)
- Pilot Travel Center
- Gold Road
- La Quinta (201 E Diamond Dr)
- Iron Skillet
- Thomas Park
- 9th & Inez (1309 N. 9th)
- 9th & Harsh (927 N. 9th)
- Airliner Motel (Broadway & Woodland)
- 12th & Lincoln
- North & 13th (NE corner)
- Nick's Pawn Shop (118 S. Broadway)
- KFC (430 S. Broadway)
- Dollar General (654 S. Broadway)
- 9th & Prescott
- First Presbyterian (Mulberry & 8th)
- Salina Fieldhouse (140 N. 5th)
- Vanier Child Center (155 N. Oakdale)
- The Alley (115 E. Ash)
- City/County Building (300 W Ash)
- Sacred Heart Cathedral (8th & Iron)
- Casey's in Minneapolis
- Highway 24 Junction
- Walmart - Concordia
- CCCC - Concordia
- OCCK - Concordia
- Washington & 7th - Concordia
- Casey's - Belleville
- CCCC - Concordia 2
- Courthouse - Belleville
- 123 Main St (Solomon)
- 307 W. 7th (Solomon)
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 50.1 | first check |
| 2026-07-30 | 50.1 | no change |
| 2026-07-31 | 50.1 | no change |
| 2026-08-01 | 50.1 | 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 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)
- Warning7670 instances
Some values have extra spaces at the start or end.
A stray space can break a match, so a stop or route may fail to link across files.
Fix: Trim leading and trailing spaces on export. The scorecard's auto-fixed copy already does this. (Usually one export setting.)
Finding code: leading_or_trailing_whitespaces · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning5 instances
Some route long names repeat the route's short name inside them.
Apps show both names together, so riders see the number twice, like '5 5 Downtown'.
Fix: Drop the short name from route_long_name and keep the long name descriptive, like 'Downtown via 5th Ave'. (One field per flagged route.)
Finding code: route_long_name_contains_short_name · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning4 instances
4 of 192 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)
- Warning3 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.)
Finding code: route_short_name_too_long · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning3 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.)
Finding code: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 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 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
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)
- 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
Some files contain columns that are not part of the GTFS spec.
Harmless to riders, but apps ignore these columns and they can hide typos in real column names.
Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)
Finding code: unknown_column · Read the fix guide · 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. Service data expired 944 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 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 28 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 944 days ago.
- Valid Met
- Passes validation with no errors.
- Current Not yet
- Service data expired 944 days ago.
- Accessible Met
- States wheelchair access on 98% of stops and 100% of trips.
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
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 60 / 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 77 / 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/81-connection-citygo-kanconnect/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.