Bay Area Rapid Transit (BART)

What changed since the last check

• Correctness no change
• Freshness down 1.7
• Rider experience no change
• Realtime quality no change

Top three things to fix

1. Re-export with a validity window that reaches at least 60 days out.

   Service data runs out in 29 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.

   Effort: One export setting.

   Agencies here usually clear this within about 1 week (based on 61 observed fixes).

2. Review the rule documentation for 'missing_required_column' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

   Missing required column (flagged by the MobilityData validator). See the linked rule for what this affects.

   Effort: Varies.

3. Check the vehicle positions endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.

   The vehicle positions realtime feed failed during sampling. When this feed is down, riders see scheduled times presented as if they were live.

   Effort: Usually a vendor support ticket.

   Agencies here usually clear this within about 1 week (based on 9 observed fixes).

Ready to send to the agency

Hi Bay Area Rapid Transit (BART) team, Service data runs out in 29 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice. The fix is usually one export setting: Re-export with a validity window that reaches at least 60 days out. 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/bay-area-rapid-transit-bart/

Copy this note from the full scorecard.

NTD certification 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 41 days.

agency_id and NTD ID: Not aligned. Your feed's agency_id is BART; your National Transit Database ID is 90003. A feed that serves several agencies (a shared regional feed) can legitimately carry more than one agency_id, so a difference here is a heads-up, not an error. Optionally set the agency_id for your service to 90003 in agency.txt (and the matching agency_id in routes.txt) so the feed lines up with your NTD record. It is a convenience, not a required feed change: FTA also links agency_id to your NTD ID on your P-50 form.

The bar this score answers to

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

Key facts

Feed URL

http://www.bart.gov/dev/schedules/google_transit.zip

Last checked

2026-07-09

Service window

29 days of service data remain. Last service date 2026-08-09.

Feed version

72

State

California