Feed status · checked 2026-10-02
San Mateo County Transit District (samTrans)
Based on the feed source on file; publisher ownership is not verified
Service mode Bus
down 7.1 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 41 days ago; last changed 56 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
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
1852 of 1852 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 1,852 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
4224 of 4224 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
Fixing this covers all 4,224 trips in the feed.
⏱ A default or per-trip field in your export.worth about +15 points in its category
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.
43 of 4224 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.
Fixing this covers 43 of 4,224 trips, about 1% of them.
⏱ Usually one value per route pattern in your scheduling source.
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
- 1852 of 1852 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
- 4224 of 4224 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
- Feed evidence
- 43 of 4224 trips lack rider-facing destination or direction text.
- Next action
- 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.
- 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.
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. 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 for scorecard_wheelchair_accessible_unknown
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
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. · Read the fix guide for scorecard_missing_headsigns
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Rider view: what this feed publishes
A quick read of rider-facing information in this feed.
- Schedule visibility
- The feed's last published service date is in 43 days.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- Fare information is published using GTFS Fares v1.
- 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.
Score by category
The MobilityData validator flagged 3 kinds of issue across 4232 instances (0 error, 0 warning, 4232 informational).
Service data covers the next 43 days.
0% of stops state wheelchair accessibility (0% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
1 accessibility depth signal
1764 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Terra Nova Blvd & Alicante Dr", "Bradford Way & Fairway Dr", "Capistrano Dr & Linda Mar Blvd", 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.
Fares are applied to trips.
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 1852 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.
- 10 (green)
- 110 (green)
- 112 (green)
- 117 (green)
- 12 (green)
- 120 (green)
- 121 (green)
- 122 (green)
- 130 (green)
- 138 (green)
- 14 (green)
- 141 (green)
- 142 (green)
- 15 (green)
- 18 (green)
- 19 (green)
- 24 (green)
- 25 (green)
- 250 (green)
- 251 (green)
- 260 (green)
- 270 (green)
- 276 (green)
- 278 (green)
- 28 (green)
- 280 (green)
- 281 (green)
- 29 (green)
- 292 (green)
- 294 (green)
- 295 (green)
- 296 (green)
- 296O (green)
- 30 (green)
- 35 (green)
- 37 (green)
- 397 (green)
- 40 (green)
- 41 (green)
- 42 (green)
- 46 (green)
- 49 (green)
- 50 (green)
- 51 (green)
- 53 (green)
- 53P (green)
- 54 (green)
- 56 (green)
- 57 (green)
- 58 (green)
- 59 (green)
- 60 (green)
- 61 (green)
- 62 (green)
- 67 (green)
- 68 (green)
- 713 (green)
- 72 (green)
- 73 (green)
- 78 (green)
- 79 (green)
- 81 (green)
- 82 (green)
- 83 (green)
- 85 (green)
- 86 (green)
- 87 (green)
- 88 (green)
- CSM (green)
- ECR (green)
- ECRO (green)
- EPX (green)
- FCX (green)
- PCX (green)
- SKY (green)
| Route | Type | Line color |
|---|---|---|
| 10 Daly City BART - Terra Nova HS | Bus | green |
| 110 Daly City BART - Linda Mar Park & Ride | Bus | green |
| 112 Sharp Park - Colma BART | Bus | green |
| 117 Linda Mar Park & Ride - Moonridge Apts | Bus | green |
| 12 Pacifica School - Fairmont Shopping Center | Bus | green |
| 120 Colma BART - Brunswick/Templeton | Bus | green |
| 121 Pope/Bellevue - Skyline College | Bus | green |
| 122 South SF BART - Stonestown/SF State | Bus | green |
| 130 Daly City BART - Airport & Linden/Oyster Point | Bus | green |
| 138 Safe Harbor Shelter | Bus | green |
| 14 Linda Mar Circulator | Bus | green |
| 141 Airport/Linden - Skyline College | Bus | green |
| 142 SFO - Shelter Creek | Bus | green |
| 15 HMBHS - Moonridge Apts | Bus | green |
| 18 Main/7th - HMBHS | Bus | green |
| 19 Lacy School - Linda Mar Park & Ride | Bus | green |
| 24 Brisbane - Shasta High | Bus | green |
| 25 Los Olivos/Santa Barbara - Ben Franklin School | Bus | green |
| 250 Downtown San Mateo - College of San Mateo | Bus | green |
| 251 Foster City - Hillsdale Mall | Bus | green |
| 260 San Carlos Caltrain - Carlmont Village | Bus | green |
| 270 Redwood City Caltrain - Florence/17th loop | Bus | green |
| 276 Redwood City Transit Ctr - Bohannon/Campbell | Bus | green |
| 278 Redwood City Caltrain - Canada College | Bus | green |
| 28 Serramonte Center - South City High | Bus | green |
| 280 Purdue/Fordham - Palo Alto Transit Ctr | Bus | green |
| 281 Belle Haven Community Campus - Stanford | Bus | green |
| 29 Lipman School - Templeton/Brunswick | Bus | green |
| 292 San Francisco - SFO - Hillsdale Mall | Bus | green |
| 294 Hillsdale - Half Moon Bay | Bus | green |
| 295 Hillsdale Mall - Redwood City Transit Center | Bus | green |
| 296 Redwood City Transit Center - Bayshore/Donohoe | Bus | green |
| 296O Redwood City TC- Palo Alto TC | Bus | green |
| 30 Daly City BART - Price/East Market | Bus | green |
| 35 El Camino High - Warwick/Christen | Bus | green |
| 37 Hillside/Grove - Alta Loma School | Bus | green |
| 397 San Francisco - Palo Alto Transit Ctr | Bus | green |
| 40 IBL Middle School - San Bruno BART | Bus | green |
| 41 Parkside IL - San Bruno BART | Bus | green |
| 42 Pacifica - Parkside IL | Bus | green |
| 46 Burlingame School - Carolan (Burlingame Caltrain) | Bus | green |
| 49 Brisbane - Terra Nova High | Bus | green |
| 50 Bay STEM Academy - Hillsdale Shopping Center | Bus | green |
| 51 Foster City - Hillsdale HS | Bus | green |
| 53 Peninsula/Humboldt - Borel MS | Bus | green |
| 53P Peninsula/Humboldt - Borel MS via Poplar | Bus | green |
| 54 Bowditch School - Hillsdale/Norfolk | Bus | green |
| 56 Aragon HS - Polhemus/Paul Scannell | Bus | green |
| 57 Edgewater/Beach Park - Hillsdale High | Bus | green |
| 58 Borel School - Polhemus/Paul Scannell | Bus | green |
| 59 Hillsdale/Norfolk - Aragon High | Bus | green |
| 60 Ralston School - Bridge/Bowsprit via Chula Vista | Bus | green |
| 61 San Carlos Caltrain - Alameda/Ralston | Bus | green |
| 62 Hillsdale - Alameda & Ralston | Bus | green |
| 67 Bridge/Bowsprit - Ralston School | Bus | green |
| 68 Hiller/Wessex - Ralston School | Bus | green |
| 713 SF Transit Center - San Francisco International | Bus | green |
| 72 Marlborough/Dumbarton - Selby Lane School | Bus | green |
| 73 "G" & Industrial - Clifford School | Bus | green |
| 78 Emerald Hills - Woodside HS | Bus | green |
| 79 Kennedy MS - Florence/17th | Bus | green |
| 81 MAHS - East Palo Alto | Bus | green |
| 82 Bay/Marsh - Hillview School | Bus | green |
| 83 Hillview School - Bay/Marsh | Bus | green |
| 85 Ormondale School - La Honda/Grandview | Bus | green |
| 86 Sharon Heights - Menlo-Atherton High School | Bus | green |
| 87 Woodside High - Portola Valley | Bus | green |
| 88 Bay/Marsh - Encinal School | Bus | green |
| CSM College of San Mateo - Downtown San Mateo | Bus | green |
| ECR Daly City BART - Palo Alto Transit Ctr | Bus | green |
| ECRO Daly City - SFO | Bus | green |
| EPX East Palo Alto - San Bruno BART and San Francisco | Bus | green |
| FCX Foster City - San Francisco | Bus | green |
| PCX Linda Mar Park & Ride - Daly City BART | Bus | green |
| SKY Daly City BART - Skyline College | Bus | green |
Over time
Overall score across the last 3 checks — down 7.1 since 2026-08-07.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-08-06 | 86.5 | first check |
| 2026-08-07 | 86.5 | no change |
| 2026-10-02 | 79.4 | down 7.1 |
What changed since your last check
- Correctness no change
- Freshness down 28.3
- Rider experience no change
What changed in this feed
Grade dropped from B to C since 2026-08-07.
Same feed file as 2026-08-07; the published zip did not change.
What changed inside the export
- Route 110 (Daly City BART - Linda Mar Park & Ride), 112 (Sharp Park - Colma BART), 117 (Linda Mar Park & Ride - Moonridge Apts), 120 (Colma BART - Brunswick/Templeton), 121 (Pope/Bellevue - Skyline College), and 27 more are no longer in the export.
- Route 10 (Daly City BART - Terra Nova HS), 110 (Daly City BART - Linda Mar Park & Ride), 112 (Sharp Park - Colma BART), 117 (Linda Mar Park & Ride - Moonridge Apts), 12 (Pacifica School - Fairmont Shopping Center), and 70 more are new in this export.
- 13 stops left the export.
- 576 new stops appeared.
- Service now runs through 2026-11-14 (was 2026-08-01).
Read from the feed file itself, compared with the previous export. A service change is normal; this is a heads-up so nothing disappears silently.
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 B. On 2026-10-02 the grade moved from B to C. As of 2026-10-02 it holds grade C.
A plain-language history of this feed, newest first.
- 2026-10-02 Grade went B to C, freshness fell 28 points.
Everything we checked
6 findings, ordered by severity.
Show every finding
- Warning4224 instances
4224 of 4224 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible stops, riders need to know the bus itself can take them.
Fix: Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. (A default or per-trip field in your export.)
Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide for scorecard_wheelchair_accessible_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning1852 instances
1852 of 1852 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)
- Warning43 instances
43 of 4224 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 for scorecard_missing_headsigns · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info4224 instances
Trip with shape dist traveled but no shape distances (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'trip_with_shape_dist_traveled_but_no_shape_distances' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: trip_with_shape_dist_traveled_but_no_shape_distances · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info7 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
Some files contain columns that are not part of the GTFS spec.
Harmless to riders, but apps ignore these columns and they can hide typos in real column names.
Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)
Finding code: unknown_column · Read the fix guide for unknown_column · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
NTD GTFS readiness Ready
Published at a public URL, valid, current, and identified with agency_id: the four feed checks for RY2026 all hold here. Only your own D-10 and P-50 filings make that official; this is a heads-up, not a determination.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Ready
- Service data covers the next 43 days.
- agency_id provided Ready
- agency.txt provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk each value on the P-50 form.
- agency_id equals your NTD ID (optional) Different (allowed)
- Your feed's agency_id is samtrans-ca-us; your National Transit Database ID is 90009. 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 samtrans-ca-us to NTD ID 90009, and keep the feed value stable. Do not change it solely to make the two values equal.
- shapes.txt covers your trips Ready
- All 4224 trips have a shape in shapes.txt.
In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed, provide a stable agency_id for each represented reporter, and confirm the feed and P-50 crosswalk each year. This box is a heads-up; your filings are the official check.
A readiness signal mapping this feed to the FTA National Transit Database GTFS requirement (Report Year 2023 onward: a public, valid, current feed, certified annually on the D-10). For RY2026, each represented reporter needs a stable agency_id, unique within the feed and crosswalked to its five-digit NTD ID on P-50; the values do not need to be equal. FTA also requires shapes.txt in the published GTFS: Full Reporters from Report Year 2025, and Reduced, Rural, and Tribal Reporters from Report Year 2026. Not an official determination; your certification is the official check.
Conformance mark Not yet
One requirement remains for this feed to earn the conformance mark. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 43 days.
- Accessible Not yet
- States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.
A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.
Clears the Google and Apple Maps four-week coverage bar. This feed has 43 days of service ahead, clearing the four-week (28-day) window Maps asks for. No validator errors either, so riders keep seeing this agency in their trip planners; warnings lower the grade here but do not remove a feed from Maps.
How this agency maps to the standards
The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance, FTA National Transit Database GTFS requirement. Read the full standards crosswalk.
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 (5 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.
- Meets Designate a technical contact in feed_info.txt's feed_contact_email
feed_info.txt states a technical contact.
- 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 4224 trips have a shape in shapes.txt.
- Meets Fare data published, or the service marked fare-free
Fare data is published.
- Correctness 98 / 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 72 / 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 60 / 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 San Mateo County Transit District (samTrans) 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 San Mateo County Transit District (samTrans) uses the same numbers as this page: grade C (79.4 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/san-mateo-county-transit-district-samtrans/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.