Feed status · checked 2026-08-01
Big Blue Bus
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in California.
A data-quality and completeness lens to help an agency improve its GTFS feed. Not an official compliance determination from any transit program. New to this? How to read your scorecard. Interactive view of this scorecard. Rubric v1.3, validator 8.0.1.
Checked for changes 81 minutes ago; last changed 3 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
Ask your AVL vendor why the feed stopped advancing; the GTFS-Realtime header timestamp should move forward on every publish.
The realtime feed's last update was about 478 days old when sampled. A realtime feed this far behind has effectively stopped. Riders see buses that already left, or apps quietly fall back to the schedule while still showing a live label.
⏱ A vendor support ticket; treat it as a feed outage.worth about +29 points in its category
Review the rule documentation for 'duplicate_key' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Duplicate key (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +18 points in its category
Check with your AVL vendor that every vehicle assignment flows into TripUpdates, including school-day and tripper runs.
32 of 32 trips scheduled during the sampling window had no live predictions. Riders on those trips get schedule data dressed up as realtime. Caltrans expects every operating trip in TripUpdates.
⏱ A vendor data-mapping question.worth about +41 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
- The realtime feed's last update was about 478 days old when sampled.
- Next action
- Ask your AVL vendor why the feed stopped advancing; the GTFS-Realtime header timestamp should move forward on every publish.
- 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
- Duplicate key (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'duplicate_key' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
- 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
- 32 of 32 trips scheduled during the sampling window had no live predictions.
- Next action
- Check with your AVL vendor that every vehicle assignment flows into TripUpdates, including school-day and tripper runs.
- 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.
Ask your AVL vendor why the feed stopped advancing; the GTFS-Realtime header timestamp should move forward on every publish.
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.
Review the rule documentation for 'duplicate_key' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
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.
Check with your AVL vendor that every vehicle assignment flows into TripUpdates, including school-day and tripper runs. · 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 133 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
- Live-arrival data covered 0% 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 8 kinds of issue across 1132 instances (34 error, 1096 warning, 2 informational).
Service data covers the next 133 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.
2 accessibility depth signals
4 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (R10, 43, R10, 43).
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.
908 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("4TH NB & SANTA MONICA NS", "SANTA MONICA EB & 6TH NS", "SANTA MONICA EB & CENTINELA FS", 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.
Sampled 9 times: 3 of 3 configured feeds healthy; 0.0% of scheduled trips had live predictions; vehicle position plausibility was not measurable.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 918 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 (orange)
- 2 (purple)
- 3 (red)
- 5 (gray)
- 7 (gray)
- 8 (teal)
- 9 (pink)
- R10 (teal)
- R12 (pink)
- 14 (brown)
- 15 (yellow)
- 16 (pink)
- 17 (yellow)
- 18 (brown)
- 41 (red)
- 43 (teal)
- 44 (orange)
- 1 (orange)
- 2 (purple)
- 3 (red)
- 5 (gray)
- 7 (gray)
- 8 (teal)
- 9 (pink)
- R10 (teal)
- R12 (pink)
- 14 (brown)
- 15 (yellow)
- 16 (pink)
- 17 (yellow)
- 18 (brown)
- 41 (red)
- 43 (teal)
- 44 (orange)
| Route | Type | Line color |
|---|---|---|
| 1 Main St & Santa Monica Blvd/UCLA | Bus | orange |
| 2 Wilshire Blvd/UCLA | Bus | purple |
| 3 Lincoln Blvd/LAX | Bus | red |
| 5 Olympic Blvd | Bus | gray |
| 7 Pico Blvd | Bus | gray |
| 8 Ocean Park Blvd & Westwood Bl/UCLA | Bus | teal |
| 9 Pacific Palisades | Bus | pink |
| R10 Downtown LA Freeway Express | Bus | teal |
| R12 Venice/Westwood Sta/UCLA Rapid | Bus | pink |
| 14 Bundy Dr & Centinela Ave | Bus | brown |
| 15 Barrington Ave | Bus | yellow |
| 16 Wilshire Bl/Bundy Dr-Playa del Rey | Bus | pink |
| 17 Culver City Sta - UCLA | Bus | yellow |
| 18 UCLA - Marina del Rey | Bus | brown |
| 41 SMC- 17th St Station- Montana | Bus | red |
| 43 26th Street | Bus | teal |
| 44 17th St Sta - SMC Bundy Campus | Bus | orange |
| 1 Main St & Santa Monica Blvd/UCLA | Bus | orange |
| 2 Wilshire Blvd/UCLA | Bus | purple |
| 3 Lincoln Blvd/LAX | Bus | red |
| 5 Olympic Blvd | Bus | gray |
| 7 Pico Blvd | Bus | gray |
| 8 Ocean Park Blvd & Westwood Bl/UCLA | Bus | teal |
| 9 Pacific Palisades | Bus | pink |
| R10 Downtown LA Freeway Express | Bus | teal |
| R12 Venice/Westwood Sta/UCLA Rapid | Bus | pink |
| 14 Bundy Dr & Centinela Ave | Bus | brown |
| 15 Barrington Ave | Bus | yellow |
| 16 Wilshire Bl/Bundy Dr-Playa del Rey | Bus | pink |
| 17 Culver City Sta - UCLA | Bus | yellow |
| 18 UCLA - Marina del Rey | Bus | brown |
| 41 SMC- 17th St Station- Montana | Bus | red |
| 43 26th Street | Bus | teal |
| 44 17th St Sta - SMC Bundy Campus | Bus | orange |
List every stop
- 20TH SB & DELAWARE FS
- 20TH SB & PEARL NS
- VENICE WB & ROBERTSON NS
- NATIONAL WB & BAGLEY FS
- NATIONAL WB & CASTLE HEIGHTS NS
- OCEAN PARK WB & BEVERLEY NS
- OLIVE NB & 9TH FS
- PALMS WB & JASMINE FS
- PALMS WB & MOTOR FS
- SANTA MONICA EB & 3RD FS
- PALMS EB & MOTOR FS
- PALMS EB & JASMINE FS
- PALMS EB & EXPOSITION NS (Palms Station)
- NATIONAL EB & CASTLE HEIGHTS NS
- NATIONAL EB & BAGLEY NS
- OLIVE NB & VENICE NS
- MOTOR SB & CHEVIOT PLAYGROUND MB
- MOTOR SB & MONTE MAR NS
- MOTOR SB & CRESTA NS
- MOTOR SB & CLUB NS
- MOTOR SB & GLENBARR NS
- MOTOR SB & CHEVIOT NS
- MOTOR SB & BANNOCKBURN NS
- MOTOR NB & MANNING FS
- MOTOR NB & BANNOCKBURN NS
- MOTOR NB & CHEVIOT NS
- MOTOR NB & GLENBARR FS
- MOTOR NB & CLUB NS
- MOTOR NB & CRESTA NS
- MOTOR NB & MONTE MAR NS
- CENTINELA NB & SHORT FS
- CENTINELA NB & LOUISE FS
- CENTINELA NB & CHARNOCK FS
- CENTINELA NB & PALMS NS
- CENTINELA NB & WOODBINE FS
- BUNDY NB & PEARL NS
- BARRINGTON NB & TERRYHILL FS
- SAWTELLE NB & SANTA MONICA FS
- FLOWER SB & 4TH NS
- BARRINGTON NB & 400 BL (REC CTR) NS
- BARRINGTON SB & 400 BK (REC CTR) MB
- BARRINGTON SB & TERRYHILL NS
- BUNDY SB & PEARL NS
- CENTINELA SB & WOODBINE NS
- CENTINELA SB & PALMS NS
- GRAND SB & VENICE NS
- CENTINELA SB & CHARNOCK NS
- MAIN NB & MARINE NS
- NATIONAL PLACE WB & OVERLAND FS
- 4TH SB & CIVIC CENTER MB
- MAIN SB & OLYMPIC NS
- MAIN NB & OLYMPIC FS
- CALIFORNIA EB & ABBOT KINNEY FS
- NATIONAL WB & ROBERTSON FS
- OVERLAND NB & PALMS FS
- LINCOLN SB & LMU DR FS
- PICO WB & SHERBOURNE NS
- SUNSET EB & MARQUEZ PL FS
- SUNSET WB & MARQUEZ PL NS
- ENTRADA EB & OCEAN NS
- OVERLAND SB & NATIONAL PLACE FS
- WESTWOOD PLAZA NB & J STEIN EYE FS
- WESTWOOD PLAZA SB & UCLA MEDICAL CENTER FS
- SAN VICENTE EB & ANITA NS
- 26TH SB & MONTANA FS
- 14TH NB & SANTA MONICA FS
- MONTANA EB & 17TH FS
- WESTWOOD PLAZA NB & STRATHMORE FS (Gateway Plaza)
- LINCOLN SB & PICO FS
- LINCOLN SB & MANCHESTER NS
- LINCOLN NB & MANCHESTER FS
- 20TH SB & SANTA MONICA FS
- OCEAN PARK WB & 14TH FS
- GRAND SB & 9TH FS
- SANTA MONICA WB & SEPULVEDA FS
- SANTA MONICA WB & 6TH NS
- 20TH SB & PICO FS
- LINCOLN NB & CALIFORNIA (VEN) NS
- LINCOLN SB & BROADWAY (VEN) NS
- 7TH SB & BROADWAY NS
- SANTA MONICA EB & 17TH FS
- GRAND SB & OLYMPIC FS
- SANTA MONICA WB & VETERAN FS
- SMC BUNDY CAMPUS PARKING LOT
- 20TH NB & PICO FS
- 20TH NB & DELAWARE NS
- 20TH NB & OLYMPIC NS
- STEWART SB & PENNSYLVANIA FS
- WILSHIRE EB & HOPE NS (7th St/Metro Center Station)
- WILSHIRE EB & GRAND NS
- NATIONAL EB & ROBERTSON FS
- COLORADO EB & 26TH FS
- PICO WB & STEWART FS
- LINCOLN NB & BLUFF CREEK FS
- NATIONAL EB & SEPULVEDA FS
- LINCOLN SB & BLUFF CREEK FS
- MANCHESTER EB & SEPULVEDA NS
- 6TH SB & SANTA MONICA FS
- LINCOLN SB & JEFFERSON FS
- 26TH SB & SAN VICENTE MB
- 4TH SB & SANTA MONICA FS
- WESTERN NB & WILSHIRE FS (Wilshire/Western Station)
- WILSHIRE WB & WESTERN FS (Wilshire/Western Sta)
- MAIN NB & MARKET NS
- WESTWOOD NB & PICO FS
- PICO EB & SAN VICENTE FS
- CRENSHAW NB & PICO FS
- CRENSHAW NB & OLYMPIC NS
- WILSHIRE EB & CRENSHAW FS
- CRENSHAW SB & WILSHIRE FS
- CRENSHAW SB & OLYMPIC FS
- PICO WB & CRENSHAW FS
- MAIN (LA) NB & ALAMEDA NS
- ROBERTSON BL NB & VENICE BL NS (Culver City Station)
- MOTOR SB & PICO FS
- CHARLES E YOUNG @ P2 GARAGE
- CENTINELA NB & WASHINGTON BLVD FS
- PICO EB & GATEWAY NS
- OCEAN PARK EB & BUNDY FS
- 7TH SB & OLYMPIC BLVD NS
- CENTINELA NB & VENICE NS
- PICO WB & BUNDY FS
- BARRINGTON NB & WILSHIRE NS
- BARRINGTON PL NB & CHAYOTE ST NS
- BARRINGTON SB & WILSHIRE NS
- MANNING EB & NATIONAL NS (Palms Station)
- NATIONAL WB & PALMS NS (Palms Station)
- WILSHIRE EB & 17TH FS
- 7TH NB & SAN VICENTE FS
- NATIONAL WB & MOTOR NS
- BLUFF CREEK WB & CENTINELA FS
- BLUFF CREEK WB & ARTISANS FS
- BLUFF CREEK WB & CAMPUS CENTER NS
- CAMPUS CENTER NB & MILLENIUM FS
- CENTINELA NB & JEFFERSON FS
- CENTINELA NB & LUCILE FS
- CENTINELA NB & 90 EAST MB
- CENTINELA NB & BRADDOCK NS
- CENTINELA NB & CULVER NS
- CENTINELA SB & WASHINGTON NS
- CENTINELA SB & SHORT NS
- CENTINELA SB & CULVER FS
- CENTINELA SB & BRADDOCK NS
- CENTINELA SB & 90 EAST MB
- CENTINELA SB & LUCILE NS
- CAMPUS CENTER SB & JEFFERSON FS
- CAMPUS CENTER SB & MILLENIUM FS
- BLUFF CREEK EB & CAMPUS CENTER FS
- BARRINGTON NB & OLYMPIC FS
- BARRINGTON NB & LA GRANGE FS
- BARRINGTON NB & SANTA MONICA NS
- BARRINGTON NB & TEXAS NS
- BARRINGTON NB & KIOWA FS
- BARRINGTON NB & SAN VICENTE NS
- BARRINGTON SB & KIOWA FS
- BARRINGTON SB & TEXAS NS
- BARRINGTON SB & NEBRASKA FS
- BARRINGTON SB & LA GRANGE FS
- BARRINGTON SB & OLYMPIC NS
- BARRINGTON SB & GORHAM NS
- VENICE EB & BEETHOVEN FS
- BARRINGTON SB & SUNSET FS
- VENICE WB & BEETHOVEN FS
- SALTAIR SB & WILSHIRE FS
- ROSE WB & RUTH NS
- ROSE EB & 6TH AVE FS
- OVERLAND NB & VENICE FS
- VIA MARINA SB & ADMIRALTY NS
- SANTA MONICA WB & 17TH FS
- VIA MARINA SB & PANAY FS
- VIA MARINA SB & MARQUESAS NS
- VIA DOLCE NB & DELL ALLEY FS
- CENTURY PARK EAST SB & OLYMPIC FS
- CENTURY PARK EAST SB & GALAXY FS
- CENTURY PARK EAST NB & GALAXY NS
- CENTURY PARK EAST NB & OLYMPIC NS
- GLENCOE NB & MAXELLA FS
- GLENCOE NB & 4114 GLENCOE MB
- GLENCOE NB & BEACH FS
- WASHINGTON EB & REDWOOD FS
- WASHINGTON EB & BEETHOVEN FS
- WADE NB & MITCHELL FS
- WADE NB & PACIFIC FS
- WALGROVE NB & LUCILLE NS
- WALGROVE NB & MORNINGSIDE FS
- WALGROVE NB & ROSE FS
- 23RD NB & ASHLAND NS
- 20TH NB & PEARL FS
- OLYMPIC EB & EXPO BIKE PATH NS
- STEWART NB & PENNSYLVANIA FS
- COLORADO EB & STANFORD NS
- COLORADO EB & FRANKLIN FS
- CENTINELA NB & SANTA MONICA FS
- CENTINELA SB & SANTA MONICA FS
- COLORADO WB & CENTINELA FS
- COLORADO WB & STANFORD NS
- 20TH SB & OLYMPIC FS
- 23RD SB & OCEAN PARK FS
- 23RD SB & ASHLAND NS
- WALGROVE SB & ROSE NS
- WALGROVE SB & MORNINGSIDE FS
- WALGROVE SB & PALMS FS
- VENICE EB & WALGROVE FS
- WADE SB & VENICE FS
- WADE SB & MITCHELL FS
- WASHINGTON WB & BEETHOVEN NS
- WASHINGTON WB & REDWOOD FS
- GLENCOE SB & BEACH FS
- GLENCOE SB & 4141 GLENCOE FS
- GLENCOE SB & MAXELLA NS
- MINDANAO WB & GLENCOE FS
- 17TH SB & COLORADO FS (17th St/SMC Station)
- COLORADO WB & 17TH NS (17th St/SMC Sta)
- 14TH SB & MICHIGAN FS
- 7TH NB & BROADWAY NS
- 7TH NB & SUNSET NS
- 4TH NB & ROSE FS
- 4TH NB & PIER FS
- LINCOLN NB & SANTA MONICA FS
- LINCOLN SB & SANTA MONICA NS
- 4TH SB & ASHLAND NS
- SANTA MONICA EB & YALE FS
- 4TH SB & ROSE NS
- 7TH SB & SUNSET FS
- 7TH SB & BROADWAY FS
- SAN VICENTE EB & 14TH FS
- 17TH SB & PEARL FS
- SAN VICENTE WB & GALE PL NS
- MAIN SB & PICO NS
- SANTA MONICA EB & WESTGATE NS
- SANTA MONICA EB & BUNDY NS
- OLYMPIC WB & CLOVERFIELD FS
- 26TH SB & LA MESA NS
- BARRINGTON NB & NEBRASKA FS
- WALGROVE SB & LUCILLE NS
- PALMS WB & GLENDON FS
- PALMS WB & KELTON FS
- SAWTELLE NB & PALMS FS
- SAWTELLE NB & STANWOOD FS
- SAWTELLE NB & NATIONAL FS
- SAWTELLE NB & IVY FS
- SAWTELLE NB & EXPOSITION FS
- SAWTELLE SB & OLYMPIC FS
- SAWTELLE SB & IVY FS
- SAWTELLE SB & NATIONAL NS
- SAWTELLE SB & STANWOOD NS
- SAWTELLE SB & PALMS NS
- PALMS EB & SEPULVEDA FS
- PALMS EB & KELTON FS
- PALMS EB & GLENDON FS
- and 668 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 37.4 | first check |
| 2026-07-30 | 52.0 | up 14.6 |
| 2026-07-31 | 52.0 | no change |
| 2026-08-01 | 52.0 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
- Realtime quality no change
What changed in this feed
Overall grade and score held steady since 2026-07-31.
Same feed file as 2026-07-31; the published zip did not change.
Changed counts
- down 32 of 32 trips scheduled during the sampling window had no live predictions. (90 → 32) (scorecard_rt_trip_coverage)
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
What changed over time
On 2026-07-25 this feed started at grade F. On 2026-07-30 feed renewed to a current calendar. As of 2026-08-01 it holds grade F.
A plain-language history of this feed, newest first.
- 2026-07-30 Feed renewed to a current calendar.
Everything we checked
14 findings, ordered by severity.
Show every finding
- Error34 instances
Duplicate key (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'duplicate_key' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: duplicate_key · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error1 instance
The realtime feed's last update was about 478 days old when sampled.
A realtime feed this far behind has effectively stopped. Riders see buses that already left, or apps quietly fall back to the schedule while still showing a live label.
Fix: Ask your AVL vendor why the feed stopped advancing; the GTFS-Realtime header timestamp should move forward on every publish. (A vendor support ticket; treat it as a feed outage.)
Finding code: scorecard_rt_feed_lapsed
- Warning6546 instances
6546 of 6546 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)
- Warning918 instances
918 of 918 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)
- Warning880 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)
- Warning192 instances
Some stops sit far from the route line, going by the feed's own distance values.
Trip planners may draw the route down the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree. (Usually an export-tool fix, not hand editing.)
Finding code: stop_too_far_from_shape_using_user_distance · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning32 instances
32 of 32 trips scheduled during the sampling window had no live predictions.
Riders on those trips get schedule data dressed up as realtime. Caltrans expects every operating trip in TripUpdates.
Fix: Check with your AVL vendor that every vehicle assignment flows into TripUpdates, including school-day and tripper runs. (A vendor data-mapping question.)
Finding code: scorecard_rt_trip_coverage · Read the fix guide · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)
- Warning17 instances
Two or more routes share the same name.
Riders can't tell the routes apart in apps.
Fix: Give each route a distinct short or long name. (One field per route.)
Finding code: duplicate_route_name · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning4 instances
On some trips the stops fall along the route line in a different order than the schedule lists.
Trip planners can draw the bus doubling back or skipping ahead, which confuses riders reading the map.
Fix: Check the stop order and the shape direction in your scheduling software; the shape is often drawn backwards. (A few minutes per flagged trip.)
Finding code: stops_match_shape_out_of_order · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
Some files leave out fields that GTFS asks for but does not require.
Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.
Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)
Finding code: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt lists no contact email and no contact URL.
Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.
Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)
Finding code: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info880 instances
About 880 stop names are written in ALL CAPS.
Mixed-case names are easier to read in apps and are read more naturally by screen readers.
Fix: Rename stops to mixed case where the language has letter case (for example, 'Central Station'). (Often a bulk fix in your scheduling software.)
Finding code: scorecard_stop_names_all_caps · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info2 instances
The feed includes a file that is not part of the GTFS spec.
Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.
Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)
Finding code: unknown_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
NTD GTFS readiness Needs attention
This feed is close to NTD-ready. 1 validator error to resolve.
- Published Ready
- Published at a public URL.
- Valid Needs attention
- 1 validator error to resolve.
- Current Ready
- Service data covers the next 133 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 6216179; your National Transit Database ID is 90008. 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 6216179 to NTD ID 90008, and keep the feed value stable. Do not change it solely to make the two values equal.
- shapes.txt covers your trips Ready
- All 6546 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. 1 validator error to resolve. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Not yet
- 1 validator error to resolve.
- Current Met
- Service data covers the next 133 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.
Realtime reliability
The realtime feed responded on 100.0% of 200 checks over the last 34 days, with 40124552s median lag.
Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.
Clears the Google and Apple Maps four-week coverage bar. This feed has 133 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 34 validator errors, the other thing Maps checks at onboarding; the findings below name each fix.
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.
- Gap Produce no critical errors in the MobilityData GTFS Validator
1 validator error to resolve.
- 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 6546 trips have a shape in shapes.txt.
- Meets Fare data published, or the service marked fare-free
Fare data is published.
- Correctness 48 / 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 100 / 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 38 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality 29 / 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/big-blue-bus/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.