SF

Alameda County / Bus

Capitol Corridor Joint Powers Authority (Capitol Corridor) SF schedule and full timetable

Shuttle_SF · America/Los_Angeles

Selected branch: SF Salesforce Plaza · 2 stops. Service day: Thursday, October 29, 2026.

Capitol Corridor Joint Powers Authority (Capitol Corridor) SF full stop-by-trip timetable

All stops on the selected branch, October 29, 2026. 15 fixed scheduled trips; showing 1–15. Frequency service is listed in the boarding schedule below. A dash means the agency supplies no time.

Stop / tripTrip 1Trip 2Trip 3Trip 4Trip 5Trip 6Trip 7Trip 8Trip 9Trip 10Trip 11Trip 12Trip 13Trip 14Trip 15
Emeryville6:05 AM7:05 AM7:50 AM8:25 AM9:25 AM10:35 AM11:40 AM12:35 PM1:35 PM2:40 PM4:05 PM5:40 PM6:45 PM8:50 PM10:50 PM
San Francisco - Transbay Terminal6:35 AM7:40 AM8:30 AM9:00 AM10:00 AM11:05 AM12:10 PM1:05 PM2:05 PM3:10 PM4:35 PM6:10 PM7:15 PM9:20 PM11:20 PM

Every departure from Emeryville

For the selected service day and branch. After-midnight times retain their service-day association; “+1 day” means the following calendar day.

Departure / windowDestinationBoarding notes
6:05 AMSF Salesforce PlazaScheduled
7:05 AMSF Salesforce PlazaScheduled
7:50 AMSF Salesforce PlazaScheduled
8:25 AMSF Salesforce PlazaScheduled
9:25 AMSF Salesforce PlazaScheduled
10:35 AMSF Salesforce PlazaScheduled
11:40 AMSF Salesforce PlazaScheduled
12:35 PMSF Salesforce PlazaScheduled
1:35 PMSF Salesforce PlazaScheduled
2:40 PMSF Salesforce PlazaScheduled
4:05 PMSF Salesforce PlazaScheduled
5:40 PMSF Salesforce PlazaScheduled
6:45 PMSF Salesforce PlazaScheduled
8:50 PMSF Salesforce PlazaScheduled
10:50 PMSF Salesforce PlazaScheduled

More Capitol Corridor Joint Powers Authority (Capitol Corridor) travel information

✓
Published Capitol Corridor Joint Powers Authority (Capitol Corridor) schedule

Imported Oct 24, 2026 · 04:27 UTC · Service dates 2026-03-02 through 2027-01-03. See data status

Schedule data published by Capitol Corridor Joint Powers Authority (Capitol Corridor). Feed discovery and cached source archives from MobilityData. Source details ↗