Capitol Corridor 536 Oakland – Sacramento
Alerts for train 536
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line Capitol Corridor.
Running now · updated 18:33
Between Richmond and Martinez +1 min
Estimated arrival at Sacramento 20:01 20:00 · 58 km/h
- Oakland17:58
- Emeryville18:06
- Richmond18:18
- Martinez18:46
- Suisun-Fairfield19:05
- Davis19:34
- Sacramento20:00
Today it is running worse than usual: typical arrival delay is 0 min; 95% of the last 22 runs arrived on time.
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
- Thu 29 Oct Max en route +37 min · last fix heading to Sacramento +20 min
Distribution · 90 days
27 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 96% · 26
- 3–10 min 0% · 0
- 10–30 min 4% · 1
- 30+ min 0% · 0
On-time by weekday
- 100% M n=6
- 100% T n=6
- 100% W n=5
- 80% T n=5
- 100% 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, 27 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.
| Stop | Sched. | Usually | 9 days in 10 | Today |
|---|---|---|---|---|
| 17:58 | +2 min | +4 min | Passed | |
| 18:06 / 18:08 | ≈ +2 min | ≈ +4 min | Passed | |
| 18:11 / 18:12 | ≈ +2 min | ≈ +4 min | Passed | |
| 18:18 / 18:20 | ≈ +2 min | ≈ +4 min | Passed | |
| 18:46 / 18:47 | ≈ +1 min | ≈ +3 min | ||
| 19:05 / 19:06 | ≈ +1 min | ≈ +2 min | ||
| 19:11 / 19:12 | ≈ +1 min | ≈ +2 min | ||
| 19:34 / 19:36 | ≈ on time | ≈ +1 min | ||
| 20:00 | on time | on time |
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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Tue 10 Nov | Martinez 18:33Partial coverage | +1 min | +10 min |
| Mon 9 Nov | Sacramento 20:15 | 0 min | +11 min |
| Fri 6 Nov | Sacramento 20:36 | 0 min | +4 min |
| Thu 5 Nov | Sacramento 20:21 | 0 min | +15 min |
| Wed 4 Nov | Sacramento 20:21 | 0 min | +31 min |
| Tue 3 Nov | Sacramento 20:08 | 0 min | +8 min |
| Mon 2 Nov | Sacramento 20:13 | 0 min | +9 min |
| Fri 30 Oct | Sacramento 20:24 | 0 min | +7 min |
| Thu 29 Oct | Sacramento 20:39 | +20 min | +37 min |
| Wed 28 Oct | Sacramento 20:15 | 0 min | +12 min |
| Tue 27 Oct | Sacramento 20:09 | 0 min | +4 min |
| Mon 26 Oct | Sacramento 20:18 | 0 min | +3 min |
| Fri 23 Oct | Sacramento 20:23 | 0 min | +5 min |
| Thu 22 Oct | Sacramento 20:11 | 0 min | +4 min |
| Wed 21 Oct | Sacramento 20:09 | 0 min | +5 min |
| Tue 20 Oct | Sacramento 20:09 | 0 min | +5 min |
| Mon 19 Oct | Sacramento 20:26 | 0 min | +2 min |
| Fri 16 Oct | Sacramento 20:26 | 0 min | +9 min |
| Thu 15 Oct | Sacramento 20:15 | 0 min | +10 min |
| Wed 14 Oct | Sacramento 20:08 | 0 min | +4 min |
| Tue 13 Oct | Sacramento 20:07 | 0 min | +5 min |
| Mon 12 Oct | Sacramento 20:17 | 0 min | +12 min |
| Fri 9 Oct | Sacramento 20:25 | 0 min | +5 min |
| Thu 8 Oct | Sacramento 20:21 | 0 min | +3 min |
| Wed 7 Oct | Sacramento 20:19 | +2 min | +15 min |
| Tue 6 Oct | Sacramento 20:11 | 0 min | +3 min |
| Mon 5 Oct | Sacramento 20:10 | 0 min | +8 min |