Feed status · checked 2026-08-01
Yolobus (Yolo County Transportation District)
Based on the feed this agency publishes
Service mode Bus
down 0.4 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 65 minutes ago; last changed 41 days ago.
Measured 4 of 4 score categories from the agency's own feed.
How we measured this
Confidence in this measurement: high.
- All four score categories were measured this run.
- Realtime was sampled in one bounded window of 9 snapshots.
- 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
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
721 of 721 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
⏱ A default or per-trip field in your export.worth about +15 points in its category
Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.
The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
⏱ A small file for most flat-fare systems.worth about +15 points in its category
Add feed_info.txt with feed_start_date and feed_end_date to your export.Likely your export tool
feed_info.txt is missing its start/end dates (the file itself is absent) Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.
⏱ Two fields, set once in export settings.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
- 721 of 721 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
- The feed contains no fare information.
- Next action
- 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.
- 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
- feed_info.txt is missing its start/end dates (the file itself is absent)
- Next action
- Add feed_info.txt with feed_start_date and feed_end_date to your export.
- 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_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. See this feed's finding-clearance log.
Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. See this feed's finding-clearance log.
Add feed_info.txt with feed_start_date and feed_end_date to your export. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. See this feed's finding-clearance log.
Rider view: what this feed publishes
A quick read of rider-facing information in this feed.
- Schedule visibility
- The feed's last published service date is in 37 days.
- Published accessibility data
- Accessibility information is stated for 99.5% 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
- Live-arrival data covered 100% of scheduled trips in the sampled window.
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 2 kinds of issue across 16 instances (0 error, 16 warning, 0 informational).
Service data covers the next 37 days.
99% of stops state wheelchair accessibility (99% marked accessible, 0% 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 (100% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
5 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (240, 211, 41, 138, 40).
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.
83 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Ikea Ct. at Reed", "Ikea Ct. at IKEA NB", "6th St. at Andrew SB", 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.
Sampled 9 times: 3 of 3 configured feeds healthy; 100.0% of scheduled trips had live predictions; 100.0% of vehicles on their route; predictions ran a median of 321s behind schedule.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 374 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.
- 138 (red)
- 211 (teal)
- 212 (orange)
- 215 (orange)
- 230 (teal)
- 240 (purple)
- 37 (teal)
- 40 (purple)
- 41 (purple)
- 42A (teal)
- 42B (green)
- 43 (red)
- 43R (teal)
- 44 (red)
- 45 (red)
| Route | Type | Line color |
|---|---|---|
| 138 Causeway Connection | Bus | red |
| 211 ROUTE 211 | Bus | teal |
| 212 ROUTE 212 | Bus | orange |
| 215 ROUTE 215 | Bus | orange |
| 230 ROUTE 230 | Bus | teal |
| 240 ROUTE 240 | Bus | purple |
| 37 ROUTE 37 | Bus | teal |
| 40 ROUTE 40 | Bus | purple |
| 41 ROUTE 41 | Bus | purple |
| 42A ROUTE 42A | Bus | teal |
| 42B ROUTE 42B | Bus | green |
| 43 ROUTE 43 | Bus | red |
| 43R ROUTE 43-R | Bus | teal |
| 44 ROUTE 44 | Bus | red |
| 45 ROUTE 45 | Bus | red |
List every stop
- Y Street & 45th
- Mondavi Center
- Silo at UC Davis
- Stockton Blvd & Colonial Way (NB)
- 5th St at G St.
- 5th St at I St.
- 5th St & Pelz Bike Path (WB)
- 5th St & Windmere Apts. (EB)
- 5th St & Cantrill/Greystone (WB)
- 5th St & Cantrill/Police Station (EB)
- 5th St & Post Office / Pole Line Rd (WB)
- 5th St & Post Office / Pole Line (EB)
- 5th St & Pole Line Rd/D.M.V (EB)
- 5th St & Pole Line Rd/D.M.V (WB)
- 5th St & Spafford St (EB)
- 5th St & Spafford (WB)
- 5th St. at D St. EB
- Cowell at Sunrise WB
- UC Davis Memorial Union
- UC Davis Health Sciences SB
- Ashley at W. Lincoln SB
- Ashley at W. Lincoln NB
- W. Beamer at Mariposa WB
- W. Beamer at Mariposa EB
- E. Beamer at Matmor WB
- E. Beamer at Matmor EB
- Beamer at 5th WB
- Beamer at 5th EB
- W. Beamer at West WB
- W. Beamer at West EB
- Cottonwood at W Beamer SB
- Cottonwood at W Beamer NB
- Cottonwood at Buckeye SB
- Cottonwood at Buckeye NB
- Cottonwood at Riverside SB
- Cottonwood at Riverside NB
- Cottonwood at W. Cross SB
- Cottonwood at W. Cross NB
- Cottonwood at W. Gibson SB
- Cottonwood at W. Gibson NB
- Cottonwood at W. Lincoln SB
- Cottonwood at W. Lincoln NB
- Cottonwood at W. Main SB
- Cottonwood at W. Main NB
- Cottonwood at W. Southwood SB
- Cottonwood at W. Southwood NB
- Court at 2nd WB
- Court at 2nd EB
- Court at Cleveland WB
- Court at Cleveland EB
- Court at College WB
- Court at College EB
- Court at Walnut WB
- Court at Walnut EB
- Farnham at Maxwell NB
- Farnham at Eaton
- Farnham at Howard NB
- W. Gibson at Amherst WB
- W. Gibson at Amherst EB
- Gibson at College EB
- Gibson at College WB
- Gibson at Coloma
- Gibson at Coloma
- W. Gibson at Midway WB
- W. Gibson at Midway EB
- Gibson at Spruce
- Gibson at Spruce
- E. Gibson at Washington WB
- E. Gibson at Washington EB
- W. Gibson at West WB
- Gibson at West
- E. Gum at East WB
- E. Gum at Matmor WB
- E. Gum at Wallace WB
- Industrial at E Main NB
- Industrial at E. Main SB
- W. Lincoln at Ashley WB
- Main at 5th WB
- Main at 5th EB
- Main at Cleveland WB
- Main at Cleveland EB
- W. Main at Community WB
- W. Main at Community EB
- E. Main at East
- E. Main at Industrial WB
- E. Main at Matmor
- Matmor at Cannery NB
- Matmor at Cannery SB
- Matmor at Crystal Springs
- Matmor at Oak NB
- Matmor at E. Main SB
- Matmor at E. Main NB
- Matmor at E. Gibson NB
- Matmor at E. Gibson SB
- Matmor at Gum SB
- Matmor at Gum NB
- Ogden at Branigan
- Pioneer at E. Gum NB
- West at Clover SB
- West at Clover NB
- West at North NB
- West at North SB
- E. Gibson at Pioneer EB
- 1st St. at D St. WB
- 1st St. at C St. EB
- 5th St. at D St. WB
- Alhambra at 5th St. EB
- Alhambra at Atlantis
- Alhambra at Arroyo
- Alhambra at Carcia
- Alhambra at Mace EB
- Alhambra at Covell
- Alhambra at 5th St. WB
- Alhambra at Loyola SB
- Alhambra at San Miguel
- Anderson at Amherst SB
- Anderson at Amherst NB
- Anderson at Hanover NB
- Anderson at Hanover SB
- Anderson at Russell SB
- Anderson at Russell NB
- Anderson at Sunset SB
- Anderson at Sunset NB
- Anderson at Villanova SB
- Anderson at Villanova NB
- Arlington at Lake WB
- Arlington at Lake EB
- Arlington at Shasta EB
- Arlington at Shasta WB
- Arthur at Alameda SB
- B at 4th NB
- B at 4th SB
- Chiles at Mace
- Chiles at Mace
- E. Covell at J EB
- E. Covell at J WB
- E. Covell at Poleline EB
- W. Covell at Sycamore WB
- W. Covell at Sycamore EB
- W. Covell at Shasta WB
- Cowell at Drummond EB
- Cowell at El Cemonte WB
- Cowell at El Cemonte EB
- Cowell at La Vida WB
- Cowell at La Vida EB
- Drummond at Lillard NB
- Drummond at Lillard SB
- El Cemonte at Glide NB
- Ensenada at Chiles
- F St. at 5th St.
- F St. at 6th St. SB
- F St. at Covell NB
- F St. at Covell SB
- Lake at W. Covell NB
- Lake at W. Covell SB
- Lillard at Cowell EB
- Loyola at Whittier Dr
- Loyola at Regis West
- Mace at 2nd St. SB
- Mace at Chiles
- Monarch at Campbell SB
- Monarch at Covell NB
- Poleline at Covell
- Russell at A St.WB
- Russell at A St. EB
- Tulip at Blackburn SB
- Tulip at Blackburn
- Tulip at Cascade NB
- Alhambra at Loyola NB
- Loyola at Tulip
- Lillard at Farragut WB
- W. Covell at Shasta EB
- 5th St. at C St.
- 6th St. at Andrew SB
- Anna at Bryte WB
- Anna at Bryte EB
- Bryte at Lisbon
- Golden Gate at Tortola
- Harbor at W. Capitol SB
- Harbor at Duluth SB
- Harbor at Duluth NB
- Hobson at Water
- Jefferson at Gateway
- Jefferson at Michigan
- Jefferson at Michigan NB
- Jefferson at Triangle Court SB
- Lisbon at Bryte
- Lisbon at Water
- Park at 17th NB
- Park at Stone NB
- Reed at I-80 WB
- Reed at Ikea EB
- Reed at Stillwater
- Solano at Sacramento NB
- Riverside at Cummins Co.
- Water at Lisbon
- Water at Hobson SB
- W. Capitol at Cedar WB
- W. Capitol at Enterprise WB
- W. Capitol at Enterprise EB
- W. Capitol at Glide WB
- W. Capitol at Glide EB
- W. Capitol at Harbor WB
- W. Capitol at Harbor EB
- W. Capitol at Jefferson WB
- W. Capitol at Jefferson EB
- W. Capitol at Pecan WB
- W. Capitol at Pine WB
- W. Capitol at Pine EB
- W. Capitol at Poplar WB
- W. Capitol at Poplar EB
- W. Capitol at Sycamore EB
- W. Capitol at Walnut EB
- W. Lincoln at Rd 98 EB
- W. Court at Cottonwood EB
- Ashley at W. Court
- 3rd St. at Clover NB
- 3rd St. at Clover SB
- 3rd St. at Beamer SB
- 3rd St. at Beamer NB
- Woodland Community College
- East at Gum
- W. Lincoln at Rd 98 WB
- County Fair Mall
- Pioneer at Spring Lake NB
- E. Main at Wal-Mart
- Jefferson at Lake Washington NB
- Jefferson at Lake Washington SB
- Marshall at Rivermont
- Harbor at W. Capitol NB
- W. Capitol at Interstate EB
- W. Capitol at Interstate Co. WB
- W. Capitol at Roadway EB
- W. Capitol at Roadway WB
- W. Capitol at Northport EB
- W. Capitol at Northport WB
- Solano at Sacramento SB
- Stillwater at Citi Group
- Stillwater at Reed
- Riverside at State Library WB
- Sacramento at Todhunter
- W. Capitol at Westacre EB
- W. Capitol at Westacre WB
- Railroad at Main (Madison)
- Yolo at Grafton (Esparto) NB
- Yolo at Grafton (Esparto) SB
- Jefferson at Higgins SB
- Hwy 16 at Rd 85 (Capay) WB
- Cache Creek Casino Resort
- Russell at California EB
- and 124 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — down 0.4 since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 78.8 | first check |
| 2026-07-30 | 77.1 | down 1.7 |
| 2026-07-31 | 76.8 | down 0.3 |
| 2026-08-01 | 76.4 | down 0.4 |
What changed since your last check
- Correctness no change
- Freshness down 1.6
- Rider experience no change
- Realtime quality no change
What changed in this feed
Overall score fell 0.4 points since 2026-07-31.
Same feed file as 2026-07-31; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
Everything we checked
7 findings, ordered by severity.
Show every finding
- Warning721 instances
721 of 721 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 · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning15 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)
- Warning2 instances
2 of 374 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)
- Warning1 instance
A file GTFS asks for (usually feed_info.txt) is missing.
feed_info.txt tells apps who publishes the feed and when it expires; without it nobody is warned before data goes stale.
Fix: Add feed_info.txt with publisher name, URL, language, and feed_start_date/feed_end_date. (One small file, set once in export settings.)
Finding code: missing_recommended_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt is missing its start/end dates (the file itself is absent)
Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.
Fix: Add feed_info.txt with feed_start_date and feed_end_date to your export. (Two fields, set once in export settings.)
Finding code: scorecard_missing_feed_info_dates · 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)
- 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 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 37 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 d139e461-175c-4156-beb0-e6a23b64d978; your National Transit Database ID is 90090. 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 d139e461-175c-4156-beb0-e6a23b64d978 to NTD ID 90090, and keep the feed value stable. Do not change it solely to make the two values equal.
- shapes.txt covers your trips Ready
- All 721 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. States wheelchair access on 100% 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 37 days.
- Accessible Not yet
- States wheelchair access on 100% 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 200 checks over the last 34 days, with 10s median lag.
Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.
Live predictions vs schedule
Arrival predictions ran a median 321s late versus the schedule, and stayed within 1259s nine times in ten. They were on time (about a minute early to five late) 39.6% of the time. 100.0% of reported vehicle positions sat on or near the published route shape.
From the last full realtime sample: how far live arrival predictions sat from the schedule, and whether vehicle positions fell on the route. These feed the realtime score; they change no other category.
Clears the Google and Apple Maps four-week coverage bar. This feed has 37 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.
The published guideline for this jurisdiction 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 100% of stops and 0% of trips.
- Meets shapes.txt with a shape for every trip
All 721 trips have a shape in shapes.txt.
- Gap Fare data published, or the service marked fare-free
No fare data is published.
- Correctness 90 / 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 47 / 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 62 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality 100 / 100
- 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/yolobus/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.