Feed status · checked 2026-08-01
SunTran
Based on the feed this agency publishes
Service mode Tram + Bus
unchanged since 2026-07-31
Catalogued in Arizona.
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 68 minutes ago; last fetch returned HTTP 404.
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 77 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the transit vehicles 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
Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').Likely your export tool
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.
⏱ Often a bulk fix in your scheduling software.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 77 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 rider-facing names are in ALL CAPS or all lowercase.
- Next action
- Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').
- 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.
Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). · 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 77 days ago.
- Published accessibility data
- Accessibility information is stated for 100% 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 6 kinds of issue across 428 instances (0 error, 428 warning, 0 informational).
Service data ended 77 day(s) ago. Trip planners have likely already dropped this feed.
100% of stops state wheelchair accessibility (67% marked accessible, 33% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
100% of stops state accessibility (67% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
21 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (10, 103X, 108X, 110X, 12, 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.
2165 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Park/Speedway (NE)", "Glenn/Campbell (SE)", "Glenn/Alvernon (SE)", 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 2200 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.
- 1 (yellow)
- 10 (pink)
- 101X (teal)
- 102X (brown)
- 103X (gray)
- 104X (black)
- 105X (pink)
- 107X (purple)
- 108X (orange)
- 109X (purple)
- 11 (brown)
- 110X (teal)
- 12 (orange)
- 15 (teal)
- 16 (teal)
- 17 (teal)
- 19 (green)
- 2 (pink)
- 203X (purple)
- 204X (green)
- 21 (red)
- 23 (blue)
- 25 (green)
- 26 (yellow)
- 27 (yellow)
- 29 (purple)
- 3 (yellow)
- 34 (orange)
- 37 (brown)
- 4 (teal)
- 401 (green)
- 412 (teal)
- 413 (gray)
- 421X (black)
- 430 (brown)
- 440 (brown)
- 450 (red)
- 486 (teal)
- 5 (brown)
- 6 (yellow)
- 61 (brown)
- 62 (green)
- 7 (green)
- 720 (black)
- 790 (black)
- 8 (red)
- 9 (purple)
- 700 (blue)
| Route | Type | Line color |
|---|---|---|
| 1 Glenn/Swan | Bus | yellow |
| 10 Ruthrauff | Bus | pink |
| 101X Golf Links-Downtown Express | Bus | teal |
| 102X Northwest-UA Express | Bus | brown |
| 103X Northwest-Downtown Express | Bus | gray |
| 104X Marana-Downtown Express | Bus | black |
| 105X Foothills-Downtown Express | Bus | pink |
| 107X Oro Valley-Downtown Express | Bus | purple |
| 108X Broadway-Downtown Express | Bus | orange |
| 109X Catalina Hwy-Downtown Express | Bus | purple |
| 11 Alvernon/Ajo | Bus | brown |
| 110X Rita Ranch-Downtown Express | Bus | teal |
| 12 S 12th Ave | Bus | orange |
| 15 Campbell Ave | Bus | teal |
| 16 Oracle/S. 6th Ave | Bus | teal |
| 17 Country Club/29th St. | Bus | teal |
| 19 Stone Ave | Bus | green |
| 2 Tucson Marketplace | Bus | pink |
| 203X Oro Valley-Aero Park Express | Bus | purple |
| 204X Northwest- Aero Park Express | Bus | green |
| 21 Congress/Silverbell | Bus | red |
| 23 Mission Road | Bus | blue |
| 25 S Park Ave | Bus | green |
| 26 Benson Highway | Bus | yellow |
| 27 Midvale/Valencia | Bus | yellow |
| 29 Pascua Yaqui/Banner UMC South | Bus | purple |
| 3 6th St/Wilmot | Bus | yellow |
| 34 Craycroft/Ft Lowell | Bus | orange |
| 37 Pantano | Bus | brown |
| 4 Speedway | Bus | teal |
| 401 N Oracle/Catalina | Bus | green |
| 412 Thornydale/Orange Grove | Bus | teal |
| 413 Marana/I-10 | Bus | gray |
| 421X Green Valley/Sahuarita Connector | Bus | black |
| 430 Tucson Estates | Bus | brown |
| 440 San Xavier | Bus | brown |
| 450 Southeast Tucson/Rita Ranch | Bus | red |
| 486 Ajo | Bus | teal |
| 5 Pima/West Speedway | Bus | brown |
| 6 Euclid/N 1st Ave | Bus | yellow |
| 61 La Cholla | Bus | brown |
| 62 Ina Rd | Bus | green |
| 7 22nd St | Bus | green |
| 720 Sun Link Extra Service | Tram / light rail | black |
| 790 Sun Link - Street Fair | Tram / light rail | black |
| 8 Broadway | Bus | red |
| 9 Grant Road | Bus | purple |
| 700 Sun Link | Tram / light rail | blue |
List every stop
- UA Mall (Inside)
- Campbell Av/Grant@Edison (SW)
- Grant/Alvernon (SE)
- Grant/Craycroft (SE)
- Alameda/Grossetta (NW)
- Church/Pennington (NW)
- SL/Broadway/6th Av (SE)
- Broadway/4th Av (SW)
- Euclid/12th St (SW)
- 22nd St/Park (SE)
- Campbell Av/Barleycorn (SW)
- 36th St/Kramer (NW)
- Country Club/Ajo (SW)
- Country Club/Ajo (NE)
- Country Club/Food Bank (NE)
- Campbell Av/Duvall Vista (NE)
- Campbell Av/Cochise Vista (NE)
- 36th St/Campbell (SE)
- Campbell Av/Barleycorn (NE)
- 22nd St/Santa Rita (NW)
- 22nd St/Park (NW)
- Broadway/Euclid (NW)
- 6th Av/Irvington (NE)
- 6th Av/Oklahoma (NE)
- 6th Av/Illinois (SE)
- 6th Av/Michigan (SE)
- 6th Av/District (SE)
- 6th Av/President (SE)
- Ajo/6th Av (SE)
- Ajo/Thomas O Price Center (SW)
- Ajo/Benson Hwy (SE)
- Ajo/Juvenile Center (EB)
- Ajo/P.C. Sheriffs Dept (EB)
- Ajo/Forgeus (SE)
- Milber St/La Colina Health Care (SE)
- Ajo/Country Club (SE)
- Ajo/Randolph Av (SE)
- Tucson Bl/Corona (NE)
- Tucson Bl/Elvira (NE)
- Tucson Bl/Medina (SE)
- Valencia/Tucson Blvd (SE)
- Valencia/Bay Colony (SE)
- Valencia/Country Club (SE)
- Valencia/Lisa Frank Dr (SE)
- Palo Verde/Britannia (SE)
- Palo Verde/Mossman (NE)
- Palo Verde/Benson Hwy (NE)
- Palo Verde/Nebraska (NE)
- Hotel Dr/Irvington (NE)
- Palo Verde/Coach Dr (NE)
- Palo Verde/Columbia (NE)
- Palo Verde/Ajo (NE)
- Palo Verde/Veterans (NE)
- Palo Verde/44th St (NE)
- Alvernon/29th St (NE)
- Alvernon/Santa Barbara (NE)
- Alvernon/Hayne (NE)
- Alvernon/Whittier (NE)
- Alvernon/Holmes (SE)
- Alvernon/5th St (NE)
- Alvernon/3rd St (SE)
- Alvernon/2nd St (NE)
- Alvernon/Speedway (NE)
- Alvernon/Fairmount (NE)
- Alvernon/Pima (NE)
- Alvernon/Seneca (NE)
- Alvernon/Flower (NE)
- Alvernon/Glenn (NE)
- Alvernon/Blacklidge (NE)
- Fort Lowell/Dodge (SE)
- Alvernon/Blacklidge (NW)
- Alvernon/Glenn (NW)
- Alvernon/Flower (NW)
- Alvernon/Seneca (SW)
- Alvernon/Pima (SW)
- Alvernon/Fairmount (SW)
- Alvernon/3rd St (SW)
- Alvernon/C De Soto (NW)
- Broadway/Alvernon (SE)
- Alvernon/Whittier (NW)
- Alvernon/Hayne (SW)
- Alvernon/Pso Dorado (SW)
- Alvernon/32nd St (NW)
- Alvernon/32nd St (SW)
- Palo Verde/Veterans (SW)
- Palo Verde/Ajo (SW)
- Palo Verde/Columbia (SW)
- Palo Verde/Michigan (SW)
- Gas Rd/Palo Verde (SE)
- Hotel Dr/Irvington (NW)
- Palo Verde/Corporate (SW)
- Palo Verde/Benson Hwy (SW)
- Palo Verde/Mossman (SW)
- Palo Verde/Hemisphere (NE)
- Palo Verde/Britannia (NW)
- Valencia/Hemisphere (NW)
- Valencia/Country Club (NW)
- Valencia/Bay Colony (NW)
- Tucson Bl/Valencia (SW)
- Tucson Bl/Medina (SW)
- Tucson Bl/Elvira (NW)
- Tucson Bl/Corona (NW)
- Ajo/Palo Verde (NW)
- Ajo/Randolph Av (NW)
- Ajo/Forgeus (NW)
- Ajo/P.C. Sheriffs Dept. (WB)
- Ajo/Juvenile Court (WB)
- Ajo/Bernard (NW)
- Ajo/Benson Hwy (NW)
- Ajo/Golden Eagle Distrib (WB)
- Ajo/2nd Av (NW)
- 6th Av/Ajo (NE)
- 6th Av/District (SW)
- Kino Pw/36th St (NE)
- 6th Av/Michigan (NW)
- 6th Av/Illinois (NW)
- 6th Av/Oklahoma (SW)
- Speedway/Cummings (NE)
- Speedway/Palms Park Dr. (NW)
- Speedway/Av Ricardo Small (NW)
- Speedway/Cmo Seco (NW)
- Speedway/Sarnoff (NE)
- Speedway/Pantano (NW)
- Speedway/Grady (NE)
- Speedway/7351 E Speedway (WB)
- Tetakusim Rd/Settler Av (NW)
- Cmo Potam/C Tetakusim (SW)
- Cmo Potam/Ball Field (IF)
- Tetakusim Rd/Sparrow Av (SW)
- Sorrel Ln/Tetakusim Rd (NE)
- Los Reales/Bolingbroke (SE)
- Los Reales/C de la Bajada (SW)
- Los Reales/Cmo Alegre (SE)
- Cardinal/Los Reales (NE)
- Cardinal/Tigre (NE)
- Cardinal/Pajarito (SE)
- Cardinal/Pincushion (NE)
- Cardinal/Century Dr (SW)
- Valencia/Mission (SE)
- Valencia/Indian Agency Rd (SE)
- Valencia/Pacheco (SE)
- 6th Av/Valeska (SE)
- 6th Av/Bilby (NE)
- 6th Av/Delta (NE)
- Kolb/C Osita (NE)
- Kolb/Princeton (NE)
- Kolb/Broadway (NE)
- Kolb/Kingston (NE)
- Speedway/Kolb (NW)
- Speedway/Dorado (NW)
- Speedway/Caribe (NE)
- Speedway/Natachee (NW)
- Speedway/Radisson Hotel (NW)
- Speedway/Wilmot (NW)
- Speedway/Alamo (NE)
- Speedway/Sahuara (NW)
- Speedway/Van Buren (NW)
- Speedway/Craycroft (NW)
- Speedway/Beverly (NW)
- Speedway/Rosemont (NW)
- Speedway/Arcadia (NW)
- Speedway/Swan (NW)
- Speedway/Catalina (NE)
- Speedway/Columbus (NW)
- Speedway/Arlington (NW)
- Speedway/Dodge (NE)
- Speedway/Howard (NE)
- Speedway/Country Club (NW)
- Speedway/Treat (NE)
- Speedway/Plumer (NW)
- Speedway/Warren Underpass (NW)
- Speedway/Olive Underpass (NE)
- Speedway/Euclid (NW)
- Speedway/2nd Av (NW)
- Speedway/4th Av (NW)
- Speedway/6th Av (NE)
- Stone/Speedway (SW)
- Stone/University (SW)
- Stone/Franklin (SW)
- Stone/Alameda (NW)
- Alameda/Court Av (NW)
- Speedway/6th Av (SE)
- Speedway/4th Av (SE)
- Speedway/2nd Av (SE)
- Speedway/Euclid (SE)
- Speedway/Olive Underpass (SW)
- Speedway/Highland Underpass (SW)
- Speedway/Warren Underpass (SW)
- Speedway/Plumer (SE)
- Speedway/Tucson (SE)
- Speedway/Treat (SE)
- Speedway/Country Club (SE)
- Speedway/Miramonte (EB)
- Speedway/Richey (SE)
- Speedway/Dodge (SE)
- Speedway/Arlington (SE)
- Speedway/Belvedere (SE)
- Speedway/Swan (SE)
- Speedway/Arcadia (SE)
- Speedway/Rosemont (SE)
- Speedway/Beverly (SE)
- Speedway/Craycroft (SE)
- Speedway/Van Buren (SE)
- Speedway/Sahuara (SE)
- Speedway/Sonoita (SE)
- Speedway/Radisson Hotel (SE)
- Speedway/Natachee (SE)
- Speedway/Dorado (SE)
- Kolb/Speedway (SW)
- Kolb/Kingston (SW)
- Kolb/K-Mart (NW)
- Kolb/Broadway (SW)
- Kolb/Princeton (SW)
- Kolb/C Ileo (SW)
- Speedway/Kolb (SE)
- Speedway/7350 E Speedway (EB)
- Speedway/Pantano (SE)
- Speedway/Woodridge Apts (SE)
- Speedway/Keesal (SE)
- Speedway/Goebel (SE)
- Speedway/Cmo Seco (SE)
- Speedway/Av Ricardo Small (SE)
- Speedway/Igo Way (SE)
- Speedway/Cummings (SE)
- 32nd St/Chrysler (NW)
- Silverlake/Palo Verde (NW)
- Silverlake/Randolph Way (NW)
- Country Club/Silverlake (NE)
- Country Club/27th St (NE)
- Country Club/23rd St (SE)
- Country Club/Eastland (NE)
- Country Club/17th St (NE)
- Country Club/Arroyo Chico (NE)
- Park/Drachman (NE)
- Park/Elm (NE)
- Park/Waverly (NE)
- Park/Grant (NE)
- Park/Copper (NE)
- Park/Glenn (SE)
- Glenn/Plumer (SE)
- Glenn/Tucson (SE)
- Glenn/Treat (SE)
- Glenn/Country Club (SE)
- Glenn/Edith (SW)
- Glenn/Palo Verde (SE)
- Glenn/Dodge (SE)
- Glenn/Columbus (NW)
- Glenn/Sycamore (NE)
- Glenn/Dodge (NW)
- Glenn/Palo Verde (NW)
- and 1950 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 | 55.7 | first check |
| 2026-07-30 | 55.7 | no change |
| 2026-07-31 | 55.7 | no change |
| 2026-08-01 | 55.7 | 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
9 findings, ordered by severity.
Show every finding
- Error1 instance
Service data ended 77 day(s) ago.
When the calendar runs out, trip planners stop showing this agency even though the transit vehicles 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)
- Warning421 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)
- 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.)
Finding code: expired_calendar · 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
Some stops sit far from the route line, going by the feed's own distance values.
Trip planners may draw the route down the wrong path or point riders to the wrong boarding location.
Fix: Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree. (Usually an export-tool fix, not hand editing.)
Finding code: stop_too_far_from_shape_using_user_distance · 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
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 77 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 77 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 5605 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 77 days ago.
- Valid Met
- Passes validation with no errors.
- Current Not yet
- Service data expired 77 days ago.
- Accessible Met
- States wheelchair access on 100% 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 72 / 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 78 / 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/suntran-2354/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.