Feed status · checked 2026-08-01
Sacramento Regional Transit (SacRT)
Based on the feed this agency publishes
Service mode Tram + Bus
unchanged since 2026-07-31
Catalogued in California.
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 1 days ago; last changed 38 days ago.
Measured 3 of 4 score categories from the agency's own feed.
How we measured this
Confidence in this measurement: medium.
- Realtime quality was not measured this run. It does not count against the grade.
- The feed was downloaded from the agency's own URL.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.Likely your export tool
Service data ended 483 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
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
2821 of 2821 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.
⏱ 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
5052 of 5052 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the transit vehicle itself can take them.
⏱ A default or per-trip field in your export.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 ended 483 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
- 2821 of 2821 stops don't say whether a wheelchair user can board there.
- Next action
- Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
- 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
- 5052 of 5052 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
- 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.
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. · 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.
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. · 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 483 days ago.
- 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.
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 7 kinds of issue across 3173 instances (0 error, 3171 warning, 2 informational).
Service data ended 483 day(s) ago. Trip planners have likely already dropped this feed.
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
24 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (10, 21, 26, 67, 82, 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.
2747 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("NORTHGATE BLVD & WINTER GARDEN AVE (NB)", "I-5 FWY & SEAMAS AVE (NB)", "Q ST & 5TH ST (EB)", 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 2821 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 (green)
- 10 (red)
- 11 (green)
- 13 (yellow)
- 15 (purple)
- 19 (green)
- 20 (blue)
- 21 (red)
- 23 (yellow)
- 25 (purple)
- 26 (red)
- 30 (yellow)
- 33 (red)
- 38 (green)
- 51 (green)
- 56 (green)
- 61 (yellow)
- 62 (green)
- 67 (orange)
- 68 (green)
- 72 (purple)
- 75 (yellow)
- 78 (blue)
- 81 (purple)
- 82 (red)
- 84 (yellow)
- 86 (green)
- 87 (purple)
- 88 (red)
- 93 (yellow)
- 102 (pink)
- 103 (pink)
- 105 (pink)
- 106 (pink)
- 109 (pink)
- 113 (blue)
- 124 (blue)
- 129 (pink)
- 134 (pink)
- 137 (pink)
- 138 (pink)
- 142 (pink)
- 161 (pink)
- 175 (blue)
- 176 (blue)
- 177 (blue)
- 205 (pink)
- 206 (pink)
- 210 (pink)
- 211 (pink)
- 212 (pink)
- 213 (pink)
- 214 (pink)
- 215 (blue)
- 226 (pink)
- 227 (pink)
- 228 (pink)
- 246 (pink)
- 247 (pink)
- 248 (pink)
- 252 (pink)
- 255 (pink)
- Gold (yellow)
- Green (green)
- Blue (blue)
| Route | Type | Line color |
|---|---|---|
| 1 GREENBACK | Bus | green |
| 10 FSL Route 10 | Bus | red |
| 11 NATOMAS/LAND PARK | Bus | green |
| 13 NATOMAS/ARDEN | Bus | yellow |
| 15 DEL PASO HEIGHTS | Bus | purple |
| 19 RIO LINDA | Bus | green |
| 20 FSL Route 20 | Bus | blue |
| 21 SUNRISE | Bus | red |
| 23 EL CAMINO | Bus | yellow |
| 25 MARCONI | Bus | purple |
| 26 FULTON | Bus | red |
| 30 J STREET | Bus | yellow |
| 33 DOS RIOS | Bus | red |
| 38 TAHOE PARK | Bus | green |
| 51 STOCKTON/BROADWAY | Bus | green |
| 56 MEADOWVIEW | Bus | green |
| 61 FRUITRIDGE | Bus | yellow |
| 62 FREEPORT | Bus | green |
| 67 FRANKLIN | Bus | orange |
| 68 OAK PARK | Bus | green |
| 72 ROSEMONT | Bus | purple |
| 75 MATHER | Bus | yellow |
| 78 BUTTERFIELD | Bus | blue |
| 81 FLORIN | Bus | purple |
| 82 NORTHROP/MORSE | Bus | red |
| 84 WATT | Bus | yellow |
| 86 GRAND | Bus | green |
| 87 HOWE | Bus | purple |
| 88 WEST EL CAMINO | Bus | red |
| 93 HILLSDALE | Bus | yellow |
| 102 RIVERSIDE COMMUTER | Bus | pink |
| 103 RIVERSIDE EXPRESS | Bus | pink |
| 105 ELSIE | Bus | pink |
| 106 LAND PARK COMMUTER | Bus | pink |
| 109 HAZEL EXPRESS | Bus | pink |
| 113 NORTH MARKET COMMUTER | Bus | blue |
| 124 SUNRISE COMMUTER | Bus | blue |
| 129 ARDEN COMMUTER | Bus | pink |
| 134 McKINLEY COMMUTER | Bus | pink |
| 137 UCDMC | Bus | pink |
| 138 CAUSEWAY CONNECTION | Bus | pink |
| 142 AIRPORT | Bus | pink |
| 161 BELVEDERE | Bus | pink |
| 175 CordoVan - Anatolia-Sunridge | Bus | blue |
| 176 CordoVan - Anatolia-Kavala Ranch | Bus | blue |
| 177 CordoVan - Villages | Bus | blue |
| 205 FRUITRIDGE RD - FREEPORT BLVD | Bus | pink |
| 206 12TH AVE - SUTTERVILLE RD | Bus | pink |
| 210 LA RIVIERA DR | Bus | pink |
| 211 COLLEGE GREENS | Bus | pink |
| 212 14TH AVE - 21ST AVE | Bus | pink |
| 213 FRUITRIDGE RD - STOCKTON BLVD | Bus | pink |
| 214 BROADWAY - STOCKTON BLVD | Bus | pink |
| 215 14TH AVE - FLORIN TOWNE | Bus | blue |
| 226 POCKET RD - RIVERSIDE BLVD | Bus | pink |
| 227 SOUTH LAND PARK - GREENHAVEN DR | Bus | pink |
| 228 GLORIA DR - RUSH RIVER DR | Bus | pink |
| 246 MEADOWVIEW - GREENHAVEN | Bus | pink |
| 247 21ST ST - FLORIN RD | Bus | pink |
| 248 MEADOWVIEW RD - RUSH RIVER DR | Bus | pink |
| 252 FREEPORT - FRUITRIDGE - ML KING | Bus | pink |
| 255 LA RIVIERA - COLLEGE GREENS | Bus | pink |
| Gold Downtown - Folsom | Tram / light rail | yellow |
| Green 13th - Richards/Township 9 | Tram / light rail | green |
| Blue Meadowview - Watt/I-80 | Tram / light rail | blue |
List every stop
- SLP DR & 43RD AVE (SB)
- SLP DR & 43RD AVE (SB)
- SLP DR & 47TH AVE (SB)
- SLP DR & SILVER LAKE DR (SB)
- ANATOLIA DR & HERODIAN DR (NB)
- 13TH ST & FAY CIR (SB)
- 13TH ST & FAY CIR (SB)
- 13TH ST & SAN CLEMENTE WAY (NB)
- 56TH AVE & HAVENHURST DR (WB)
- HAVENHURST DR & FLINTWOOD WAY (NB)
- HAVENHURST DR & GREENHAVEN DR (WB)
- GREENHAVEN DR & GREENWAY CIR (SB)
- GREENHAVEN DR & GREENSTAR WAY (SB)
- GREENHAVEN DR & PARK RANCH WAY (SB)
- GREENHAVEN DR & FLORIN RD (SB)
- ANATOLIA DR & HERODIAN DR (SB)
- GREENHAVEN DR & WINDBRIDGE DR (SB)
- GREENHAVEN DR & LA FLEUR WAY (SB)
- TIMBERLAND DR & CANYONLANDS DR (SB)
- SWALE RIVER WAY & GLORIA DRIVE (NB)
- HAVENHURST DR & GREENHAVEN DR (EB)
- HAVENHURST DR & WESTMORELAND WAY (SB)
- 56TH AVE & HAVENHURST DR (EB)
- 13TH ST & 56TH AVE (NB)
- 13TH ST & SAN CLEMENTE WAY (NB)
- 13TH ST & GAGLE WAY (NB)
- 13TH ST & TUGGLE WAY (EB)
- SLP DR & 13TH ST (WB)
- NORTHGATE BLVD & WINTER GARDEN AVE (NB)
- SLP DR & SILVER LAKE DR (NB)
- SLP DR & 47TH AVE (NB)
- SLP DR & 47TH AVE (NB)
- SLP DR & 43RD AVE (NB)
- SLP DR & 40TH AVE (NB)
- SLP DR & 35TH AVE (NB)
- SLP DR & NEVIS CT (NB)
- SLP DR & PLEASANT DR (NB)
- TIMBERLAKE WY & BRUCEVILLE RD (WB)
- SLP DR & CRESTWOOD WAY (SB)
- SLP DR & PLEASANT DR (EB)
- SLP DR & RIDGEWAY DR (NB)
- SLP DR & CRESTWOOD WAY (NB)
- SLP DR & VOLZ DR (NB)
- SLP DR & PARKSIDE CT (NB)
- LAND PARK DR & SUTTERVILLE RD (NB)
- LAND PARK DR & 16TH AVE (NB)
- LAND PARK DR & 13TH AVE (NB)
- LAND PARK DR & 11TH AVE (NB)
- LAND PARK DR & 9TH AVE (NB)
- I-5 FWY & SEAMAS AVE (NB)
- LAND PARK DR & 7TH AVE (NB)
- LAND PARK DR & CORDANO WAY (NB)
- LAND PARK DR & VALLEJO WAY (NB)
- LAND PARK DR & 3RD AVE (NB)
- LAND PARK DR & CARAMAY WAY (NB)
- LAND PARK DR & 2ND AVE (NB)
- LAND PARK DR & LARKIN WAY (NB)
- LOUIS LANE & ORLANDO AVE (NB)
- LAND PARK DR & BROADWAY (NB)
- 16TH ST & BROADWAY (NB)
- 16TH ST & V ST (NB)
- 16TH ST & T ST (NB)
- 16TH ST & S ST (NB)
- 16TH ST & R ST (NB)
- LOUIS LANE & ORLANDO AVE (NB)
- Q ST & 5TH ST (EB)
- LOUIS LANE & ORLANDO AVE (NB)
- BUTANO DR & EL CAMINO AVE (SB)
- BUTANO DR & WATT AVE (WB)
- BUTANO DR & PARK TOWNE CIR (WB)
- BUTANO DR & COTTAGE WAY (SB)
- BUTANO DR & COTTAGE WAY (SB)
- COTTAGE WAY & KINCAID WAY (WB)
- Q ST & 7TH ST (EB)
- HERITAGE LN & EXPOSITION BLVD (NB)
- RESPONSE RD & CHALLENGE WAY (EB)
- HERITAGE LN & RESPONSE RD (NB)
- Q ST & 9TH ST (EB)
- ETHAN WAY & ALTA ARDEN (NB)
- ETHAN WAY & COTTAGE WAY (NB)
- ETHAN WAY & KEITH WAY (NB)
- ETHAN WAY & DELMA WAY (NB)
- EL CAMINO AVE & ETHAN WAY (EB)
- ARDEN WAY & ROYAL OAKS DR (EB)
- ARDEN WAY & BLUMENFELD DR (EB)
- ARDEN FAIR MALL & TERMINAL (NB)
- Q ST & 10TH ST (EB)
- ARDEN WAY & CHALLENGE WAY (EB)
- E BIDWELL ST & NESMITH CT PAST COLLEGE ENTRANCE (SB)
- ARDEN WAY & ETHAN WAY (EB)
- RILEY ST & GLENN DR (NB)
- ARDEN WAY & HOWE AVE (EB)
- IRON POINT RD & BLACK DIAMOND DR (WB)
- IRON POINT RD & FOLSOM BLVD (WB)
- RILEY ST & NATOMA ST (SB)
- ARDEN WAY & BELL ST (EB)
- SCHOLAR WAY & FLC PARKING LOT/ADMIN BLDG (EB)
- BROADSTONE PKWY & E BIDWELL ST (WB)
- E BIDWELL ST & POWER CENTER DR (SB)
- PALLADIO PKWY & BTW BROADSTONE & IRON POINT RD (SB)
- CREEKSIDE DR & 1600 CREEKSIDE DR (EB)
- ARDEN WAY & CLINTON RD (EB)
- CREEKSIDE DR & 1650 CREEKSIDE DR (EB)
- N LEXINGTON DR & AINSWORTH WAY (EB)
- N LEXINGTON DR & WESLEYAN WAY (EB)
- AMERICAN RIVER CANYON DR & RIVER RIDGE WAY (NB)
- PREWETT DR & SILBERHORN DR (EB)
- SILBERHORN DR & S LEXINGTON DR (SB)
- AMERICAN RIVER CANYON DR & BOBWHITE LN (NB)
- SCHOLAR WAY & FLC MAIN ENTRANCE (WB)
- ARDEN WAY & FULTON AVE (EB)
- E BIDWELL ST & MONTROSE DR (SB)
- ARDEN WAY & BERKSHIRE WAY (EB)
- AMERICAN RIVER CANYON DRIVE & OAK AVE (NB)
- AMERICAN RIVER CANYON DR & GREY CANYON DR (NB)
- AMERICAN RIVER CANYON DR & BOULDER CANYON WAY (NB)
- MADISON AVE & GREENBACK LANE (WB)
- MAIN AVE & GREENBACK LANE (NB)
- ARDEN WAY & MORSE AVE (EB)
- GREENBACK LN & MADISON AVE (EB)
- WALES DR & E BIDWELL ST (EB)
- ARDEN WAY & PROFESSIONAL DR (EB)
- NATOMA STATION DR & NATOMA STATION DR (NB)
- NATOMA STATION DR & PARKER DR (NB)
- NATOMA STATION DR & TURN PIKE DR (NB)
- NATOMA STATION DR & SEATON DR (NB)
- BLUE RAVINE RD & NATOMA STATION DR (EB)
- BLUE RAVINE RD & SEATON DR (EB)
- PRAIRIE CITY RD & BLUE RAVINE RD (SB)
- PRAIRIE CITY RD & WILLARD DR (SB)
- ARDEN WAY & WATT AVE (EB)
- BROADSTONE PKWY & PALLADIO PKWY (EB)
- EMPIRE RANCH RD & PALOMINO COURT (NB)
- EMPIRE RANCH RD & WOODHEAD ST (NB)
- E NATOMA ST & EMPIRE RANCH RD (WB)
- E NATOMA ST & WESLEY DR (WB)
- E NATOMA ST & BONHILL DR (WB)
- E NATOMA ST & EMPIRE RANCH GOLFCLUB (WB)
- Q ST & 11TH ST (EB)
- ARDEN WAY & LA PLAYA WAY (EB)
- E NATOMA ST & BALLOU CIRCLE (WB)
- RILEY ST & GLENN DR (SB)
- CREEKSIDE DR & OAK AVE PKWY (EB)
- PREWETT DR & KILSBY ST (EB)
- PREWETT DR & N LEXINGTON DR (SB)
- SILBERHORN DR & WENHAM WAY (SB)
- OAK AVE PKWY & CREEKSIDE DR (SB)
- IRON POINT RD & BROADSTONE PKWY (WB)
- ARDEN WAY & LA SIERRA DR (EB)
- IRON POINT LIGHT RAIL STATION & NATOMA STATION DR (WB)
- IRON POINT RD & GROVER RD (EB)
- IRON POINT RD & OAK AVE PKWY (EB)
- IRON POINT RD & ROWBERRY DR (EB)
- IRON POINT RD & ROWBERRY DR (WB)
- IRON POINT RD & OAK AVE PKWY (WB)
- ARDEN WAY & ESPERANZA DR (EB)
- IRON POINT RD & MCADOO DR (WB)
- IRON POINT RD & GROVER RD (WB)
- IRON POINT RD & BROADSTONE PKWY (EB)
- IRON POINT RD & SHOPPING CENTER (EB)
- E BIDWELL ST & POWER CENTER DR (NB)
- OAK AVE PKWY & S. LEXINGTON DR (SB)
- SILBERHORN DR & WENHAM WAY (NB)
- SILBERHORN DR & FAYETTE WAY (NB)
- ARDEN WAY & EASTERN AVE (EB)
- SILBERHORN DR & PREWETT DR (NB)
- PREWETT DR & BTW KILSBY ST & NEWINGTON WAY (WB)
- N LEXINGTON DR & WRENTHAM ST (WB)
- OAK AVE PKWY & S LEXINGTON DR (NB)
- OAK AVE PKWY & N LEXINGTON DR (NB)
- CREEKSIDE DR & 1780 CREEKSIDE DR (EB)
- CREEKSIDE DR & OAK AVE PKWY (WB)
- CREEKSIDE DR & 1715 CREEKSIDE DR (WB)
- CREEKSIDE DR & 1617 CREEKSIDE DR (WB)
- CREEKSIDE DR & E BIDWELL ST (WB)
- ARDEN WAY & SURITA ST (EB)
- E BIDWELL ST & BLUE RAVINE RD (NB)
- RILEY ST & E BIDWELL ST (NB)
- MADISON AVE & 9465 MADISON AVE (WB)
- ARDEN WAY & MISSION AVE (EB)
- IRON POINT RD & PRAIRIE CITY RD (WB)
- SCHOLAR WAY & CAVITT DR (EB)
- HISTORIC FOLSOM LIGHT RAIL STATION & SUTTER ST (NB)
- ARDEN WAY & PALOMA AVE (EB)
- PARKWAY DR & BONANZA LANE (SB)
- PARKWAY DR & SCHIEDIGGER CIRCLE (SB)
- PARKWAY DR & BRIDGE (SB)
- PARKWAY DR & WILLOW BEND RD (WB)
- CAVITT DR & LOTHIAN WAY (SB)
- CAVITT DR & BROADSTONE PKWY (SB)
- BROADSTONE PKWY & SERPA WAY (EB)
- BROADSTONE PKWY & EAGLE WAY (EB)
- BROADSTONE PKWY & EAGLES WAY (WB)
- BROADSTONE PKWY & SERPA WAY (WB)
- CAVITT DR & HILLSWICK WAY (NB)
- CAVITT DR & LOTHIAN WAY (NB)
- OAK AVE PKWY & NORTH LEXINGTON DR (NB)
- PARKWAY DR & HUMBUG CREEK DR (EB)
- PARKWAY DR & KIDDER WAY (EB)
- PARKWAY DR & DALL WAY (EB)
- PARKWAY DR & MORGANITE CT (EB)
- E NATOMA ST & BALLOU CIRCLE (EB)
- E NATOMA ST & FERGUSEN WAY (EB)
- E NATOMA ST & JENKINS WAY (EB)
- E NATOMA ST & BOWEN DR (EB)
- E NATOMA ST & GOLF LINKS DR (EB)
- E NATOMA ST & EMPIRE RANCH RD (EB)
- EMPIRE RANCH RD & WOODHEAD ST (SB)
- EMPIRE RANCH RD & BROADSTONE PKWY (SB)
- PALLADIO PKWY & ACROSS FROM KAISER HOSPITAL (NB)
- Q ST & 13TH ST (EB)
- WALES DR & BTW E BIDWELL & RILEY ST (WB)
- BIDWELL ST & RILEY ST (WB)
- RILEY ST & E BIDWELL ST (SB)
- RILEY ST & WALMART SHOPPING CENTER (SB)
- IRON POINT RD & WILLARD DR (WB)
- BLUE RAVINE RD & JORGENSEN RD (WB)
- BLUE RAVINE RD & BIG VALLEY RD (WB)
- E NATOMA ST & WESLEY DR (EB)
- N LEXINGTION DR & WESLEYAN WAY (WB)
- BLUE RAVINE RD & OAK AVE PKWY (EB)
- IRON POINT RD & BETWEEN MCADOO AND OUTCROPPING (EB)
- COTTAGE WAY & MORSE AVE (EB)
- COTTAGE WAY & KINCAID WAY (EB)
- BUTANO DR & COTTAGE WAY (NB)
- 15TH ST & K ST (SB)
- BUTANO DR & COTTAGE WAY (NB)
- BUTANO DR & PARK TOWNE CIR (EB)
- FAIR OAKS BLVD & TOPP CT (SB)
- FAIR OAKS BLVD & EL CAMINO AVE (SB)
- FAIR OAKS BLVD & FRONTIER WAY (SB)
- FAIR OAKS BLVD & SHELFIELD DR (SB)
- FAIR OAKS BLVD & GARFIELD AVE (SB)
- FAIR OAKS BLVD & WESTMINSTER CT (SB)
- ARDEN WAY & FAIR OAKS BLVD (WB)
- ARDEN WAY & PARK PLACE DR (WB)
- ARDEN WAY & MISSION AVE (WB)
- ARDEN WAY & PLUTO WAY (WB)
- ARDEN WAY & EASTERN AVE (WB)
- ARDEN WAY & CATHAY WAY (WB)
- ARDEN WAY & MAPLE GLEN RD (WB)
- ARDEN WAY & LA PLAYA WAY (WB)
- ARDEN WAY & WATT AVE (WB)
- ARDEN WAY & PROFESSIONAL DR (WB)
- ARDEN WAY & MORSE AVE (WB)
- ARDEN WAY & AVONDALE AVE (WB)
- ARDEN WAY & FULTON AVE (WB)
- 3RD ST & K ST (NB)
- ARDEN WAY & WRIGHT ST (WB)
- ARDEN WAY & BELL ST (WB)
- and 2571 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 | 39.0 | first check |
| 2026-07-30 | 39.1 | up 0.1 |
| 2026-07-31 | 39.1 | no change |
| 2026-08-01 | 39.1 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
What changed in this feed
Overall grade and score held steady since 2026-07-31.
Same feed file as 2026-07-31; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
Everything we checked
13 findings, ordered by severity.
Show every finding
- Error1 instance
Service data ended 483 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)
- Warning5052 instances
5052 of 5052 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible stops, riders need to know the transit vehicle 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 · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning3163 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)
- Warning2821 instances
2821 of 2821 stops don't say whether a wheelchair user can board there.
Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
Fix: Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. (A column in stops.txt; your scheduling software likely has it.)
Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning3 instances
Some service calendars in the feed have already ended.
Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)
Finding code: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
Some 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)
- Warning1 instance
This feed's service calendar runs out within the next 7 days.
When the calendar ends, Google Maps and other trip planners drop your agency entirely. Riders see no service at all.
Fix: Export and publish an updated GTFS feed that covers at least the next 30 days of service. (Usually a re-export from your scheduling software.)
Finding code: feed_expiration_date7_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt lists no contact email and no contact URL.
Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.
Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)
Finding code: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Many of the feed's trips don't run at all in the next 7 days.
It usually means old service periods are still in the export, making the feed bigger and harder to check.
Fix: Trim past service periods the next time you export. (One setting in most export tools.)
Finding code: trip_coverage_not_active_for_next7_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
The feed contains no fare information.
Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
Fix: Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. (A small file for most flat-fare systems.)
Finding code: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info2379 instances
About 2379 stop names are written in ALL CAPS.
Mixed-case names are easier to read in apps and are read more naturally by screen readers.
Fix: Rename stops to mixed case where the language has letter case (for example, 'Central Station'). (Often a bulk fix in your scheduling software.)
Finding code: scorecard_stop_names_all_caps · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info2 instances
The feed includes a file that is not part of the GTFS spec.
Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.
Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)
Finding code: unknown_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
NTD GTFS readiness Not ready
Resolve this before you certify on the D-10. Service data expired 483 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 483 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) Different (allowed)
- Your feed's agency_id is SRTD; your National Transit Database ID is 90019. A feed that serves several agencies (a shared regional feed) can legitimately carry more than one agency_id. The values do not need to equal the five-digit NTD ID, so this difference is allowed and carries no score. Confirm that P-50 crosswalks agency_id SRTD to NTD ID 90019, and keep the feed value stable. Do not change it solely to make the two values equal.
- shapes.txt covers your trips Ready
- All 5052 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 483 days ago. 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 Not yet
- Service data expired 483 days ago.
- 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.
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.
In California, the published guideline is California Transit Data Guidelines. Caltrans' published quality guidelines and compliance checklist; this rubric is anchored to them.
California Minimum GTFS Guidelines checklist (3 of 6 measured items met)
The state's own Data Process Checklist, matched item by item to what this scorecard already measures. An item marked "not measured here" is real ground the checklist covers that this tool does not check; see the official checklist for the full picture.
- Meets Publish GTFS Schedule at a stable, automatically-fetchable URL
The published feed URL downloaded at the last check.
- Not measured here Implement required fields: Fares v2, text-to-speech stop names, shapes.txt, wheelchair_boarding, and Pathways where applicable
This scorecard measures wheelchair_boarding, shapes.txt coverage, fare data, and station pathways separately, below; it does not check the Fares v2 format specifically or text-to-speech stop names.
- Not measured here Achieve a passing score in every category of the MobilityData GTFS Grading Scheme v1
This scorecard automates a proxy for the Grading Scheme's rider-facing fields (see the standards crosswalk) rather than running the scheme itself, which grades by comparison to the real world by hand.
- Not measured here Publish changes to the base schedule at least one week ahead of every service change
This scorecard does not track a feed's publish history, so advance notice cannot be checked.
- Meets Produce no critical errors in the MobilityData GTFS Validator
Passes validation with no errors.
- Not measured here Publish Trip Updates, Vehicle Positions, and Alerts feeds
This scorecard checks realtime reachability and freshness overall; it does not check for all three feed types individually.
- Not measured here Update Trip Updates and Vehicle Positions at least every 20 seconds
This scorecard samples realtime freshness; it does not check this specific 20-second cadence.
- Not measured here Publish information for at least 99% of vehicles in service
This scorecard measures the share of scheduled trips represented in TripUpdates, a related but different figure than vehicle coverage.
- Not measured here Keep 100% of trip_ids consistent between Schedule and Realtime
This scorecard does not currently check trip_id consistency between the Schedule and Realtime feeds.
- Not measured here Produce no critical errors in the Center for Urban Transportation Research realtime validator
This scorecard does not run the CUTR realtime validator.
- Not measured here Publish accessible feed links on the agency or regional partner website
This scorecard does not check the agency's own website.
- Not measured here Register GTFS and GTFS-Realtime feeds with transit.land and the Mobility Database
This scorecard does not currently check aggregator registration for this section.
- Gap Designate a technical contact in feed_info.txt's feed_contact_email
feed_info.txt has no feed_contact_email or feed_contact_url.
- Gap wheelchair_boarding stated on stops and trips
States wheelchair access on 0% of stops and 0% of trips.
- Meets shapes.txt with a shape for every trip
All 5052 trips have a shape in shapes.txt.
- Gap Fare data published, or the service marked fare-free
No fare data is published.
- 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 25 / 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/sacramento-regional-transit-sacrt-2137/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.