← All agencies

Feed status · checked 2026-08-01

Utah Transit Authority (UTA)

Based on the feed this agency publishes

Service mode Tram + Rail + Bus

FDCBA

37.2 / 100

down 0.5 since 2026-07-31

Catalogued in Utah.

Expires in 14 daysAccessibility gapsRealtime not yet published

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 66 minutes ago; last changed 4 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

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.

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

Fix 02

Re-generate shape distances in your export; flag to your vendor if it persists.Likely your export tool

Some trips have stop times whose distances along the route go backwards. Apps can show transit vehicles jumping backwards or mis-order stops.

⏱ Usually an export-tool fix, not hand editing.worth about +24 points in its category

Fix 03

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

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 runs out in 14 day(s).
Next action: Re-export with a validity window that reaches at least 60 days out.
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

Agency: Utah Transit Authority (UTA)
Finding: scorecard_feed_expiring_soon
Feed evidence: Service data runs out in 14 day(s).
Why it matters: When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.
Requested change: Re-export with a validity window that reaches at least 60 days out.
Recheck: Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Evidence: https://gtfsscorecard.org/agency/utah-transit-authority-uta/?finding=scorecard_feed_expiring_soon#finding-handoff

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 with a validity window that reaches at least 60 days out. · 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. See this feed's finding-clearance log.
Re-generate shape distances in your export; flag to your vendor if it persists.
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. See this feed's finding-clearance log.
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. See this feed's finding-clearance log.

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 46.7% 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.

Hi,

Our GTFS feed (Utah Transit Authority (UTA)) scored F (37.2 out of 100) on the GTFS Scorecard. Could you review these in our export settings:

1. Re-export with a validity window that reaches at least 60 days out.
   What: Service data runs out in 14 day(s).
   Finding code: scorecard_feed_expiring_soon
   Guide: https://gtfsscorecard.org/fix/scorecard_feed_expiring_soon/

2. Re-generate shape distances in your export; flag to your vendor if it persists.
   What: Some trips have stop times whose distances along the route go backwards.
   Finding code: decreasing_or_equal_stop_time_distance

3. 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.
   What: The feed contains no fare information.
   Finding code: scorecard_no_fare_data
   Guide: https://gtfsscorecard.org/fix/scorecard_no_fare_data/

Full scorecard: https://gtfsscorecard.org/agency/utah-transit-authority-uta/

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.

Hi Utah Transit Authority (UTA) team,

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.

The fix is usually one export setting: Re-export with a validity window that reaches at least 60 days out.

This came from your GTFS data quality scorecard, which checks the feed you publish and lists the fixes in plain language: https://gtfsscorecard.org/agency/utah-transit-authority-uta/

Score by category

Correctness26.0 / 100

The MobilityData validator flagged 9 kinds of issue across 2127 instances (65 error, 2062 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 experience64.1 / 100

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

Accessibility66.7 / 100

47% of stops state accessibility (47% marked accessible). Reflects what the feed states, 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 5436 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.

821 (teal)
451 (red)
455 (teal)
470 (teal)
473 (red)
2 (green)
223 (teal)
227 (teal)
F94 (teal)
21 (green)
54 (teal)
62 (teal)
72 (teal)
604 (teal)
612 (green)
613 (teal)
626 (teal)
627 (teal)
F638 (teal)
630 (teal)
640 (teal)
806 (red)
807 (red)
33 (green)
35 (green)
45 (teal)
871 (teal)
509 (teal)
200 (green)
209 (green)
205 (teal)
213 (teal)
F618 (teal)
513 (red)
240 (teal)
248 (teal)
F556 (teal)
F570 (teal)
F578 (teal)
822 (red)
830X (teal)
862 (teal)
831 (teal)
833 (teal)
805 (red)
850 (green)
704 (green)
834 (teal)
750 (pink)
551 (red)
201 (teal)
720 (gray)
217 (green)
17 (teal)
9 (green)
220 (teal)
218 (teal)
F590 (teal)
F514 (teal)
667 (teal)
47 (teal)
701 (teal)
628 (teal)
994 (black)
F620 (teal)
F453 (teal)
4 (teal)
601 (teal)
703 (red)
F232 (teal)
F11 (teal)
F525 (teal)
F202 (teal)
472 (red)
1 (green)
50X (teal)
602 (teal)
603X (teal)
823 (teal)
39 (green)
417 (teal)
126 (teal)
219 (teal)
625 (teal)
645 (teal)

Routes in Utah Transit Authority (UTA)'s feed
Route	Type	Line color
821 SOUTH COUNTY/PROVO STATION	Bus	teal
451 TOOELE FAST BUS	Bus	red
455 U OF U/DAVIS COUNTY/WSU	Bus	teal
470 OGDEN - SALT LAKE INTERCITY	Bus	teal
473 SLC - OGDEN HWY 89 EXPRESS	Bus	red
2 200 SOUTH	Bus	green
223 2300 EAST/ HOLLADAY BLVD	Bus	teal
227 2700 WEST	Bus	teal
F94 9400 SOUTH FLEX	Bus	teal
21 2100 SOUTH / 2100 EAST	Bus	green
54 5400 SOUTH	Bus	teal
62 6200 SOUTH	Bus	teal
72 7200 SOUTH	Bus	teal
604 WEST OGDEN	Bus	teal
612 WASHINGTON BLVD	Bus	green
613 WEBER INDUSTRIAL PARK	Bus	teal
626 WEST ROY / WSU DAVIS	Bus	teal
627 CLFD STATION / FRUIT HEIGHTS PNR	Bus	teal
F638 THE BRIGHAM CITY Flex	Bus	teal
630 BRIGHAM CITY/ OGDEN COMMUTER	Bus	teal
640 LAYTON HILLS MALL / WSU OGDEN CAMP	Bus	teal
806 EAGLE MTN/SARATOGA SPR/LEHI STN/UVU	Bus	red
807 NORTH COUNTY/LEHI STATION/UVU	Bus	red
33 3300 SOUTH	Bus	green
35 3500 SOUTH	Bus	green
45 4500 SOUTH	Bus	teal
871 TECH CORRIDOR RAIL CONNECTOR	Bus	teal
509 900 W SHUTTLE	Bus	teal
200 STATE STREET NORTH	Bus	green
209 900 EAST / 9TH Ave	Bus	green
205 500 EAST	Bus	teal
213 1300 EAST	Bus	teal
F618 OGDEN BDO FLEX	Bus	teal
513 INDUSTRIAL BUSINESS PARK SHUTTLE	Bus	red
240 4000 WEST/ DIXIE VALLEY	Bus	teal
248 4800 WEST	Bus	teal
F556 5600 WEST FLEX	Bus	teal
F570 7000 SOUTH FLEX	Bus	teal
F578 7800 SOUTH FLEX	Bus	teal
822 SOUTH UTAH COUNTY BYU/UVU LIMITED	Bus	red
830X UTAH VALLEY EXPRESS	Bus	teal
862 OREM EAST/WEST	Bus	teal
831 PROVO GRANDVIEW	Bus	teal
833 AIRPORT/PROVO STATION	Bus	teal
805 SANTAQUIN/PAYSON/SF/PROVO STN/UVU	Bus	red
850 STATE STREET	Bus	green
704 Green Line	Tram / light rail	green
834 VINEYARD/RIVERWOODS/ PROVO STATION	Bus	teal
750 FrontRunner	Rail	pink
551 INTERNATIONAL CENTER	Bus	red
201 STATE STREET SOUTH	Bus	teal
720 S-Line	Tram / light rail	gray
217 REDWOOD ROAD	Bus	green
17 1700 SOUTH	Bus	teal
9 900 SOUTH	Bus	green
220 HIGHLAND DRIVE / 1100 EAST	Bus	teal
218 SOUTH JORDAN	Bus	teal
F590 9000 SOUTH FLEX	Bus	teal
F514 JORDAN GATEWAY FLEX	Bus	teal
667 LAGOON / STATION PARK SHUTTLE	Bus	teal
47 4700 SOUTH	Bus	teal
701 Blue Line	Tram / light rail	teal
628 CLEARFIELD / LAYTON WESTSIDE	Bus	teal
972 BINGHM JNCT/SOL BRIGHTN	Bus	black (no shape in feed)
994 90TH SO TRAX/SNWBRD/ALTA	Bus	black
F620 WEST HAVEN FLEX	Bus	teal
F453 TOOELE SLC FLEX	Bus	teal
4 400 SOUTH	Bus	teal
601 OGDEN TROLLEY	Bus	teal
703 Red Line	Tram / light rail	red
F232 3200 WEST FLEX	Bus	teal
F11 11TH AVENUE FLEX	Bus	teal
F525 MIDVALE FLEX	Bus	teal
F202 SANDY PARKWAY FLEX	Bus	teal
472 RIVERDALE / SALT LAKE EXPRESS	Bus	red
1 South Temple	Bus	green
50X MID-VALLEY CONNECTOR BRT	Bus	teal
602 OGX WILDCAT SHUTTLE	Bus	teal
603X Ogden Express (OGX)	Bus	teal
823 SPVL/SPFK	Bus	teal
39 3900 SOUTH	Bus	green
417 NORTH REDWOOD RD	Bus	teal
126 12600 SOUTH	Bus	teal
219 South Redwood Rd	Bus	teal
625 ATC / HARRISON BLVD / WSU	Bus	teal
645 MONROE BLVD	Bus	teal

List every stop

Washington Blvd Station
University Hospital
Redwood Rd / 700 N (SB)
State St / 100 S (NB)
State St / University Pkwy (SB)
State St / 1500 S (SB)
State St / 1600 S (SB)
State Rd / 1300 W (WB)
State St / North County Blvd (WB)
State St / 860 E (WB)
State St / 740 E (WB)
State St / 700 E (WB)
State St / 500 E (WB)
State St / 300 E (WB)
Main St / American Fork Center St (
Main St / 100 W (WB)
Main St / 300 W (WB)
Main St / Columbia Village (WB)
State St / Green Spring Way (NB)
State St / 800 N (NB)
State St / Green Spring Way (SB)
State St / Columbia Village (EB)
Main St / 300 W (EB)
500 W / 300 N (NB)
500 W / 500 N
500 W / 800 N (NB)
500 W / 940 N (NB)
Utah Valley Hospital (NB)
State St / Riverside Ave (NB)
State St / Grandview Ln (NB)
State St / 1850 N (NB)
State St / 1100 N (NB)
State St / 1950 N (NB)
State St / 1851 S (NB)
State St / 1700 S (NB)
State St / 1600 S (NB)
State St / University Pkwy (NB)
State St / 1200 N (NB)
UVU Fulton Library (WB)
1200 W / 1300 N (NB)
1200 W / 1420 (NB)
Main St / 100 W (EB)
State St / 300 E (EB)
State St / 400 E (EB)
State St / 500 E (EB)
State St / 740 E (EB)
State St / 860 E (EB)
State St / North County Blvd (EB)
Pleasant Grove Center St / State St
Center St / 400 W (EB)
Center St / 200 W (EB)
Center St / 100 W (EB)
State St / 100 E (SB)
State St / 700 N (SB)
State St / 600 N (SB)
State St / 500 N (SB)
State St / 400 N (SB)
State St / 2000 N (NB)
State St / 800 W (SB)
State St / 1800 N (SB)
State St / 1400 N (SB)
State St / 1000 N (SB)
State St / 600 N (SB)
State St / 100 N (SB)
State St / 200 S (SB)
State St / 600 S (SB)
State St / Grandview Ln (SB)
State St / Riverside Ave (SB)
500 W / 1050 N (SB)
500 W / 940 N (SB)
500 W / 800 N (SB)
500 W / 500 N (SB)
500 W / 300 N (SB)
100 N / 100 W (EB)
550 W / 1800 N (SB)
BYU Central Campus Station (NB)
University Ave / Center St (SB)
University Ave / 300 S (SB)
100 W / 920 S (SB)
University Ave / 450 S (NB)
University Ave / 300 S (NB)
800 E / 1169 S (NB)
800 E / 900 S (NB)
State St / 1700 S (SB)
State St / 1800 S (SB)
State St / 1950 N (SB)
State St / 2000 N (SB)
700 N / 600 E (EB)
BYU Central Campus Station (SB)
550 W / 1800 N (NB)
550 W / University Pkwy (NB)
University Pkwy / Main St (WB)
University Pkwy / 200 W (WB)
Canyon Creek Pkwy / Commerce Way (S
Canyon Creek Pkwy / Commerce Way (N
800 E / 1150 S (SB)
State St / 300 W (EB)
University Ave / 960 N (SB)
University Ave / 700 N (NB)
Main St / 1000 N (SB)
Main Street / 200 N (SB)
Center St / Main St (EB)
Center St / 400 E (EB)
800 E / 700 N (NB)
800 E / 700 N (SB)
Center St / 400 E (WB)
Center St / 100 E (WB)
State St / 1200 N (SB)
Main St / 400 N (NB)
1000 N / Main Street (EB)
State St / 300 W (WB)
State St / 700 E (EB)
State St / 1300 W (EB)
State St / 700 S (SB)
State St / 800 S (NB)
State St / 600 S (NB)
State St / 400 S (NB)
State St / 200 S (NB)
State St / Center St (NB)
State St / 200 N (NB)
State St / 600 N (NB)
State St / 1400 N (NB)
State St / 1600 N (NB)
State St / 1800 N (NB)
State St / Lindon Main St (NB)
State St / 300 N (NB)
State St / 400 N (NB)
State Rd / 800 N (NB)
State Rd / 790 S (NB)
State Rd / 700 S (NB)
Main St / 50 S (NB)
Center St / 50 W (WB)
Center St / 200 W (WB)
State St / 1850 N (SB)
1200 W / 400 S (SB)
1200 W / 600 S (SB)
UVU Institute (EB)
800 S / State St (EB)
State St / 500 N (SB)
800 E / 800 S (SB)
800 E / 1000 S (SB)
900 E / 400 S (SB)
900 E / 460 S (SB)
State Street / 900 E (NB)
State St / 400 N (SB)
1750 W / 1300 S (NB)
Canyon Creek Pkwy / Spanish Fork Pk
State Street / 300 S (SB)
State St / Orem Center St (SB)
900 E / 50 S (SB)
Canyon Creek Pkwy / Spanish Fork Pk
300 S / 400 E (WB)
1460 N / 1500 W (WB)
1460 N / 1900 W (WB)
1460 N / Grand Ave (WB)
2100 W / 1730 N (NB)
Main St / 1820 S (NB)
Main St / 1600 S (NB)
Main St / 1450 S (NB)
Main St / 1400 S (NB)
1430 S / 400 W (WB)
1430 S / 550 W (WB)
1430 W / Sandhill Rd (WB)
Sandhill Rd / 1350 S (NB)
1430 S / Sandhill Rd (EB)
1430 S / 550 W (EB)
1430 S / 400 W (EB)
Main St / University Pkwy (SB)
Main St / 1450 S (SB)
Main St / 1600 S (SB)
Main St / 1820 S (SB)
2100 W / 1730 N (SB)
Main St / 1600 N (SB)
1460 N / Grand Ave (EB)
1460 N / 1900 W (EB)
900 E / 300 S (NB)
900 E / 150 S (NB)
2230 N / 400 W (WB)
900 E / Center St (NB)
900 E / 200 N (NB)
900 E / 300 N (NB)
900 E / 450 N (NB)
900 E / 450 N (SB)
900 E / 300 N (SB)
900 E / 200 N (SB)
900 E / Center St (SB)
800 E / 800 S (NB)
800 E / 620 S (NB)
800 E / 500 S (NB)
1600 N / 110 W (WB)
1600 N / 280 W (WB)
1600 N / 400 W (WB)
1600 N / 1040 N (WB)
1600 N / 1040 N (EB)
1600 N / 800 W (EB)
1600 N / State St (EB)
1600 N / 280 W (EB)
1600 N / 110 W (EB)
1200 N / 800 E (EB)
State St / 1320 S (SB)
Main St / 900 N (NB)
Main St / 600 N (SB)
400 N / Main St (EB)
400 N / 100 E (EB)
400 N / 200 E (EB)
400 N / 400 E (EB)
Main St / 400 S (SB)
400 E / 200 N (SB)
Main St / Center St (SB)
400 E / Center St (SB)
400 E / 200 S (SB)
400 E / 400 S (SB)
400 S / 200 E (WB)
Main St / 200 S (SB)
800 E / 600 N (SB)
800 E / State Rd (SB)
800 E / 200 N (SB)
800 E / Center St (SB)
Center St / 600 E (WB)
Main St / 140 S (SB)
Main St / 200 S (SB)
Main St / 300 S (SB)
Main St / 500 S (SB)
Highway 198 / 400 N (SB)
Highway 198 / Sheen Rd (SB)
100 N / 1000 E (WB)
100 N / 900 E (WB)
100 N / 600 E (WB)
100 N / 400 E (WB)
100 N / 200 E (WB)
100 W / 100 N (SB)
100 W / 400 S (SB)
100 W / 700 S (SB)
100 W / 700 S (NB)
100 W / 400 S (NB)
100 W / 200 S (NB)
100 N / Main St (EB)
100 N / 200 E (EB)
100 N / 400 E (EB)
100 N / 500 E (EB)
100 N / 600 E (EB)
100 N / 900 E (EB)
100 N / 1000 E (EB)
Highway 198 / Sheen Rd (NB)
Highway 198 / 400 N (NB)
Main St / 500 S (NB)
Main St / 300 S (NB)
Main St / 200 S (NB)
Main St / 100 S (NB)
Center St / 600 E (EB)
and 5186 more (see the full list on the map or in the GeoJSON)

Over time

Overall score across the last 4 checks — down 0.5 since 2026-07-31.

Show the numbers

Overall score by check, with the change from the previous check
Check	Score	Change
2026-07-25	41.9	first check
2026-07-30	38.1	down 3.8
2026-07-31	37.7	down 0.4
2026-08-01	37.2	down 0.5

What changed since your last check

Correctness no change
Freshness down 1.7
Rider experience no change

What changed in this feed

Overall score fell 0.5 points 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.

What changed over time

On 2026-07-25 this feed started at grade F. On 2026-08-01 the grade held, though the score fell from 42 to 37. As of 2026-08-01 it holds grade F.

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

2026-07-30 Score fell 4 points, freshness fell 8 points.

Everything we checked

14 findings, ordered by severity.

Show every finding

Error65 instances
Some trips have stop times whose distances along the route go backwards.
Apps can show transit vehicles jumping backwards or mis-order stops.
Fix: Re-generate shape distances in your export; flag to your vendor if it persists. (Usually an export-tool fix, not hand editing.)
Finding code: decreasing_or_equal_stop_time_distance · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning2895 instances
2895 of 5436 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)
Warning1693 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)
Warning270 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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning58 instances
Some scheduled trips move faster between stops than a transit vehicle can.
Usually a typo'd stop time; riders get arrival times no transit vehicle can meet.
Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)
Finding code: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning55 instances
55 of 11053 trips lack rider-facing destination or direction text.
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 · See GTFS Best Practices (opens GTFS Best Practices on an external site)
Warning17 instances
Some stops sit far from the route line they belong to.
Trip planners may draw the transit vehicle route through the wrong path or point riders to the wrong boarding location.
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)
Warning16 instances
Some stops exist in the feed but no trip ever stops at them.
Riders may walk to a stop where no transit vehicle is scheduled to arrive.
Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)
Finding code: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning6 instances
The feed contains route shapes no trip uses.
Harmless to riders, but it bloats the feed and suggests stale export data.
Fix: Turn on 'remove unused shapes' (or the like) in your export tool. (One setting.)
Finding code: unused_shape · 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 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 · 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
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 · 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 · 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 Needs attention

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

Published Ready: Published at a public URL.
Valid Needs attention: 1 validator error to resolve.
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 11053 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. 1 validator error to resolve. Service data runs out in 14 days; renew to qualify. States wheelchair access on 47% of stops and 100% of trips; the mark needs 90% of each.

Valid Not yet: 1 validator error to resolve.
Current Not yet: Service data runs out in 14 days; renew to qualify.
Accessible Not yet: States wheelchair access on 47% of stops and 100% of trips; the mark needs 90% of each.

In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.

A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.

Can riders use it?

Checks beyond structural validation: places where the feed is valid but a rider still could not travel.

16 of 5436 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.

These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.

At risk for the Google and Apple Maps four-week coverage bar. This feed has 14 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. The feed also carries 65 validator errors, the other thing Maps checks at onboarding; the findings below name each fix.

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 26 / 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 64 / 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.

[![Utah Transit Authority (UTA) GTFS data quality grade: F](https://gtfsscorecard.org/data/artifacts/utah-transit-authority-uta/badge.svg)](https://gtfsscorecard.org/agency/utah-transit-authority-uta/)

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/utah-transit-authority-uta/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.

GTFS Scorecard. (2026). Utah Transit Authority (UTA) GTFS feed-quality record, dated 2026-08-01 (grade F (37.2/100), rubric v1.3, gtfs-validator 8.0.1, reader archive profile raw-v1, feed sha256 e10dbf6590b0…). https://gtfsscorecard.org/data/artifacts/utah-transit-authority-uta/2026-08-01.json

@misc{gtfsscorecard-utah-transit-authority-uta-2026-08-01,
  title        = {Utah Transit Authority (UTA) GTFS feed-quality record},
  author       = {GTFS Scorecard},
  year         = {2026},
  howpublished = {\url{https://gtfsscorecard.org/data/artifacts/utah-transit-authority-uta/2026-08-01.json}},
  note         = {Checked 2026-08-01; rubric v1.3; gtfs-validator 8.0.1; reader archive profile raw-v1; grade F (37.2/100)}
}

Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.