← All agencies

Feed status · checked 2026-08-01

Beach Cities Transit

Based on the feed this agency publishes

Service mode Bus

FDCBA

62.2 / 100

unchanged since 2026-07-31

Catalogued in California.

Feed expiredAccessibility gaps

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 3 hours ago; last fetch returned HTTP 404.

Measured 4 of 4 score categories from the Mobility Database's mirror copy of the feed.

How we measured this

Confidence in this measurement: medium.

All four score categories were measured this run.
Realtime was sampled in one bounded window of 9 snapshots.
The agency's own feed URL was unreachable, so the Mobility Database's hosted mirror copy was scored instead.

Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.

Top things to fix

Fix 01

Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.Likely your export tool

Service data ended 1308 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.

⏱ Usually one export setting; export on a schedule so it never lapses again.worth about +100 points in its category

Fix 02

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

208 of 208 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.

⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category

Fix 03

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

227 of 227 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

Finding handoff

Move one finding to a recheck

Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.

Feed evidence: Service data ended 1308 day(s) ago.
Next action: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.
Recheck: Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.

Copy handoff text

Agency: Beach Cities Transit
Finding: scorecard_feed_expired
Feed evidence: Service data ended 1308 day(s) ago.
Why it matters: When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
Requested change: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.
Recheck: Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Evidence: https://gtfsscorecard.org/agency/beach-cities-transit/?finding=scorecard_feed_expired#finding-handoff

How to make and check these changes

Check the result on the published feed. Read the guide, make the change in your tool, and use the next comparable run to see whether the finding is still reported. Only an action or ticket record can attribute who made the change.

Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. · 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. Self-check a feed before you publish.
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
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
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 was 1308 days ago.
Published accessibility data: Accessibility information is stated for 0% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
Fare information: Fare information is published using GTFS Fares v1.
Realtime information: One or more realtime feeds were reachable; live-arrival coverage is not known.

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.

Hi,

Our GTFS feed (Beach Cities Transit) scored D (62.2 out of 100) on the GTFS Scorecard. Could you review these in our export settings:

1. Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.
   What: Service data ended 1308 day(s) ago.
   Finding code: scorecard_feed_expired
   Guide: https://gtfsscorecard.org/fix/scorecard_feed_expired/

2. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
   What: 208 of 208 stops don't say whether a wheelchair user can board there.
   Finding code: scorecard_wheelchair_boarding_unknown
   Guide: https://gtfsscorecard.org/fix/scorecard_wheelchair_boarding_unknown/

3. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
   What: 227 of 227 trips don't say whether the vehicle is wheelchair accessible.
   Finding code: scorecard_wheelchair_accessible_unknown
   Guide: https://gtfsscorecard.org/fix/scorecard_wheelchair_accessible_unknown/

Full scorecard: https://gtfsscorecard.org/agency/beach-cities-transit/

Send the agency a note

Supporting this agency? Copy this and email it to them. It names what lapsed, why it matters to riders, and the one setting to change.

Hi Beach Cities Transit team,

Service data ended 1308 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.

The fix is usually one export setting: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.

This came from your GTFS data quality scorecard, which checks the feed you publish and lists the fixes in plain language: https://gtfsscorecard.org/agency/beach-cities-transit/

Score by category

Correctness83.0 / 100

The MobilityData validator flagged 6 kinds of issue across 8 instances (0 error, 6 warning, 2 informational).

Freshness0.0 / 100

Service data ended 1308 day(s) ago. Trip planners have likely already dropped this feed.

Rider experience52.5 / 100

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.

Accessibility0 / 100

0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.

FaresLegacy fares

Fares are applied to trips.

Realtime quality100.0 / 100

Sampled 9 times outside service hours: 3 of 3 configured feeds healthy; 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 208 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.

Beach Cities Transit 102 Northbound (blue)
Beach Cities Transit 102 Southbound (blue)
Beach Cities Transit 109 Northbound (red)
Beach Cities Transit 109 Southbound (red)

Routes in Beach Cities Transit's feed
Route	Type	Line color
Beach Cities Transit 102 Northbound	Bus	blue
Beach Cities Transit 102 Southbound	Bus	blue
Beach Cities Transit 109 Northbound	Bus	red
Beach Cities Transit 109 Southbound	Bus	red

List every stop

Palos Verdes Blvd / Via Valencia
Catalina Ave. / Elena Ave.
Catalina Ave. / Avenue I
Catalina Ave. / Avenue F
Catalina Ave. / Avenue C
Catalina Ave. / Knob Hill Ave.
Catalina Ave. / Topaz St.
Catalina Ave. / Sapphire St.
Catalina Ave. / Pearl St.
Catalina Ave. / Carnelian St.
Beryl St. / Harbor Dr.
Hermosa Ave. / Lyndon St.
Hermosa Ave. / 2nd St.
Hermosa Ave. / 6th St.
Hermosa Ave. / 8th St.
Hermosa Ave. / 10th St.
Hermosa Ave. / 16th St.
Hermosa Ave. / 19th St.
Hermosa Ave. / 22nd St.
Hermosa Ave. / 26th St.
Manhattan Ave. / Longfellow Ave.
Manhattan Ave. / 1st St.
Manhattan Ave. / 4th St.
Manhattan Ave. / 10th St.
Highland Ave. / 14th St.
Highland Ave. / 18th St.
Highland Ave. / Marine Ave.
Highland Ave. / 26th St.
Highland Ave. / 30th St.
Highland Ave. / 33rd St.
Highland Ave. / Rosecrans Ave.
Rosecrans Ave. / Alma Ave.
Rosecrans Ave. / Blanche Rd.
Rosecrans Ave. / Pacific Ave.
Rosecrans Ave. / Walnut Ave.
Rosecrans Ave. / Sepulveda Blvd.
Parkview Ave. / Village Dr.
Apollo St / Rosecrans Ave.
Douglas St. / Park Pl
Rosecrans Ave. / Nash St.
Rosecrans Ave. / Village Dr.
Park Pl. / Plaza El Segundo
Sepulveda Blvd. / El Segundo Blvd.
Grand Ave. / Sepulveda Blvd.
Grand Ave. / Kansas St.
Grand Ave. / Center St.
Grand Ave. / Lomita St.
Grand Ave. / Sheldon St.
Grand Ave. / Eucalyptus Dr.
Main St. / Holly Ave.
Main St./ Mariposa Ave
Main St. / Oak Ave.
Main St. / Walnut Ave.
Main St. / Imperial Ave.
Imperial Ave. / Eucalyptus Dr.
Imperial Ave. / Sheldon St.
Imperial Ave. / McCarthy Ct.
Imperial Ave. / Center St.
California St. / Imperial Ave.
Imperial Hwy. / California St.
Imperial Hwy. / Sepulveda Blvd.
Imperial Hwy. / Hughes Wy.
Imperial Hwy. / Nash St.
Imperial Hwy. / Douglas St.
Aviation Station / Bus Bay 3
Aviation Blvd. / Imperial Hwy.
Aviation Blvd. / 111th St.
Aviation Blvd. / 104th St.
Century Blvd./ Aviation Blvd..
Century Blvd. / International Rd.
Airport Blvd. / Century Blvd.
96th St. / Airport Blvd.
LAX Transit Center / Bus Bay 6
96th St. / Airport Blvd.
Century Blvd. / Airport Blvd.
Century Blvd. / International Rd.
Century Blvd. / Aviation Blvd.
Aviation Blvd. / 104th St.
Aviation Blvd. / 111th St.
Imperial Hwy. / Aviation Blvd.
Imperial Hwy. / Douglas St.
Imperial Hwy. / Nash St.
Imperial Hwy. / Hughes Wy.
Imperial Hwy. / Sepulveda Blvd.
Imperial Ave. / California St.
Imperial Ave. / Center St.
Imperial Ave. / McCarthy Ct.
Imperial Ave. / Sheldon St.
Imperial Ave. / Eucalyptus Dr.
Main St. / Imperial Ave.
Main St. / Walnut Ave.
Main St. / Oak Ave.
Main St / Mariposa Ave.
Main St. / Holly Ave.
Grand Ave. / Main St.
Grand Ave. / Eucalyptus Dr.
Grand Ave. / Sheldon St.
Grand Ave. / Lomita St.
Grand Ave. / Center St.
Grand Ave. / Kansas St.
Grand Ave. / Sepulveda Blvd.
Sepulveda Blvd. / El Segundo Blvd.
Park Pl. / Plaza El Segundo
Rosecrans Ave. /Sepulveda Blvd.
Rosecrans Ave. / Walnut Ave.
Rosecrans Ave. / Pacific Ave.
Rosecrans Ave. / Blanche Rd.
Highland Ave. / 33rd St.
Highland Ave. / 30th St
Highland Ave. / 26th St.
Highland Ave. / Marine Ave.
Highland Ave. / 18th St.
Highland Ave. / 14th St.
Manhattan Ave. / 10th St.
Manhattan Ave. / 4th St.
Manhattan Ave. / 1st St.
Manhattan Ave. / Longfellow Ave.
Manhattan Ave. / 27th St.
Hermosa Ave. / 25th St.
Hermosa Ave. / 22nd St.
Hermosa Ave. / 19th St.
Hermosa Ave. / 16th St.
Hermosa Ave. / 11th St.
Hermosa Ave. / 8th St.
Hermosa Ave. / 6th St.
Hermosa Ave. / 2nd St.
Harbor Dr. / Yacht Club Wy.
Beryl St. / Harbor Dr.
Catalina Ave. / Beryl St.
Catalina Ave. / Carnelian St.
Catalina Ave. / Diamond St.
Catalina Ave. / Torrance Blvd.
Catalina Ave. / Pearl St.
Catalina Ave. / Sapphire St.
Catalina Ave. / Topaz St.
Catalina Ave. / Knob Hill Ave.
Catalina Ave. / Avenue C
Catalina Ave. / Avenue F
Avenue I / Elena Ave.
Redondo Beach Pier
Catalina Ave. / Torrance Blvd.
Catalina Ave. / Garnet St.
Catalina Ave. / Emerald St.
Catalina Ave. / Diamond St.
Diamond St. / PCH
Diamond St. / Sea Hawk Way
Diamond St. / Lucia Ave.
Prospect Ave. / Diamond St.
Beryl St. / Prospect Ave.
Beryl St. / Flagler Ln.
190th St. / Beryl St.
Rindge Ln. / 190th St.
Rindge Ln. / Ripley Ave.
Rindge Ln. / Pullman Ln.
Rindge Ln. / Clark Ln.
Rindge Ln. / Grant Ave.
Rindge Ln. / Carnegie Ln.
Artesia Blvd. / Rindge Ln.
Artesia Blvd. / Mackay Ln.
Artesia Blvd. / Felton Ln.
Artesia Blvd. / Inglewood Ave.
Artesia Blvd. / Kingsdale Ave.
Hawthorne Blvd. / Artesia Blvd.
Hawthorne Blvd. / Market Place Drive
Hawthorne Blvd. / 182nd St.
Artesia Blvd. / Firmona Ave.
Artesia Blvd. / Inglewood Ave.
Artesia Blvd. / Felton Ln.
Artesia Blvd. / Mackay Ln.
Vail Ave. / Artesia Blvd.
Vail Ave. / Nelson Ave.
Vail Ave. / Voorhees Ave.
Vail Ave. / Gates Ave.
Vail Ave. / Robinson St.
Vail Ave. / May Ave.
Vail Ave. / Pinckard Ave.
Vail Ave. / Warfield Ave.
Redondo Beach Ave. / Manhattan Beach Blvd.
Redondo Beach Ave. / Santa Fe Ave.
Redondo Beach Ave. / Space Park Drive
Redondo Beach Green Line Station
Redondo Beach Ave. / Marine Ave.
Redondo Beach Ave. / Space Park Dr.
Redondo Beach Ave. / Manhattan Beach Blvd.
Vail Ave. / Warfield Ave.
Vail Ave. / Bataan Rd.
Vail Ave. / Ernest Ave.
Vail Ave. / Robinson St.
Vail Ave. / Gates Ave.
Vail Ave. / Voorhees Ave.
Vail Ave. / Nelson Ave.
Vail Ave. / Artesia Blvd.
Rindge Ln. / Artesia Blvd.
Rindge Ln. / Carnegie Ln.
Rindge Ln. / Grant Ave.
Rindge Ln. / Clark Ln.
Rindge Ln. / Pullman Ln.
Rindge Ln. / Ripley Ave.
Rindge Ln. / 190th St.
Beryl St. / 190th St.
Beryl St. / Flagler Ln.
Prospect Ave. / Beryl St.
Prosect Ave. / Diamond St.
Diamond St. / Lucia Ave.
Diamond St. / Helberta Ave.
Diamond St. / PCH
Catalina Ave. / Emerald St.
Catalina Ave. / Garnet St.

Over time

Overall score across the last 4 checks — unchanged since 2026-07-31.

Show the numbers

Overall score by check, with the change from the previous check
Check	Score	Change
2026-07-25	62.2	first check
2026-07-30	62.2	no change
2026-07-31	62.2	no change
2026-08-01	62.2	no change

What changed since your last check

Correctness no change
Freshness no change
Rider experience no change
Realtime quality no change

Everything we checked

11 findings, ordered by severity.

Show every finding

Error1 instance
Service data ended 1308 day(s) ago.
When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
Fix: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. (Usually one export setting; export on a schedule so it never lapses again.)
Finding code: scorecard_feed_expired · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
Warning227 instances
227 of 227 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)
Warning208 instances
208 of 208 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)
Warning3 instances
Some service calendars in the feed have already ended.
Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)
Finding code: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning1 instance
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
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
Many of the feed's trips don't run at all in the next 7 days.
It usually means old service periods are still in the export, making the feed bigger and harder to check.
Fix: Trim past service periods the next time you export. (One setting in most export tools.)
Finding code: trip_coverage_not_active_for_next7_days · 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)
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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Info1 instance
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 Not ready

Resolve this before you certify on the D-10. Service data expired 1308 days ago, so FTA would find the link out of date.

Published Ready: Published at a public URL.
Valid Ready: Passes validation with no errors.
Current Not ready: Service data expired 1308 days ago, so FTA would find the link out of date.
agency_id provided Ready: agency.txt provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk each value on the P-50 form.

agency_id equals your NTD ID (optional) 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 227 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. Service data expired 1308 days ago. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.

Valid Met: Passes validation with no errors.
Current Not yet: Service data expired 1308 days ago.
Accessible Not yet: States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.

In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.

A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.

Realtime reliability

The realtime feed responded on 100.0% of 200 checks over the last 34 days, with 0s median lag.

Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.

Below the Google and Apple Maps four-week coverage bar. This feed's last day of service has passed, so Google and Apple Maps will stop showing your agency. Re-export with a calendar that covers at least the next four weeks.

How this agency maps to the standards

The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance, FTA National Transit Database GTFS requirement. Read the full standards crosswalk.

In California, the published guideline is California Transit Data Guidelines. Caltrans' published quality guidelines and compliance checklist; this rubric is anchored to them.

California Minimum GTFS Guidelines checklist (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.
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 227 trips have a shape in shapes.txt.
Meets Fare data published, or the service marked fare-free
Fare data is published.

Correctness 83 / 100: GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading covers stop locations, route names, and colors. Google Transit requires a feed to pass validation for publication. FTA NTD readiness also checks that the published feed is valid.
Freshness 0 / 100: GTFS Schedule best practices call for a dataset that stays current. An expired calendar can remove service from Google Transit and other rider trip planners. FTA NTD readiness also checks that the published feed is current.
Rider experience 52 / 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.

[![Beach Cities Transit GTFS data quality grade: D](https://gtfsscorecard.org/data/artifacts/beach-cities-transit/badge.svg)](https://gtfsscorecard.org/agency/beach-cities-transit/)

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/beach-cities-transit/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.

GTFS Scorecard. (2026). Beach Cities Transit GTFS feed-quality record, dated 2026-08-01 (grade D (62.2/100), rubric v1.3, gtfs-validator 8.0.1, reader archive profile raw-v1, feed sha256 8e8883a31c2c…). https://gtfsscorecard.org/data/artifacts/beach-cities-transit/2026-08-01.json

@misc{gtfsscorecard-beach-cities-transit-2026-08-01,
  title        = {Beach Cities Transit GTFS feed-quality record},
  author       = {GTFS Scorecard},
  year         = {2026},
  howpublished = {\url{https://gtfsscorecard.org/data/artifacts/beach-cities-transit/2026-08-01.json}},
  note         = {Checked 2026-08-01; rubric v1.3; gtfs-validator 8.0.1; reader archive profile raw-v1; grade D (62.2/100)}
}

Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.