11705 536 Oakland – Sacramento

View line 11705

Oakland 17:58 → Sacramento 20:00 Mon, Tue, Wed, Thu, Fri 2 h 02 min · 9 stops MARC

Running now · updated 18:48

Heading to Sacramento +11 min

Estimated arrival at Sacramento 20:11 20:00 · 156 km/h

  1. Oakland17:58
  2. Emeryville18:06
  3. Richmond18:18
  4. Martinez18:46
  5. Suisun-Fairfield19:05
  6. Davis19:34
  7. Sacramento20:00

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

On-time · 30 days
91%
20/22 runs under 3 min
RT coverage: 21 full · 1 partial · 0 no data
On-time · 90 days
93%
25/27 runs under 3 min
RT coverage: 26 full · 1 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: 0 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

  • Thu 29 Oct Max en route +37 min · last fix heading to Sacramento +20 min
  • Tue 10 Nov Max en route +11 min · last fix heading to Martinez +11 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 93% · 25
  • 3–10 min 0% · 0
  • 10–30 min 7% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 83% 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.

StopSched.Usually 9 days in 10Today
17:58+2 min +4 min
18:06 / 18:08≈ +2 min ≈ +4 min
18:11 / 18:12≈ +2 min ≈ +4 min
18:18 / 18:20≈ +2 min ≈ +4 min
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:00on 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

DateLast stopFinalMax
Tue 10 NovMartinez 18:44Partial coverage+11 min+11 min
Mon 9 NovSacramento 20:150 min+11 min
Fri 6 NovSacramento 20:360 min+4 min
Thu 5 NovSacramento 20:210 min+15 min
Wed 4 NovSacramento 20:210 min+31 min
Tue 3 NovSacramento 20:080 min+8 min
Mon 2 NovSacramento 20:130 min+9 min
Fri 30 OctSacramento 20:240 min+7 min
Thu 29 OctSacramento 20:39+20 min+37 min
Wed 28 OctSacramento 20:150 min+12 min
Tue 27 OctSacramento 20:090 min+4 min
Mon 26 OctSacramento 20:180 min+3 min
Fri 23 OctSacramento 20:230 min+5 min
Thu 22 OctSacramento 20:110 min+4 min
Wed 21 OctSacramento 20:090 min+5 min
Tue 20 OctSacramento 20:090 min+5 min
Mon 19 OctSacramento 20:260 min+2 min
Fri 16 OctSacramento 20:260 min+9 min
Thu 15 OctSacramento 20:150 min+10 min
Wed 14 OctSacramento 20:080 min+4 min
Tue 13 OctSacramento 20:070 min+5 min
Mon 12 OctSacramento 20:170 min+12 min
Fri 9 OctSacramento 20:250 min+5 min
Thu 8 OctSacramento 20:210 min+3 min
Wed 7 OctSacramento 20:19+2 min+15 min
Tue 6 OctSacramento 20:110 min+3 min
Mon 5 OctSacramento 20:100 min+8 min