Feed status · checked 2026-10-02
Sacramento Regional Transit (SacRT)
Based on the feed source on file; publisher ownership is not verified
Service mode Tram + Bus
down 3.3 since 2026-08-07
Cataloged 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 40 minutes ago; last changed 103 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.
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. Set feed_end_date in feed_info.txt past your next service change.Likely your export tool
Service data ended 48 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.
This one is about the feed as a whole, so there is no share of it to count.
⏱ 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
2534 of 2534 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 2,534 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
4953 of 4953 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.
Fixing this covers all 4,953 trips in the feed.
⏱ A default or per-trip field in your export.worth about +15 points in its category
Riders and need behind these fixes
- No ridership snapshot was on hand when this was built, so annual rider-trips are not known.
- California 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-09-28.
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.
- Feed evidence
- Service data ended 48 day(s) ago.
- Next action
- Re-export the feed with a calendar that reaches further out. Set feed_end_date in feed_info.txt 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
- 2534 of 2534 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
- 4953 of 4953 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. Set feed_end_date in feed_info.txt past your next service change. · Read the fix guide for scorecard_feed_expired
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.
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 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. See this feed's finding-clearance log.
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 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. 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 was 48 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 4 kinds of issue across 2864 instances (0 error, 2862 warning, 2 informational).
Service data ended 48 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
9 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.
2462 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 2534 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)
- 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)
- 137 (pink)
- 138 (pink)
- 142 (pink)
- 161 (pink)
- 175 (blue)
- 176 (blue)
- 177 (blue)
- Gold (yellow)
- 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 (no shape in feed) |
| 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 |
| 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 |
| Gold Downtown - Folsom | Tram / light rail | yellow |
| Blue Meadowview - Watt/I-80 | Tram / light rail | blue |
Over time
Overall score across the last 3 checks — down 3.3 since 2026-08-07.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-08-06 | 47.9 | first check |
| 2026-08-07 | 47.5 | down 0.4 |
| 2026-10-02 | 44.2 | down 3.3 |
What changed since your last check
- Correctness no change
- Freshness down 13.3
- Rider experience no change
What changed in this feed
Overall score fell 3.3 points since 2026-08-07.
Same feed file as 2026-08-07; the published zip did not change.
New since 2026-08-07 (1 finding)
- Error1 instance
Service data ended 48 day(s) ago.
Finding code: scorecard_feed_expired · Read the fix guide for scorecard_feed_expired · See GTFS Best Practices (opens GTFS Best Practices on an external site)
No longer reported since 2026-08-07 (1 finding)
- Service data runs out in 8 day(s). (scorecard_feed_expiring_soon)
This records the later feed state. It does not establish who made a change or why.
Subscribe to this feed’s changes (Atom) to hear about grade drops and export changes in a reader, with no sign-up.
What changed over time
On 2026-08-06 this feed started at grade F. On 2026-10-02 feed expired. On 2026-10-02 the check no longer reported: service data runs out in 8 day(s). As of 2026-10-02 it holds grade F.
A plain-language history of this feed, newest first.
- 2026-10-02 Feed expired.
Everything we checked
10 findings, ordered by severity.
Show every finding
- Error1 instance
Service data ended 48 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. Set feed_end_date in feed_info.txt 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 for scorecard_feed_expired · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning4953 instances
4953 of 4953 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 for scorecard_wheelchair_accessible_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning2860 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)
- Warning2534 instances
2534 of 2534 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
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
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 for stop_too_far_from_shape · 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 for scorecard_no_fare_data · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info2192 instances
About 2192 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 for scorecard_stop_names_all_caps · 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 for unknown_file · 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 for scorecard_no_feed_contact · 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 48 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 48 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 4953 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
Two requirements remain for this feed to earn the conformance mark. Service data expired 48 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 48 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.
Realtime reliability
The realtime feed responded on 100.0% of 102 checks in the 14 days to 2026-08-21, with 18s median lag.
Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment. The window ends at the newest observation, which is not always today: if the monitor stops, this window stops with it.
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 4953 trips have a shape in shapes.txt.
- Gap Fare data published, or the service marked fare-free
No fare data is published.
- Correctness 84 / 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 24 / 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 California portfolio: the same scorecards for every feed we track in that group, on one free page.
For programs that support several agencies
This scorecard and the board one-pager for Sacramento Regional Transit (SacRT) are free, and they stay free. If you support several agencies, as a state program, a technical-assistance center, a feed vendor, or a consultancy, you can buy the program report bundle. It puts this agency's board report in one archive with the reports for the other agencies you support, and each cover carries your program's name, logo, and accent color.
The report for Sacramento Regional Transit (SacRT) uses the same numbers as this page: grade F (44.2 out of 100) as of the check on 2026-10-02, its category scores, its top fixes, and its score at each check.
One bundle, up to 25 agencies: $149, paid once, delivered within 2 business days or refunded. Other plans, including a monthly refresh, are on the bundle page.
See a sample bundle report: a real agency's current grade, with placeholder branding.
A purchase buys no influence over grades, methodology, or which agencies are listed. The grade on this page comes from the check on 2026-10-02, scored with rubric v1.3 and MobilityData gtfs-validator 8.0.1. Based on the feed source on file; publisher ownership is not verified. Read how the grade is calculated.
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/2026-10-02.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-10-02. 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.