GTFS Scorecard
← All agencies

Feed status · checked 2026-08-01

Bay Area Rapid Transit (BART)

Based on the feed this agency publishes

Service mode Metro + Bus

63.5 / 100

down 0.3 since 2026-07-31

Catalogued 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.3, validator 8.0.1.

Checked for changes 3 hours ago; last changed 4 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 6 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

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 in its category

Fix 02

Add the required column named in the finding to the flagged file.Likely your export tool

A file is missing a column that GTFS requires. Apps may reject the whole file, so riders could lose the affected routes or stops.

⏱ Often an export setting; ask your vendor if it recurs.worth about +12 points in its category

Fix 03

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

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

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 runs out in 29 day(s).
Next action
Re-export with a validity window that reaches at least 60 days out.
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.

  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.

    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.

  2. Add the required column named in the finding to the flagged file. · 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.

  3. 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. 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 29 days.
Published accessibility data
Accessibility information is stated for 0% of stops and 100% 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.

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

The MobilityData validator flagged 14 kinds of issue across 2697 instances (2 error, 2653 warning, 42 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.

3 accessibility depth signals

  • 6 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (Green-S, Green-N, Red-S, Red-N, Blue-S, and more).

    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.

  • 166 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Pleasant Hill / Contra Costa Centre", "Pleasant Hill / Contra Costa Centre", "North Concord / Martinez", and more).

    Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.

  • This feed models stations or entrances but has no pathways.txt and levels.txt.

    Consider: Add pathways.txt connecting entrances, platforms, and elevators, and levels.txt for each floor, so the step-free route is described.

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.

FaresLegacy fares

Fares are applied to trips.

Realtime quality100.0 / 100

Sampled 6 times outside service hours: 2 of 2 configured feeds healthy; predictions ran a median of 0s behind schedule.

Routes and stops

Each route is drawn once, using the longest shape its trips follow; stops are the dots.

This feed has 287 stops.

Skip to route and stop data

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.

  • Yellow-S (yellow)
  • Blue-S (teal)
  • Blue-N (teal)
  • Grey-N (white)
  • Yellow-N (yellow)
  • Grey-S (white)
  • Orange-N (orange)
  • Orange-S (orange)
  • Green-S (green)
  • Green-N (green)
  • Red-S (red)
  • Red-N (red)
Routes in Bay Area Rapid Transit (BART)'s feed
RouteTypeLine color
Yellow-S Antioch to SF Int'l Airport SFO/MillbraeSubway / metroyellow
Blue-S Dublin/Pleasanton to Daly CitySubway / metroteal
Blue-N Daly City to Dublin/PleasantonSubway / metroteal
Grey-N Oakland Int'l Airport OAK to ColiseumSubway / metrowhite
Yellow-N Millbrae/SF Int'l SFO to AntiochSubway / metroyellow
Grey-S Coliseum to Oakland Int'l Airport OAKSubway / metrowhite
Orange-N Berryessa/North San Jose to RichmondSubway / metroorange
Orange-S Richmond to Berryessa/North San JoseSubway / metroorange
Green-S Berryessa/North San Jose to Daly CitySubway / metrogreen
Green-N Daly City to Berryessa/North San JoseSubway / metrogreen
Red-S Richmond to SF Int'l Airport SFO/MillbraeSubway / metrored
Red-N Millbrae/SF Int'l Airport SFO to RichmondSubway / metrored
BridgeA Bus BridgeBusblack (no shape in feed)
BridgeB Bus BridgeBusblack (no shape in feed)
List every stop
  • 12th Street / Oakland City Center
  • B2 13th St and Broadway Entrance / Exit
  • A2 13th St and Broadway Entrance / Exit
  • B3 13th St and Broadway Entrance / Exit
  • A3 Oakland City Center Entrance / Exit
  • A1 12th St and Broadway Entrance / Exit
  • B1 12th St and Broadway Entrance / Exit
  • A4 Frank Ogawa Plaza Entrance / Exit
  • B4 14th St and Broadway Entrance / Exit
  • 16th Street / Mission
  • A 16TH & Mission SW Entrance / Exit
  • B 16TH & Mission NE Entrance / Exit
  • Elevator Entrance / Exit
  • 19th Street Oakland
  • B2 19th and Broadway Entrance / Exit
  • A1 17th and Broaddway Entrance / Exit
  • A2 20th and Broadway Entrance / Exit
  • B4 20th and Broadway Entrance / Exit
  • B3 19th and Broadway Entrance / Exit
  • B1 17th and Broadway Entrance / Exit
  • 24th Street / Mission
  • Elevator Entrance / Exit
  • B 24TH & Mission NE Entrance / Exit
  • A 24TH & Mission SW Entrance / Exit
  • Lake Merritt
  • Lake Merritt
  • Fruitvale
  • Fruitvale
  • Coliseum
  • Coliseum
  • San Leandro
  • San Leandro
  • Bay Fair
  • Bay Fair
  • Hayward
  • Hayward
  • South Hayward
  • South Hayward
  • Union City
  • Union City
  • Fremont
  • Fremont
  • Antioch
  • Main Entrance / Exit
  • Ashby
  • Adeline Street East Entrance / Exit Stairs
  • Adeline Street East Entrance / Exit Elevator
  • Adeline Street West Entrance / Exit
  • Balboa Park
  • A2 John F Foran Fwy (Ramp) Entrance / Exit
  • A1 Geneva Ave Entrance / Exit
  • B1 Geneva Ave Entrance / Exit
  • B3 Geneva Ave Entrance / Exit
  • B2 (Elevator) Geneva Ave Entrance / Exit
  • B4 John F Foran Fwy (Ramp) Entrance / Exit
  • Bay Fair
  • East Entrance / Exit
  • West Entrance / Exit
  • Berryessa / North San Jose
  • Main Entrance / Exit
  • North Entrance / Exit
  • South Entrance / Exit
  • Rockridge
  • Rockridge
  • Orinda
  • Orinda
  • Lafayette
  • Lafayette
  • Walnut Creek
  • Walnut Creek
  • Pleasant Hill / Contra Costa Centre
  • Pleasant Hill / Contra Costa Centre
  • Concord
  • Concord
  • North Concord / Martinez
  • North Concord / Martinez
  • Pittsburg / Bay Point
  • Pittsburg / Bay Point
  • Castro Valley
  • Main Entrance / Exit
  • Civic Center / UN Plaza
  • Elevator Entrance / Exit
  • A3 1150 Market Street - UN Plaza Stairs Entrance / Exit
  • B3 1150 Market Street Entrance / Exit
  • A4 Market Street & 7th Street (NW) Entrance / Exit
  • B4 Market Street & 7th Street (NE) Entrance / Exit
  • A2 Market Street & Hyde Street (SW) Entrance / Exit
  • B2 Market Street & 8th Street (SE) Entrance / Exit
  • Colma
  • West Entrance / Exit to Parking Garage
  • East Entrance / Exit
  • Coliseum
  • 71st Ave Entrance / Exit
  • Elevated Walkway to Amtrak Station, Coliseum Arena Entrance / Exit
  • San Leandro Street Entrance / Exit
  • OAK Connection Entrance / Exit
  • Snell St Entrance / Exit
  • Coliseum/Airport Connector Entrance / Exit
  • Concord
  • West Concourse Entrance / Exit
  • East Concourse Entrance / Exit
  • Daly City
  • A John Daly, Junipero Serra Blvd Entrance / Exit
  • East Parking Lot Entrance / Exit
  • B De Long St, St Charles Ave Entrance / Exit
  • Downtown Berkeley
  • B4 Shattuck Ave & Allston Way (West) Entrance / Exit
  • A2 Shattuck Ave & Allston Way (East) Entrance / Exit
  • B1 Shattuck Ave & Addison Street (West) Entrance / Exit
  • A1 Shattuck Ave & Addison Street (East) Entrance / Exit
  • B3 DBRK Entrance / Exit
  • El Cerrito Del Norte
  • West Concourse Entrance / Exit
  • East Concourse Entrance / Exit
  • Dublin / Pleasanton
  • Main Entrance / Exit
  • Pittsburg Center
  • Pittsburg Center
  • Antioch
  • Antioch
  • Embarcadero
  • B1 Market & Spear Street (SE) Entrance / Exit
  • A1 Market & Drumm Street (NE) Entrance / Exit
  • A2 Market & Davis Street (North) Entrance / Exit
  • B2 Market Street & Main Street (South) Entrance / Exit
  • A3 Market Street & Front Street (NW) Entrance / Exit
  • B3 Market Street & Fremont Street (SW) Entrance / Exit
  • Fremont
  • East Plaza Entrance / Exit
  • West Plaza Entrance / Exit
  • Station Entrance / Exit
  • Fruitvale
  • Main Entrance / Exit
  • Glen Park
  • Main Entrance / Exit
  • Coliseum - OAC
  • Oakland International Airport Station
  • Hayward
  • Main Entrance / Exit
  • 12th Street / Oakland City Center
  • 12th Street / Oakland City Center
  • 12th Street / Oakland City Center
  • 19th Street Oakland
  • 19th Street Oakland
  • 19th Street Oakland
  • MacArthur
  • MacArthur
  • MacArthur
  • MacArthur
  • Castro Valley
  • Castro Valley
  • West Dublin / Pleasanton
  • West Dublin / Pleasanton
  • Dublin / Pleasanton
  • Dublin / Pleasanton
  • Lafayette
  • A Entrance / Exit
  • B Entrance / Exit
  • Lake Merritt
  • B1 NW 8th & Oak St Jack London Sq Entrance / Exit
  • B2 SW 8th St, Laney College Entrance / Exit
  • A2 SE 9th & Oak St Entrance / Exit
  • A1 NE Chinatown Entrance / Exit
  • West Oakland
  • West Oakland
  • Embarcadero
  • Embarcadero
  • Montgomery Street
  • Montgomery Street
  • Powell Street
  • Powell Street
  • Civic Center / UN Plaza
  • Civic Center / UN Plaza
  • 16th Street / Mission
  • 16th Street / Mission
  • 24th Street / Mission
  • 24th Street / Mission
  • Glen Park
  • Glen Park
  • Balboa Park
  • Balboa Park
  • Daly City
  • Daly City
  • Daly City
  • MacArthur
  • Main Entrance / Exit
  • Millbrae
  • Main Entrance / Exit
  • Milpitas
  • West Station Entrance / Exit
  • East Station Entrance / Exit
  • Montgomery Street
  • A1 Market & Post Street (NW) Entrance / Exit
  • B1 598 Market St (SW) Entrance / Exit
  • A2 Market & Montgomery Street (NE) Entrance / Exit
  • B2 Market & 2nd Street (South) Entrance / Exit
  • A3 Sutter Street Entrance / Exit
  • A4 Sansome Street Entrance / Exit
  • B3 575 Market St (SE) Entrance / Exit
  • North Berkeley
  • North Entrance / Exit
  • South Entrance / Exit
  • North Concord / Martinez
  • Main Entrance / Exit
  • Oakland International Airport
  • Main Entrance / Exit
  • Orinda
  • Main Entrance / Exit
  • Pittsburg Center
  • Main Entrance / Exit
  • Pleasant Hill / Contra Costa Centre
  • Main Entrance / Exit
  • Pittsburg / Bay Point
  • Main Entrance / Exit
  • El Cerrito Plaza
  • West Concourse Central Entrance / Exit
  • East Concourse Central Entrance / Exit
  • South Concourse Fairmont Entrance / Exit
  • Powell Street
  • A4 Market Street & 4th Street (NE) Entrance / Exit
  • B4 Market Street & 4th Street (SE) Entrance / Exit
  • A3 Stockton Street Entrance / Exit
  • A2 Market Street & Ellis Street Entrance / Exit
  • B3 Market Street & 4th Street (South) Entrance / Exit
  • B2 Market Street & 5th Street (NE) Entrance / Exit
  • A1 899 Market St Entrance / Exit
  • B1 Market Street & 5th Street Entrance / Exit
  • Ashby
  • Ashby
  • Downtown Berkeley
  • Downtown Berkeley
  • North Berkeley
  • North Berkeley
  • El Cerrito Plaza
  • El Cerrito Plaza
  • El Cerrito Del Norte
  • El Cerrito Del Norte
  • Richmond
  • Richmond
  • Richmond
  • B 19th Street / Civic Center Entrance / Exit
  • A Marina Way / 16th St Entrance / Exit
  • Rockridge
  • West Concourse Entrance / Exit
  • Main (South) Entrance / Exit
  • Warm Springs / South Fremont
  • Warm Springs / South Fremont
  • Milpitas
  • Milpitas
  • Berryessa / North San Jose
  • and 37 more (see the full list on the map or in the GeoJSON)

Over time

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

2026-07-25: 63.72026-07-30: 64.22026-07-31: 63.82026-08-01: 63.5
Show the numbers
CheckScoreChange
2026-07-2563.7 first check
2026-07-3064.2 up 0.5
2026-07-3163.8 down 0.4
2026-08-0163.5 down 0.3

What changed since your last check

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

What changed over time

On 2026-07-25 this feed started at grade D. On 2026-07-31 feed entered the expiry window (30 days of service left). As of 2026-08-01 it holds grade D.

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

  • 2026-07-31 Feed entered the expiry window (30 days of service left).

Everything we checked

18 findings, ordered by severity.

Show every finding
  • Error2 instances

    A file is missing a column that GTFS requires.

    Apps may reject the whole file, so riders could lose the affected routes or stops.

    Fix: Add the required column named in the finding to the flagged file. (Often an export setting; ask your vendor if it recurs.)

    Finding code: missing_required_column · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning2514 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

  • Warning287 instances

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

  • Warning132 instances

    Same name and description for stop (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'same_name_and_description_for_stop' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Finding code: same_name_and_description_for_stop · See MobilityData GTFS Validator rules

  • Warning2 instances

    Some stops exist in the feed but no trip ever stops at them.

    Riders may walk to a stop where no transit vehicle is scheduled to arrive.

    Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)

    Finding code: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning2 instances

    The feed contains route shapes no trip uses.

    Harmless to riders, but it bloats the feed and suggests stale export data.

    Fix: Turn on 'remove unused shapes' (or the like) in your export tool. (One setting.)

    Finding code: unused_shape · Read the fix guide · See MobilityData GTFS Validator rules

  • 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

  • Warning1 instance

    Some stops sit far from the route line they belong to.

    Trip planners may draw the transit vehicle route through the wrong path or point riders to the wrong boarding location.

    Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)

    Finding code: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules

  • 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

  • Warning1 instance

    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.

    Fix: Re-export with a validity window that reaches at least 60 days out. (One export setting.)

    Finding code: scorecard_feed_expiring_soon · Read the fix guide · See GTFS Best Practices

  • Warning1 instance

    This feed models stations or entrances but has no pathways.txt.

    Trip planners can't guide riders through the station, and there is no step-free route information for wheelchair users.

    Fix: Add pathways.txt connecting entrances, platforms, and any elevators, with a level for each. (Worth it for multi-level or large stations; flat stops don't need it.)

    Finding code: scorecard_station_no_pathways · Read the fix guide · See GTFS Schedule reference

  • Info24 instances

    Some trip headsigns name a stop along the way, not the final destination.

    The sign should tell riders where the transit vehicle ends up, so a midpoint name can send them the wrong way.

    Fix: Set trip_headsign to the trip's last stop or its overall destination. (Usually a bulk edit in your scheduling software.)

    Finding code: trip_headsign_matches_intermediate_stop · See MobilityData GTFS Validator rules

  • Info9 instances

    Some service dates fall outside the date window set in feed_info.txt.

    feed_info.txt should span every day your service runs, so apps know when the data applies.

    Fix: Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside. (Two fields in feed_info.txt, or one export setting.)

    Finding code: service_window_outside_feed_period · Read the fix guide · See MobilityData GTFS Validator rules

  • Info5 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

  • Info2 instances

    Some files contain columns that are not part of the GTFS spec.

    Harmless to riders, but apps ignore these columns and they can hide typos in real column names.

    Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)

    Finding code: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules

  • Info1 instance

    Feed valid beyond total service window (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'feed_valid_beyond_total_service_window' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Finding code: feed_valid_beyond_total_service_window · See MobilityData GTFS Validator rules

  • Info1 instance

    Future calendar (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'future_calendar' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Finding code: future_calendar · See MobilityData GTFS Validator rules

  • 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

NTD GTFS 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 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 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. 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 BART to NTD ID 90003, and keep the feed value stable. Do not change it solely to make the two values equal.
shapes.txt covers your trips Ready
All 2689 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. 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.

  • 2 of 105 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.

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

Live predictions vs schedule

Arrival predictions ran right on the schedule, and stayed within 54s nine times in ten. They were on time (about a minute early to five late) 99.4% 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 161 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

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 100% of trips.

  • Meets shapes.txt with a shape for every trip

    All 2689 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 48 / 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 68 / 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.

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