Capitol Corridor 532 Oakland – Sacramento

View line Capitol Corridor

Oakland 15:58 → Sacramento 18:00 Mon, Tue, Wed, Thu, Fri 2 h 02 min · 9 stops Amtrak

Running now · updated 18:03

Between Davis and Sacramento +6 min

Estimated arrival at Sacramento 18:06 18:00 · 122 km/h

  1. Oakland15:58
  2. Emeryville16:06
  3. Richmond16:18
  4. Martinez16:46
  5. Suisun-Fairfield17:05
  6. Davis17:34
  7. Sacramento18:00

Today it is running worse than usual: typical arrival delay is 0 min; 71% of the last 21 runs arrived on time.

On-time · 30 days
71%
15/21 runs under 3 min
RT coverage: 21 full · 0 partial · 0 no data
On-time · 90 days
75%
18/24 runs under 3 min
RT coverage: 24 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+10min
9 in 10 runs arrive with less than this
30 days: +10 min

Last 30 days

Arrival delay at Sacramento, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Wed 4 Nov Max en route +44 min · last fix heading to Sacramento +39 min
  • Mon 26 Oct Max en route +33 min · last fix heading to Sacramento +17 min
  • Fri 16 Oct Max en route +27 min · last fix heading to Sacramento +10 min
  • Wed 21 Oct Max en route +25 min · last fix heading to Sacramento +9 min
  • Fri 6 Nov Max en route +21 min · last fix heading to Sacramento +6 min

Distribution · 90 days

24 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 0% · 0
  • On time 75% · 18
  • 3–10 min 13% · 3
  • 10–30 min 8% · 2
  • 30+ min 4% · 1

On-time by weekday

  • 80% M n=5
  • 80% T n=5
  • 60% W n=5
  • 100% T n=4
  • 60% F n=5
  • — S n=0
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (9 stops).

Last 90 days, 24 runs. At intermediate stops it is an estimate from the delay at origin and destination. Delays over 2 h count as “> 2 h”: our data does not measure them exactly.

StopSched.Usually 9 days in 10Today
15:58+2 min +4 minPassed
16:06 / 16:08≈ +2 min ≈ +4 minPassed
16:11 / 16:12≈ +2 min ≈ +5 minPassed
16:18 / 16:20≈ +2 min ≈ +6 minPassed
16:46 / 16:47≈ +1 min ≈ +6 minPassed
17:05 / 17:06≈ +1 min ≈ +5 minPassed
17:11 / 17:12≈ +1 min ≈ +6 minPassed
17:34 / 17:36≈ on time ≈ +8 minPassed
18:00on time +10 minNext

Each run is closed into train_runs (country, train number, service day) from the live positions. Final delay = last delay seen. Partial coverage: the feed stopped before the final stop (last value used, hatched in the chart). No data: a run without any valid delay; counts as neither on time nor late. Data collected since 10 July 2026.

Will I make my connection?

Pick where you get off and how many minutes you have until your next train. We work it out from what this train did over the last 90 days.

Include the time to change platforms. It is an estimate from past data, not a guarantee. Days more than 2 h late count as a missed connection.

Recent runs

DateLast stopFinalMax
Fri 6 NovSacramento 17:58+6 min+21 min
Thu 5 NovSacramento 18:090 min+5 min
Wed 4 NovSacramento 18:24+39 min+44 min
Tue 3 NovSacramento 18:23+5 min+20 min
Mon 2 NovSacramento 18:090 min+5 min
Fri 30 OctSacramento 18:180 min+14 min
Wed 28 OctSacramento 18:150 min+12 min
Tue 27 OctSacramento 18:060 min+5 min
Mon 26 OctSacramento 18:57+17 min+33 min
Fri 23 OctSacramento 18:050 min+5 min
Thu 22 OctSacramento 18:170 min+9 min
Wed 21 OctSacramento 18:27+9 min+25 min
Tue 20 OctSacramento 18:120 min+4 min
Mon 19 OctSacramento 18:080 min+6 min
Fri 16 OctSacramento 18:29+10 min+27 min
Thu 15 OctSacramento 18:060 min+3 min
Wed 14 OctSacramento 18:140 min+11 min
Tue 13 OctSacramento 18:070 min+3 min
Mon 12 OctSacramento 18:110 min+5 min
Fri 9 OctSacramento 18:130 min+6 min
Thu 8 OctSacramento 18:110 min+7 min
Wed 7 OctSacramento 18:19+1 min+19 min
Tue 6 OctSacramento 18:070 min+5 min
Mon 5 OctSacramento 18:160 min+11 min