GTFS Scorecard
← All agencies

Prep for a call: printable one-page brief · For your board packet: printable one-pager · Compare with another agency · Watch this feed: get an email before it expires

Feed status · checked 2026-07-09

Bay Area Rapid Transit (BART)

Based on the feed this agency publishes

60.5 / 100

down 0.3 since 2026-07-08

Ahead of 51% of all tracked agencies and 48% of mid-size agencies. Operates in California.

Expires in 29 daysAccessibility 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.1, validator 8.0.1.

Checked for changes 16 minutes ago; last changed 14 days ago.

Top things to fix

Fix 01

Re-export with a validity window that reaches at least 60 days out.Likely your export tool

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.

⏱ One export setting.worth about +51 points

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

Fix 02

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.

⏱ Varies.worth about +12 points

Fix 03

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.

⏱ Usually a vendor support ticket.worth about +8 points

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

Close the loop on each fix. Read the guide, make the change in your tool, and let the next run verify it — the scorecard shows the fix; the agency publishes it.

  1. Re-export with a validity window that reaches at least 60 days out. · Read the fix guide

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.

  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. · Read the fix guide

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.

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

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.

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.

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.

Score by category

Correctness48.8 / 100

The MobilityData validator flagged 13 kinds of issue across 2733 instances (2 error, 2655 warning, 76 informational).

Freshness48.3 / 100

Service data runs out in 29 day(s). Publish an updated feed soon or riders will lose trip planning.

Rider experience67.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.

Accessibility37.5 / 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 quality84.2 / 100

Sampled 6 times: 2 of 3 feeds healthy; 85.4% of scheduled trips had live predictions; predictions ran a median of 0s behind schedule.

Over time

Overall score across the last 20 checks — down 0.3 since 2026-07-08.

2026-06-19: 67.42026-06-20: 66.92026-06-21: 67.32026-06-22: 66.42026-06-23: 65.92026-06-24: 65.82026-06-25: 64.32026-06-26: 65.22026-06-27: 64.42026-06-28: 64.12026-06-29: 63.82026-06-30: 63.52026-07-01: 63.12026-07-02: 62.82026-07-04: 62.12026-07-05: 61.82026-07-06: 61.52026-07-07: 61.12026-07-08: 60.82026-07-09: 60.5
Show the numbers
CheckScoreChange
2026-06-1967.4 first check
2026-06-2066.9 down 0.5
2026-06-2167.3 up 0.4
2026-06-2266.4 down 0.9
2026-06-2365.9 down 0.5
2026-06-2465.8 down 0.1
2026-06-2564.3 down 1.5
2026-06-2665.2 up 0.9
2026-06-2764.4 down 0.8
2026-06-2864.1 down 0.3
2026-06-2963.8 down 0.3
2026-06-3063.5 down 0.3
2026-07-0163.1 down 0.4
2026-07-0262.8 down 0.3
2026-07-0462.1 down 0.7
2026-07-0561.8 down 0.3
2026-07-0661.5 down 0.3
2026-07-0761.1 down 0.4
2026-07-0860.8 down 0.3
2026-07-0960.5 down 0.3

What changed since your last check

What changed in this feed

Overall score fell 0.3 points since 2026-07-08.

Same feed file as 2026-07-08; the published zip did not change.

New since 2026-07-08 (1 finding)

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-06-19 this feed started at grade D. On 2026-07-08 feed entered the expiry window (30 days of service left). As of 2026-07-09 it holds grade D.

A plain-language history of this feed, newest first.

Everything we checked

Beyond the grade

Opportunities that do not change your grade today: fare detail, on-demand service, and deeper accessibility data.

NTD certification readiness Needs attention

This feed is close to NTD-ready. 1 validator error to resolve. Service data runs out in 29 days; renew before you certify.

Published Ready
Published at a public URL.
Valid Needs attention
1 validator error to resolve.
Current Needs attention
Service data runs out in 29 days; renew before you certify.
agency_id matches your 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.

In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed and confirm it once a year. This box is a heads-up on whether yours looks ready; it is not the official sign-off.

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). Aligning agency_id with your NTD ID lets the feed line up with your NTD record; the July 2025 final rule links the two on the P-50 form rather than requiring that feed change, and 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. Service data runs out in 29 days; renew to qualify. States wheelchair access on 0% of stops and 100% of trips; the mark needs 90% of each.

Valid Not yet
1 validator error to resolve.
Current Not yet
Service data runs out in 29 days; renew to qualify.
Accessible Not yet
States wheelchair access on 0% of stops and 100% 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.

Can riders use it?

Checks beyond structural validation: places where the feed is valid but a rider still could not travel.

These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.

Realtime reliability

The realtime feed responded on 100.0% of 105 checks over the last 16 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.

Prediction accuracy

Arrival predictions ran right on the schedule, and stayed within 37s nine times in ten. They were on time (about a minute early to five late) 99.9% of the time.

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 31 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 2 validator errors, the other thing Maps checks at onboarding; the findings below name each fix.

How this agency maps to the standards

A data-quality lens, not a compliance determination. Each category shows this feed's score and the standards it relates to: the FTA National Transit Database GTFS requirement, the MobilityData grading scheme, and the Google Transit gate. 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 (2 of 5 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 100% of trips.

  • Not measured here shapes.txt with a shape for every trip

    Shape coverage has not been measured for this feed.

  • Meets Fare data published, or the service marked fare-free

    Fare data is published.

Correctness 49 / 100
GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading: stop locations, route names and colors. Google Transit: a feed must pass validation to stay in Maps.
Freshness 48 / 100
The FTA National Transit Database expectation of a valid, current feed. Google Transit: an expired calendar drops the agency from Maps.
Rider experience 68 / 100
GTFS Best Practices for rider-facing fields. MobilityData grading: stop names and headsigns.
Realtime quality 84 / 100
GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.

Show your grade

Put a live badge on your agency site or feed README. It updates daily and links back to this scorecard.

Bay Area Rapid Transit (BART) GTFS data quality grade: D

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/bay-area-rapid-transit-bart/2026-07-09.json and never overwritten, pinning the grade, category scores, rubric version, validator version, and the scored feed's sha256 as they stood on 2026-07-09. Use it in a board packet, an NTD narrative, 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.