PLEASE NOTE:
We're supporting this ETA feed only as a legacy service. We will not be making changes to it.
All new development is focused on the Real BART API and the GTFS-Real Time Feed.
For quick and easy real time ETAs, use our simple-to-parse XML feed and crank out your killer app with the same real time data we use on the BART website, hot off the griddle from BART Central. Here's what you need to know:
- Get a validation key
Psyche: we don't do that here. We never make you jump through hoops to use BART open data. We just ask that you follow our simple License Agreement, give our customers good information and not hog community resources. If that doesn't work, we can manage usage with keys and write more terms and conditions. But who wants that? - Keep your work up to date
This feed will change, and when it does we'll try to give you plenty of notice through the RSS feed and the opt-in email list and the BART Developers Google Group. - Don't use the BART logo
Only we get to use official BART trademarks and copyrighted works to let customers know they're getting info directly from BART versus one of the tons of other places that use BART open data. - Don't forget about us
Give us a shout out or a link back, then submit your app to the App Center.
About the Feed
The BART Real Time ETA Feed is an XML data file with a root element that encompasses elements holding the station name, the station abbreviation, the date and time and a series of ETA elements. Each ETA element contains a destination and an estimate showing up to the next three trains arriving at the specified station with the given destination. The file is updated every 60 seconds.
Station Abbreviations
| Abbr | Station Name |
| 12th | 12th St. Oakland City Center |
| 16th | 16th St. Mission (SF) |
| 19th | 19th St. Oakland |
| 24th | 24th St. Mission (SF) |
| ashb | Ashby (Berkeley) |
| balb | Balboa Park (SF) |
| bayf | Bay Fair (San Leandro) |
| cast | Castro Valley |
| civc | Civic Center (SF) |
| cols | Coliseum/Oakland Airport |
| colm | Colma |
| conc | Concord |
| daly | Daly City |
| dbrk | Downtown Berkeley |
| dubl | Dublin/Pleasanton |
| deln | El Cerrito del Norte |
| plza | El Cerrito Plaza |
| embr | Embarcadero (SF) |
| frmt | Fremont |
| ftvl | Fruitvale (Oakland) |
| glen | Glen Park (SF) |
| hayw | Hayward |
| lafy | Lafayette |
| lake | Lake Merritt (Oakland) |
| mcar | MacArthur (Oakland) |
| mlbr | Millbrae |
| mont | Montgomery St. (SF) |
| nbrk | North Berkeley |
| ncon | North Concord/Martinez |
| orin | Orinda |
| pitt | Pittsburg/Bay Point |
| phil | Pleasant Hill |
| powl | Powell St. (SF) |
| rich | Richmond |
| rock | Rockridge (Oakland) |
| sbrn | San Bruno |
| sfia | San Francisco Int'l Airport |
| sanl | San Leandro |
| shay | South Hayward |
| ssan | South San Francisco |
| ucty | Union City |
| wcrk | Walnut Creek |
| woak | West Oakland |
Frequently Asked Questions
Why are you doing this?
We want to foster innovative applications, reach a broader audience and encourage more people to choose BART.
Will you help me troubleshoot?
If we help you, it's only fair that we help everyone else, too. We simply don't have the resources for that. Let us know about any issues or enhancements you'd like to see, but unfortunately we aren't able to provide technical support for your development efforts.
What are your plans for future development?
All of our developer services are created on what we call "BART one percent time." So within that context we're doing our best to fix problems, add new features and keep it all going. Drop us a line with your suggestions and learn about changes through the RSS feed, the opt-in email list or the BART Developers Google Group.
