Feed status · checked 2026-11-21
GTrans
Based on the feed source on file; publisher ownership is not verified
Service mode Bus
down 0.4 since 2026-11-20
Cataloged in California.
The grade is not a count of validator errors. It also weighs freshness and rider information. How the grade works
Feed file
Feed URL: https://ridegtrans.com/gtfs.zip
Watch this feed for free: we email you before it expires or when its grade drops.
Top things to 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.
The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
This one is about the feed as a whole, so there is no share of it to count.
⏱ A small file for most flat-fare systems.worth about +15 points in its category
Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').Likely your export tool
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.
This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.
⏱ Often a bulk fix in your scheduling software.worth about +6 points in its category
Add feed_contact_email or feed_contact_url to feed_info.txt.Likely your export tool
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.
This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.
⏱ One field, set once in export settings.worth about +4 points in its category
Riders and need behind these fixes
- This feed carries no National Transit Database ID, so annual rider-trips are not known for it.
- 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-11-02.
These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.
Finding handoff
Move one finding to a recheck
Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.
- Finding
- Fix 01 in Top things to fix: its feed evidence and the requested change.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Finding
- Fix 02 in Top things to fix: its feed evidence and the requested change.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Finding
- Fix 03 in Top things to fix: its feed evidence and the requested change.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
How to make and check these changes
Check the result on the published feed. Read the guide, make the change in your tool, and use the next comparable run to see whether the finding is still reported. Only an action or ticket record can attribute who made the change.
Fix 01 · Read the fix guide for scorecard_no_fare_data
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. See this feed's finding-clearance log.
Fix 02 · Read the fix guide for mixed_case_recommended_field
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.
Fix 03 · Read the fix guide for missing_feed_contact_email_and_url
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 42 days.
- Published accessibility data
- Accessibility information is stated for 100% 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.
About this feed
Looking for times or routes? This page checks the data file that trip planners use. For schedules, use the agency's own website or a trip planner.
GTrans’s published feed lists 7 bus routes, 1,875 scheduled trips and 445 stops. Its service dates run from 2026-10-11 through 2027-01-02. The published file last changed on 2026-10-13.
Score by category
The MobilityData validator flagged 4 kinds of issue across 30 instances (0 error, 29 warning, 1 informational).
Service data covers the next 42 days.
100% of stops state wheelchair accessibility (0% marked accessible, 100% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
100% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
4 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (2, 2SCH, 4, 5).
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.
429 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Compton Bl & Matthisen Ave", "Western Ave & Redondo Beach Bl", "Western Ave & 154th St", 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 445 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.
- 1X (red)
- 2 (purple)
- 2SCH (purple)
- 3 (orange)
- 3SCH (orange)
- 4 (brown)
- 5 (teal)
| Route | Type | Line color |
|---|---|---|
| 1X Line 1X | Bus | red |
| 2 Line 2 | Bus | purple |
| 2SCH Line 2 School | Bus | purple |
| 3 Line 3 | Bus | orange |
| 3SCH Line 3 School | Bus | orange |
| 4 Line 4 | Bus | brown |
| 5 Line 5 | Bus | teal |
List every stop
- Compton Bl & Matthisen Ave
- Marine Ave & Cranbrook Ave
- Gardena Bl & Figueroa St
- Gardena Bl & Hoover St
- Redondo Beach Bl & Budlong Ave
- Redondo Beach Bl & Raymond Ave
- Redondo Beach Bl & Normandie Ave
- Marine Ave & Prarie Ave
- Redondo Beach Bl & Nuanu Dr
- Redondo Beach Bl & Denker Ave
- Redondo Beach Bl & Gramercy Pl
- Redondo Beach Bl & Van Ness Ave
- Compton Bl & Aranbe Ave
- Redondo Beach Bl & Wilkie Ave
- Redondo Beach Bl & Yukon Ave
- Redondo Beach Bl & Ainsworth Ave
- Redondo Beach Bl & Prarie Ave
- Marine Ave & Bodger Ave
- Redondo Beach Bl & Amie Ave
- Redondo Beach Bl & Hawthorne Bl
- Pacific Coast Hwy & Belle Porte Ave
- Pacific Coast Hwy & President Ave
- Pacific Coast Hwy & Western Ave
- Marine Ave & Doty Ave
- Western Ave & 255th St
- Western Ave & 253rd St
- Western Ave & Lomita Bl
- Marine Ave & Yukon Ave
- Western Ave & 247th St
- Western Ave & 242nd Pl
- Western Ave & 238th St
- Western Ave & 236th St
- Western Ave & Sepulveda Bl
- Western Ave & 228th St
- Marine Ave & Prarie Ave
- Western Ave & Plaza del Amo
- Western Ave & 223rd St
- Western Ave & 220th St
- Marine Ave & Lemoli Ave
- Western Ave & 213th St
- Western Ave & Torrance Bl
- Western Ave & 208th St
- Western Ave & 205th St
- Western Ave & Del Amo Bl
- Western Ave & Western Way
- Marine Ave & Freeman Ave
- Western Ave & Toyota Way
- Western Ave & 190th St
- Western Ave & 186th St
- Western Ave & 182nd St
- Western Ave & 178th St
- Western Ave & Artesia Bl
- Western Ave & 169th St
- Western Ave & 166th St
- Western Ave & Marine Ave
- Western Ave & 146th St
- Marine Ave & Hawthorne Bl
- Western Ave & 139th St
- Western Ave & 135th St
- Western Ave & 132nd St
- Marine Ave & Dublin Ave
- Western Ave & El Segundo Bl
- Western Ave & 120th St
- Imperial Hwy & Denker Ave
- Imperial Hwy & Normandie Ave
- Imperial Hwy & Budlong Ave
- Imperial Hwy & Vermont Ave
- Marine Ave & Firmona Av
- Vermont Ave & Green Line Station
- Vermont Ave & 124th St
- Vermont Ave & El Segundo Bl
- Marine Ave & Van Ness Ave
- Vermont Ave & 132nd St
- Vermont Ave & 135th St
- Vermont Ave & 140th St
- Vermont Ave & 168th St
- Vermont Ave & Artesia Bl
- Normandie Ave & 186th St
- Wilmington Ave & 118th St
- Normandie Ave & 190th St
- Normandie Ave & Knox St
- Normandie Ave & Francisco St
- Marine Ave & Gramercy Pl
- Normandie Ave & 204th St
- Normandie Ave & Torrance Bl
- Normandie Ave & 212th St
- Normandie Ave & Levinson St
- Normandie Ave & 220th St
- Normandie Ave & 223rd St
- 120th St & Compton Ave
- Normandie Ave & 228th St
- Normandie Ave & Sepulveda Bl
- Normandie Ave & Oakhealth Dr
- Marine Ave & Western Ave
- Normandie Ave & Pasatiempo Ln
- Normandie Ave & 245th St
- Normandie Ave & Lomita Bl
- Normandie Ave & 253rd St
- Normandie Ave & 255th St
- Normandie Ave & 253rd St
- Compton Bl & Orleander Ave
- Normandie Ave & Lomita Bl
- Normandie Ave & 245th St
- Alondra Bl & Central Ave
- Western Ave & 154th Pl
- Normandie Ave & Pasatiempo Ln
- Normandie Ave & Oakhealth Dr
- Normandie Ave & Sepulveda Bl
- Normandie Ave & 228th St
- Normandie Ave & 225th St
- Normandie Ave & 223rd St
- Western Ave & Redondo Beach Bl
- Compton Ave & El Segundo Bl
- Normandie Ave & 220th St
- Normandie Ave & Carson St
- Normandie Ave & Levinson St
- Normandie Ave & Torrance Bl
- Western Ave & Redondo Beach Bl
- Normandie Ave & 204th St
- Normandie Ave & Francisco St
- Normandie Ave & Knox St
- Normandie Ave & 190th St
- Normandie Ave & 186th St
- El Segundo Bl & Slater Ave
- Vermont Ave & Artesia Bl
- Vermont Ave & 170th St
- Vermont Ave & 168th St
- Vermont Ave & Carnelian Pl
- Western Ave & 162nd St
- Vermont Ave & 138th St
- Vermont Ave & 135th St
- Vermont Ave & 133rd St
- Vermont Ave & El Segundo Bl
- Vermont Ave & 125th St
- El Segundo Bl & Central Ave
- Imperial Hwy & Budlong Ave
- Imperial Hwy & Normandie Ave
- Imperial Hwy & Denker Ave
- Imperial Hwy & Western Ave
- Western Ave & Gardena Bl
- Western Ave & College Dr
- Western Ave & 120th St
- El Segundo Bl & Aviation Bl
- El Segundo Bl & Isis Ave
- El Segundo Bl & Shoup Ave
- El Segundo Bl & Keene Ave
- El Segundo Bl & Inglewood Ave
- El Segundo Bl & Ramona Ave
- El Segundo Bl & Hawthorne Bl
- 166th St & Western Ave
- El Segundo Bl & Birch Ave
- El Segundo Bl & Oxford Ave
- El Segundo Bl & Prarie Ave
- El Segundo Bl & Cordary Ave
- El Segundo Bl & Yukon Ave
- El Segundo Bl & Cerise Ave
- El Segundo Bl & McKinley Ave
- El Segundo Bl & Chadron Ave
- El Segundo Bl & Crenshaw Bl
- El Segundo Bl & Wilkie Ave
- 166th St & Denker Ave
- El Segundo Bl & Van Ness Ave
- El Segundo Bl & Western Ave
- El Segundo Bl & Harvard Bl
- El Segundo Bl & Halldale Ave
- El Segundo Bl & Normandie Ave
- El Segundo Bl & Budlong Ave
- El Segundo Bl & Avalon Bl
- El Segundo Bl & Hoover St
- El Segundo Bl & Broadway
- El Segundo Bl & Main St
- 166th St & Brighton Ave
- El Segundo Bl & San Pedro St
- El Segundo Bl & McKinley Ave
- El Segundo Bl & Keene Ave
- El Segundo Bl & Central Ave
- El Segundo Bl & Slater Ave
- Compton Ave & El Segundo Bl
- El Segundo Bl & San Pedro St
- Compton Ave & 124th St
- 120th St & Wilmington Ave
- Gardena Bl & Raymond Ave
- Van Ness Ave & 154th St
- Van Ness Ave & 147th St
- Van Ness Ave & Rosecrans Ave
- Van Ness Ave & 139th St
- Van Ness Ave & 135th St
- Gardena Bl & Budlong Ave
- 135th St & Wilton Pl
- El Segundo Bl & Main St
- 135th St & Halldale Ave
- 135th St & Normandie Ave
- Normandie Ave & 139th St
- Normandie Ave & Rosecrans Ave
- Normandie Ave & 145th Pl
- Normandie Ave & 149th St
- Normandie Ave & Marine Ave
- Normandie Ave & Redondo Beach Bl
- Normandie Ave & Magnolia Ave
- El Segundo Bl & Broadway
- Normandie Ave & 160th St
- Normandie Ave & 162nd St
- Normandie Ave & 166th St
- Normandie Ave & 170th St
- Normandie Ave & Artesia Bl
- Normandie Ave & 178th St
- Normandie Ave & 182nd St
- Alondra Bl & Nestor Ave
- Kingsdale Ave & 182nd St
- Compton Bl & Acacia Ave
- Hawthorne Bl & 182nd St
- Hawthorne Bl & 179th St
- Hawthorne Bl & Artesia Bl
- Redondo Beach Bl & Freeman Ave
- Redondo Beach Bl & Prarie Ave
- Redondo Beach Bl & Ainsworth Ave
- Redondo Beach Bl & Yukon Ave
- Redondo Beach Bl & Crenshaw Bl
- Redondo Beach Bl & Arcturus Ave
- Vermont Ave & 163rd St
- Western Ave & 154th St
- El Segundo Bl & Figueroa St
- Redondo Beach Bl & Van Ness Ave
- Redondo Beach Bl & Denker Ave
- Redondo Beach Bl & Raymond Ave
- Redondo Beach Bl & Budlong Ave
- Redondo Beach Bl & Catalina Ave
- Redondo Beach Bl & Vermont Ave
- Gardena Bl & Hoover St
- Gardena Bl & Figueroa St
- Vermont Ave & 161st St
- El Segundo Bl & Hoover St
- Gardena Bl & Broadway
- Main St & Alondra Bl
- Alondra Bl & Maple Ave
- Alondra Bl & Haskins Ln
- Alondra Bl & Clymar Ave
- Alondra Bl & Aprilla Ave
- Western Ave & 122nd St
- Western Ave & 125th St
- Western Ave & El Segundo Bl
- Vermont Ave & Magnolia Ave
- El Segundo Bl & Vermont Ave
- Western Ave & 132nd St
- Western Ave & 135th St
- Western Ave & 139th St
- Western Ave & Rosecrans Ave
- Western Ave & 146th St
- Western Ave & Marine Ave
- Western Ave & 166th St
- and 195 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 13 checks — down 0.4 since 2026-11-20.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-11-09 | 84.1 | first check |
| 2026-11-10 | 83.7 | down 0.4 |
| 2026-11-11 | 83.3 | down 0.4 |
| 2026-11-12 | 82.9 | down 0.4 |
| 2026-11-13 | 82.5 | down 0.4 |
| 2026-11-14 | 82.0 | down 0.5 |
| 2026-11-15 | 81.6 | down 0.4 |
| 2026-11-16 | 81.2 | down 0.4 |
| 2026-11-17 | 80.8 | down 0.4 |
| 2026-11-18 | 80.4 | down 0.4 |
| 2026-11-19 | 80.0 | down 0.4 |
| 2026-11-20 | 79.5 | down 0.5 |
| 2026-11-21 | 79.1 | down 0.4 |
What changed since your last check
- Correctness no change
- Freshness down 1.7
- Rider experience no change
Feed history
Every check on record for this feed, grouped by the published file, newest first. A new file means the published zip changed. Grades from earlier rubric versions are shown with their rubric and are not comparable with today’s grade or the trend above.
| Checked | Published file | Service dates through | Grade at the time |
|---|---|---|---|
| 2026-11-09 to 2026-11-21 (13 checks) | f9e8c3ab3828 | 2027-01-02 | Current rubric: see the trend above |
| 2026-10-13 to 2026-11-06 (25 checks) | f9e8c3ab3828 | 2027-01-02 | B, 85.4 under rubric 1.4, an earlier scoring contract; not comparable with today’s grade |
| 2026-10-02 to 2026-10-12 (11 checks) | 9f3d2b99e008 | 2026-10-10 | C, 70 under rubric 1.4, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-25 to 2026-10-01 (65 checks) | 9f3d2b99e008 | 2026-10-10 | C, 72.3 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-23 to 2026-07-24 (2 checks) | 9f3d2b99e008 | 2026-10-10 | B, 87.5 under rubric 1.2, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-14 to 2026-07-20 (7 checks) | d52578a9a8eb | 2026-07-18 | F, 59.2 under rubric 1.2, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-08 to 2026-07-13 (6 checks) | d52578a9a8eb | 2026-07-18 | D, 64.8 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-02 to 2026-07-07 (6 checks) | c288957eb392 | 2026-07-18 | D, 62.6 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade |
| 2026-06-29 to 2026-07-01 (3 checks) | d52578a9a8eb | 2026-07-18 | D, 69.8 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade |
| 2026-06-19 to 2026-06-28 (10 checks) | 97ecf124ce5c | 2026-07-18 | D, 68.2 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade |
What changed over time
On 2026-11-09 this feed started at grade B. On 2026-11-20 the grade moved from B to C. As of 2026-11-21 it holds grade C.
A plain-language history of this feed, newest first.
- 2026-11-20 Grade went B to C.
Everything we checked
6 findings, ordered by severity.
Show every finding
- Warning27 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)
- 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 route colors don't contrast with their text color.
Route badges get hard to read, most of all for riders with low vision.
Fix: Pick a darker/lighter route_text_color for the flagged routes. (One field per route.)
Finding code: route_color_contrast · Read the fix guide for route_color_contrast · 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)
- Info1 instance
The feed has a stretch of two weeks or more with no service running.
A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.
Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)
Finding code: big_gap_in_service · Read the fix guide for big_gap_in_service · 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).
App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.
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)
How we measured this
Checked for changes 18 hours ago; last changed 40 days ago.
Measured 3 of 4 score categories from the feed URL on file (publisher not verified).
How we measured this
Confidence in this measurement: medium.
- Realtime quality was not measured this run. It does not count against the grade.
- The feed was downloaded from the configured feed URL. Publisher ownership of that URL is not verified.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
A data-quality and completeness lens to help an agency improve its GTFS feed. Not an official compliance determination from any transit program. New to this? How to read your scorecard. Interactive view of this scorecard. Rubric v1.5, validator 8.0.1.
NTD GTFS readiness Ready
Published at a public URL, valid, current, and identified with agency_id: the four feed checks for RY2026 all hold here. Only your own D-10 and P-50 filings make that official; this is a heads-up, not a determination.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Ready
- Service data covers the next 42 days.
- agency_id provided Ready
- agency.txt provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk each value on the P-50 form.
- agency_id equals your NTD ID (optional) Not checked yet
- This feed provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk it on the P-50 form. The value does not need to equal the five-digit NTD ID; we do not have that ID on file, so the optional equality comparison is not checked yet.
- shapes.txt covers your trips Ready
- All 1875 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 Awarded
This feed earns the conformance mark: valid, current, and stating wheelchair access on nearly every stop and trip.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 42 days.
- Accessible Met
- States wheelchair access on 100% of stops and 100% of trips.
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 200 checks in the 25 days to 2026-10-20, with 15s 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.
Clears the Google and Apple Maps four-week coverage bar. This feed has 41 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 (4 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.
- Meets wheelchair_boarding stated on stops and trips
States wheelchair access on 100% of stops and 100% of trips.
- Meets shapes.txt with a shape for every trip
All 1875 trips have a shape in shapes.txt.
- Gap Fare data published, or the service marked fare-free
No fare data is published.
- Correctness 86 / 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 70 / 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 78 / 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.
Similar feeds in California
Other scorecards in California, starting with the same kind of service at a similar size. Listed for comparison, not ranked.
Cite this record
This page updates on every check. The record below does not: it is the dated file this grade came from, published at https://gtfsscorecard.org/data/artifacts/gtrans-2270/2026-11-21.json and never overwritten, pinning the grade, category scores, rubric version, validator version, reader archive profile, and the scored feed's sha256 as they stood on 2026-11-21. Use it in a board packet, a regulatory filing, or a research citation instead of linking the live page, whose content will differ on your next visit.
Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.