← All agencies

Feed status · checked 2026-11-14

SunTran

Based on the feed source on file; publisher ownership is not verified

Service mode Tram + Bus

59.8 / 100

down 0.4 since 2026-11-13

Cataloged in Arizona.

Expires in 14 daysRealtime not yet published

Source feed: https://www.suntran.com/wp-content/uploads/SunTranGTFS.zip Version history on the Mobility Database

Checked 2026-11-08: the feed URL on file had stopped working, so this record now tracks the file linked from suntran.com. The agency name and stop locations in that file match this record. Grades dated before this change came from an older Mobility Database mirror copy.

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.5, validator 8.0.1.

Checked for changes 16 hours ago; last changed 5 days ago.

Measured 3 of 4 score categories from the feed URL on file (publisher not verified).

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 configured feed URL. Publisher ownership of that URL is not verified.

Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.

About this feed

SunTran’s published feed lists 44 routes (tram / light rail and bus), 4,433 scheduled trips and 2,212 stops. Its service dates run from 2026-08-16 through 2026-11-28. The published file last changed on 2026-11-09.

Top things to fix

Fix 01

Re-export with a validity window that reaches at least 60 days out.Likely your export tool

Service data runs out in 14 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.

This one is about the feed as a whole, so there is no share of it to count.

⏱ One export setting.worth about +66 points in its category

Fix 02

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.

This one is about the feed as a whole, so there is no share of it to count.

⏱ A small file for most flat-fare systems.worth about +15 points in its category

Riders and need behind these fixes

  • This feed carries no National Transit Database ID, so annual rider-trips are not known for it.
  • Arizona as a whole measures lower on transit need. That is a statewide reading, not one for this feed's service area. Source: US Census ACS 5-year 2022, statewide overlay, as of 2026-11-02.

These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.

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.

Finding
Fix 01 in Top things to fix: its feed evidence and the requested 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
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.

  1. Fix 01 · Read the fix guide for scorecard_feed_expiring_soon

    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.

  2. Fix 02 · Read the fix guide for scorecard_no_fare_data

    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.

  3. Fix 03 · Read the fix guide for mixed_case_recommended_field

    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 is in 14 days.
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

Correctness68.0 / 100

The MobilityData validator flagged 5 kinds of issue across 1255 instances (0 error, 1255 warning, 0 informational).

Freshness23.3 / 100

Service data runs out in 14 day(s). Publish an updated feed soon or riders will lose trip planning.

Rider experience77.5 / 100

100% of stops state wheelchair accessibility (66% marked accessible, 34% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.

Accessibility100 / 100

100% of stops state accessibility (66% marked accessible). Reflects what the feed states, not verified physical usability.

2 accessibility depth signals

  • 20 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (10, 103X, 110X, 12, 16, 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.

  • 2176 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.

Realtime qualityNot yet measured

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 2212 stops.

Skip to route and stop data

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)
  • 103X (gray)
  • 105X (pink)
  • 107X (purple)
  • 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)
  • 700 (blue)
  • 8 (red)
  • 9 (purple)
  • 124X (brown)
Routes in SunTran's feed
RouteTypeLine color
1 Glenn/SwanBusyellow
10 RuthrauffBuspink
101X Golf Links-Downtown ExpressBusteal
103X Northwest- UA Downtown ExpressBusgray
105X Foothills-Downtown ExpressBuspink
107X Oro Valley-Downtown ExpressBuspurple
109X Catalina Hwy-Downtown ExpressBuspurple
11 Alvernon/AjoBusbrown
110X Rita Ranch-Downtown ExpressBusteal
12 S 12th AveBusorange
15 Campbell AveBusteal
16 Oracle/S. 6th AveBusteal
17 Country Club/29th St.Busteal
19 Stone AveBusgreen
2 Tucson MarketplaceBuspink
203X Oro Valley-Aero Park ExpressBuspurple
204X Northwest- Aero Park ExpressBusgreen
21 Congress/SilverbellBusred
23 Mission RoadBusblue
25 S Park AveBusgreen
26 Benson HighwayBusyellow
27 Midvale/ValenciaBusyellow
29 Pascua Yaqui/Banner UMC SouthBuspurple
3 6th St/WilmotBusyellow
34 Craycroft/Ft LowellBusorange
37 PantanoBusbrown
4 SpeedwayBusteal
401 N Oracle/CatalinaBusgreen
412 Thornydale/Orange GroveBusteal
413 Marana/I-10Busgray
421X Green Valley/Sahuarita ConnectorBusblack
430 Tucson EstatesBusbrown
440 San XavierBusbrown
450 Southeast Tucson/Rita RanchBusred
486 AjoBusteal
5 Pima/West SpeedwayBusbrown
6 Euclid/N 1st AveBusyellow
61 La ChollaBusbrown
62 Ina RdBusgreen
7 22nd StBusgreen
700 Sun LinkTram / light railblue
8 BroadwayBusred
9 Grant RoadBuspurple
124X Northwest-Downtown ExpressBusbrown
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)
  • 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/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)
  • Glenn/Edith (NW)
  • Glenn/Country Club (NW)
  • Glenn/Treat (NW)
  • Glenn/Tucson (NW)
  • and 1962 more (see the full list on the map or in the GeoJSON)

Over time

Overall score across the last 6 checks — down 0.4 since 2026-11-13.

2026-11-09: 61.92026-11-10: 61.52026-11-11: 61.02026-11-12: 60.62026-11-13: 60.22026-11-14: 59.8
Show the numbers
Overall score by check, with the change from the previous check
CheckScoreChange
2026-11-0961.9 first check
2026-11-1061.5 down 0.4
2026-11-1161.0 down 0.5
2026-11-1260.6 down 0.4
2026-11-1360.2 down 0.4
2026-11-1459.8 down 0.4

What changed since your last check

  • Correctness no change
  • Freshness down 1.7
  • Rider experience no change

Feed history

Every check on record for this feed, grouped by the published file, newest first. A new file means the published zip changed. Grades from earlier rubric versions are shown with their rubric and are not comparable with today’s grade or the trend above.

Feed history by published file
CheckedPublished fileService dates throughGrade at the time
2026-11-09 to 2026-11-14 (6 checks)a4634dda6cc42026-11-28Current rubric: see the trend above
2026-10-02 to 2026-11-06 (35 checks)f57bec4a90c52026-05-16F, 55.7 under rubric 1.4, an earlier scoring contract; not comparable with today’s grade
2026-07-25 to 2026-10-01 (65 checks)f57bec4a90c52026-05-16F, 55.7 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-07-13 to 2026-07-24 (9 checks)f57bec4a90c52026-05-16F, 55.7 under rubric 1.2, an earlier scoring contract; not comparable with today’s grade
2026-06-19 to 2026-07-12 (24 checks)f57bec4a90c52026-05-16F, 55.7 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade

What changed over time

On 2026-11-09 this feed started at grade D. On 2026-11-14 the grade moved from D to F. As of 2026-11-14 it holds grade F.

A plain-language history of this feed, newest first.

  • 2026-11-14 Grade went D to F.

Everything we checked

9 findings, ordered by severity.

Show every finding
  • Warning1064 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 for mixed_case_recommended_field · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning118 instances

    On some trips the stop distances run a little past the end of the route line.

    The stop and shape distance values don't quite line up, so any math that uses them can drift.

    Fix: Re-generate shape_dist_traveled on export so stop and shape distances use the same units. (Usually an export-tool fix, not hand editing.)

    Finding code: trip_distance_exceeds_shape_distance_below_threshold · Read the fix guide for trip_distance_exceeds_shape_distance_below_threshold · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning71 instances

    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 for stop_too_far_from_shape_using_user_distance · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning3 instances

    3 of 4433 trips have no headsign, the text that tells riders where the transit vehicle is going. A trip counts when it has trip_headsign or a stop_headsign at every stop.

    When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.

    Fix: Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign. (Usually one value per route pattern in your scheduling source.)

    Finding code: scorecard_missing_headsigns · Read the fix guide for scorecard_missing_headsigns · See GTFS Best Practices (opens GTFS Best Practices on an external site)

  • Warning1 instance

    This feed's service calendar runs out within the next 30 days.

    If a new feed isn't published before it ends, trip planners will drop your agency and riders will see no service.

    Fix: Schedule a feed re-export now so the new calendar is live well before the current one ends. (Usually a re-export from your scheduling software.)

    Finding code: feed_expiration_date30_days · Read the fix guide for feed_expiration_date30_days · 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 for missing_feed_contact_email_and_url · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning1 instance

    Service data runs out in 14 day(s).

    When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.

    Fix: Re-export with a validity window that reaches at least 60 days out. (One export setting.)

    Finding code: scorecard_feed_expiring_soon · Read the fix guide for scorecard_feed_expiring_soon · See GTFS Best Practices (opens GTFS Best Practices 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 for scorecard_no_fare_data · 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. Small errors then sit in the feed for months.

    Fix: Add feed_contact_email to feed_info.txt. (One field.)

    Finding code: scorecard_no_feed_contact · Read the fix guide for scorecard_no_feed_contact · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

NTD GTFS readiness Needs attention

This feed is close to NTD-ready. Service data runs out in 14 days; renew before you certify.

Published Ready
Published at a public URL.
Valid Ready
Passes validation with no errors.
Current Needs attention
Service data runs out in 14 days; renew before you certify.
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 4433 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

One requirement remains for this feed to earn the conformance mark. Service data runs out in 14 days; renew to qualify.

Valid Met
Passes validation with no errors.
Current Not yet
Service data runs out in 14 days; renew to qualify.
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.

At risk for the Google and Apple Maps four-week coverage bar. This feed has 13 days of service left. Maps needs at least four weeks (28 days) of upcoming service, so your agency will fall out of trip planners soon. Re-export with a longer calendar.

How this agency maps to the standards

The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance, FTA National Transit Database GTFS requirement. Read the full standards crosswalk.

Correctness 68 / 100
GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading covers stop locations, route names, and colors. Google Transit requires a feed to pass validation for publication. FTA NTD readiness also checks that the published feed is valid.
Freshness 23 / 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.

Part of the Arizona portfolio: the same scorecards for every feed we track in that group, on one free page.

Similar feeds in Arizona

Other scorecards in Arizona, starting with the same kind of service at a similar size. Listed for comparison, not ranked.

Show your grade

Put this badge on your agency site or feed README. It updates after each completed scoring check, shows the date of that check, and links back to this scorecard. When there is no current score it says so instead of showing an old one.

SunTran: GTFS feed quality grade F, 59.8 of 100, checked 2026-11-14. GTFS 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-11-14.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-11-14. 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.