Feed status · checked 2026-11-21
SunTran Utah
Based on the feed source on file; publisher ownership is not verified
Service mode Bus
unchanged since 2026-11-20
Cataloged in Utah.
The grade is not a count of validator errors. It also weighs freshness and rider information. How the grade works
Feed file
Watch this feed for free: we email you before it expires or when its grade drops.
Top things to fix
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.Likely your team
171 of 171 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.
Fixing this covers all 171 stops in the feed.
⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.Likely your export tool
416 of 416 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
Fixing this covers all 416 trips in the feed.
⏱ A default or per-trip field in your export.worth about +15 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.
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.
- Utah 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
- Finding
- Fix 02 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
- Finding
- Fix 03 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.
Fix 01 · Read the fix guide for scorecard_wheelchair_boarding_unknown
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.
Fix 02 · Read the fix guide for scorecard_wheelchair_accessible_unknown
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.
Fix 03 · 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.
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 405 days.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 0% 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.
About this feed
Looking for times or routes? This page checks the data file that trip planners use. For schedules, use the agency's own website or a trip planner.
SunTran Utah’s published feed lists 8 bus routes, 416 scheduled trips and 171 stops. Its service dates run from 2024-01-01 through 2027-12-31. The published file last changed on 2026-11-09.
Score by category
The MobilityData validator flagged 1 kind of issue across 416 instances (0 error, 0 warning, 416 informational).
Service data covers the next 405 days.
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.
2 accessibility depth signals
4 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (Route, Route, Route, Route).
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.
71 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Learning Center (Call) 2044 S Mesa Palms Dr", "Buena Vista/Calle Del Sol", "Bluff View/Sunrise", 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 171 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.
- Route (brown)
- Route (blue)
- Route (brown)
- Route (blue)
- Route (red)
- Route (teal)
- Route (green)
- Zion (brown)
| Route | Type | Line color |
|---|---|---|
| Route 6 Dixie Dr South | Bus | brown |
| Route 2 Riverside | Bus | blue |
| Route 4 Sunset | Bus | brown |
| Route 7 Washington | Bus | blue |
| Route 1 Red Cliffs | Bus | red |
| Route 5 Ivins | Bus | teal |
| Route 3 West Side Connector | Bus | green |
| Zion Route Zion Route | Bus | brown |
List every stop
- Transit Center 957 East 100 South
- Target 225 South River Rd
- 795 South 200 East
- 705 South 200 East
- Lightfoot’s Chevron 565 South 200 East
- Family Dollar 425 South 200 East
- 305 South 200 East
- Red Mtn Elem. 175 South 200 East
- Veterans Center 90 North 200 East
- 85 East 100 North
- Ivins City Office 85 North Main
- 272 East Center St
- 265 Red Cliffs Dr
- Park 410 East Center St
- Vista Elementary (Across St) 580 East
- 930 East Center @ Padre Canyon Dr
- 1250 E Snow Canyon Pkwy
- Black Desert Resort/Snow Canyon Parkway
- Homestead Townhomes 765 N Valley View
- 365 North Valley View
- Valley View @ Stonebridge
- 505 South Valley View
- 1910 East Red Cliffs Dr (Wells Fargo)
- Green Valley Condo's 834 South Dixie Dr
- 1078 South Dixie @ Silicon Way
- Dixie Dr/Mesa Palms Dr
- Learning Center (Call) 2044 S Mesa Palms Dr
- Wal-Mart 145 West 2710 South Circle
- Dixie Dr @ Black Ridge Dr
- Tonaquint Park 600 West @ Dixie Drive
- 1675 South Dixie Dr
- Cottonwood Cove Park 845 South Dixie Dr
- Green Valley Market 567 South Valley View
- Deseret Industries 865 North 2450 East (Route 1 Transfer to Route 7)
- 1367 West 100 North
- 1730 West 100 North
- Oasis Palms Apts 328 North Dixie Dr
- Dairy Queen 682 North Dixie Dr
- IHC Sunset Clinic 1739 West Sunset Blvd
- Jiffy Lube 1287 West Sunset Blvd
- Transfer Announcement
- Good Shepherd Church 610 North 2450 East
- Transfer Announcement
- 449 North 2450 East
- Bio Life 816 N 2860 E
- Costco 850 N 2860 E
- Wal Mart 689 W Telegraph
- 151 W Telegraph
- 51 E Telegraph/Post Office
- Telegraph & Palo Verde
- Telegraph at Bella Vista
- 190 N 1100 E
- Kings Row @ 1100 E & Kings Hwy
- 245 North 2450 East
- 1100 E & Pine Valley St.
- Bluff View/Victoria Ln
- Bluff View/Sunrise
- 700 E/Springhill Dr
- Community Recreation Center
- Library 250 N 300 E
- 135 E 300 N
- 335 N Main
- 55 W Buena Vista Blvd/N Main
- Buena Vista Blvd/N Millcreek Springs Dr
- 25 North 2450 East
- Buena Vista/Calle Del Sol
- 144 Cactus Ln/Buena Vista Blvd
- Cactus Ln/Quail Ridge Dr
- Cactus Ln/N Cactus Ln
- Mill Creek HS 250 South 2450 East
- Fossil Ridge School 383 South Mall Drive
- 700 W State St Hurricane
- Lion Blvd Springdale
- 3400 W Hurricane (Walmart)
- 700 W State St Hurricane
- 1670 S 120 E (Dixie Center) St. George
- 120 South 700 East
- 105 South Mall Drive
- Buena Vista (Boiler Park) Washington
- Red Cliffs Mall (Barnes & Noble)
- 1210 Zion Park Blvd (Bit & Spur) Springdale
- 1130 Zion Park Blvd (Hampton) Springdale
- Kolob Terrace Rd Virgin
- 300 N State St LaVerkin
- 40 North Mall Drive
- Kolob Terrace Rd Virgin
- 300 N State St LaVerkin
- Buena Vista (Boiler Park) Washington
- 5300 W Regional Park Rd (DMV) Hurricane
- Zion Medical Center 1791 East 280 North
- Barnes and Noble 435 North 1680 East
- Promenade 245 North Red Cliffs Dr (Red Lobster)
- Security Service Credit Union 1227 East 100 South
- 631 East 100 South
- Lions Club 301 East 100 South
- Library 80 West 100 South
- 112 South 300 West
- 320 South 700 East
- 243 West 400 South
- 55 West 400 South
- 660 South Main
- St George Express 950 South Main
- Best Western 1140 South Main
- Jack in the Box 1596 West Convention Ctr
- Dixie Center 215 E 1670 S
- Bella Vista Apts 360 East Riverside Dr
- Dr Volunteer Clinic 1060 East Riverside Dr
- Harmons 1210 East 700 South
- 592 South 700 East
- 950 East 700 South
- 580 East 700 South
- Dixie High School 677 South 400 East
- Jubilee House 500 South 400 East
- Rec Center 404 East 300 South
- 776 East 600 South
- Ball Diamond 425 S 900 E
- Avalon Apartments 333 South 1000 East
- 85 South 700 East
- 740 East 700 South
- 465 East Tabernacle
- 245 East Tabernacle
- City Office Outbound 185 East 200 North
- Opera House 15 East 200 North
- 244 West 200 North
- SW Behavioral Health Ctr 202 North 500 West
- 402 North 500 West
- Subway Outbound 630 West 500 North
- Sunset Corner 1091 North Bluff Street
- Subway Inbound 631 West 500 North
- 955 East 700 South
- Sandtown 400 North 500 West
- Ace Hardware 495 West 200 North
- Catholic Church 261 West 200 North
- Post Office 50 East 200 North
- City Office Inbound 190 East 200 North
- 210 East Tabernacle
- 420 East Tabernacle
- 710 East Tabernacle
- 990 East Tabernacle
- Verizon Store 1018 W Sunset Blvd
- 1300 West Sunset Blvd
- Carls Jr 1624 West Sunset Blvd
- Lin's Marketplace 1930 West Sunset Blvd
- Sunset/Lava Flow 2290 West Sunset Blvd
- Snow Canyon Middle School Lava Flow Dr
- Snow Canyon High School Lava Flow Dr
- 1720 North Lava Flow Dr
- 2000 North Lava Flow Dr
- 1957 North 2100 West
- Firehouse Park 2035 West 1800 North
- 1912 West 1575 North
- Sierra Pointe 1465 North 2100 West
- 1925 West 1465 North
- 1835 West 1230 North - Paradise Canyon Elementary
- Housing Authority 975 North 1725 West
- 950 North Dixie Downs Rd
- Albertson's Market 745 North Dixie Drive
- 540 North Dixie Drive
- Dixie Dr @ Sunbrook Dr
- Green Valley Market 567 South Valley View Dr
- Intermountain River Rd Clinic 557 South River Rd
- Valley View Dr @ Stonebridge Dr
- 124 North Valley View Dr
- Summer Hills Apts 320 North Valley View Dr
- 540 North Valley View Dr
- 970 North Valley View Dr
- Cache Valley Bank - Sunset @ Valley View
- 1205 North 1650 West - Royal Oaks
- 390 W Old Highway 91
- 1075 South 200 East
- 955 South 200 East
Over time
Overall score across the last 13 checks — unchanged since 2026-11-20.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-11-09 | 78.2 | first check |
| 2026-11-10 | 78.2 | no change |
| 2026-11-11 | 78.2 | no change |
| 2026-11-12 | 78.2 | no change |
| 2026-11-13 | 78.2 | no change |
| 2026-11-14 | 78.2 | no change |
| 2026-11-15 | 78.2 | no change |
| 2026-11-16 | 78.2 | no change |
| 2026-11-17 | 78.2 | no change |
| 2026-11-18 | 78.2 | no change |
| 2026-11-19 | 78.2 | no change |
| 2026-11-20 | 78.2 | no change |
| 2026-11-21 | 78.2 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- 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.
| Checked | Published file | Service dates through | Grade at the time |
|---|---|---|---|
| 2026-11-09 to 2026-11-21 (13 checks) | 79ad5c2333e5 | 2027-12-31 | Current rubric: see the trend above |
| 2026-10-02 to 2026-11-06 (35 checks) | 873a2da3c5cb | 2031-01-30 | D, 63.2 under rubric 1.4, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-25 to 2026-10-01 (65 checks) | 873a2da3c5cb | 2031-01-30 | F, 58.6 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-13 to 2026-07-24 (9 checks) | 873a2da3c5cb | 2031-01-30 | F, 58.6 under rubric 1.2, an earlier scoring contract; not comparable with today’s grade |
| 2026-06-19 to 2026-07-12 (24 checks) | 873a2da3c5cb | 2031-01-30 | F, 58.6 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade |
Everything we checked
5 findings, ordered by severity.
Show every finding
- Warning416 instances
416 of 416 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible stops, riders need to know the bus itself can take them.
Fix: Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. (A default or per-trip field in your export.)
Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide for scorecard_wheelchair_accessible_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning370 instances
370 of 416 trips have no headsign, the text that tells riders where the bus 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)
- Warning171 instances
171 of 171 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 for scorecard_wheelchair_boarding_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference 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)
- Info416 instances
Unsorted stop times (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unsorted_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: unsorted_stop_times · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
How we measured this
Checked for changes 18 hours ago; last changed 12 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.
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.
NTD GTFS readiness Ready
Published at a public URL, valid, current, and identified with agency_id: the four feed checks for RY2026 all hold here. Only your own D-10 and P-50 filings make that official; this is a heads-up, not a determination.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Ready
- Service data covers the next 405 days.
- 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 416 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. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 405 days.
- Accessible Not yet
- States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.
A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.
Clears the Google and Apple Maps four-week coverage bar. This feed has 404 days of service ahead, clearing the four-week (28-day) window Maps asks for. No validator errors either, so riders keep seeing this agency in their trip planners; warnings lower the grade here but do not remove a feed from Maps.
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 99 / 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 100 / 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 32 / 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 Utah portfolio: the same scorecards for every feed we track in that group, on one free page.
Similar feeds in Utah
Other scorecards in Utah, starting with the same kind of service at a similar size. Listed for comparison, not ranked.
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-utah/2026-11-21.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-21. 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.