IR16 2190 Zürich HB – Olten

View line IR16

Zürich HB 22:06 → Olten 22:56 Daily 0 h 50 min · 5 stops SBB CFF FFS

Running now · updated 22:59

Between Aarau and Olten +5 min

Estimated arrival at Olten 23:01 22:56 · 83 km/h

  1. Zürich HB22:06
  2. Baden22:21
  3. Brugg AG22:30
  4. Aarau22:45
  5. Olten22:56

Today it is running worse than usual: typical arrival delay is +1 min; 82% of the last 28 runs arrived on time.

On-time · 30 days
82%
23/28 runs under 3 min
RT coverage: 28 full · 0 partial · 1 no data
On-time · 90 days
89%
40/45 runs under 3 min
RT coverage: 45 full · 0 partial · 1 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

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

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

Worst days

  • Tue 20 Oct Max en route +5 min · last fix heading to Baden +5 min
  • Tue 10 Nov Max en route +4 min · last fix heading to Olten +4 min
  • Mon 2 Nov Max en route +3 min · last fix heading to Olten +3 min
  • Sun 25 Oct Max en route +3 min · last fix heading to Olten +3 min
  • Fri 16 Oct Max en route +3 min · last fix heading to Olten +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 40
  • 3–10 min 11% · 5
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 89% M n=9
  • 67% T n=6
  • 100% W n=5
  • 100% T n=6
  • 83% F n=6
  • 100% S n=7
  • 83% S n=6

Stops and timetable

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

Last 90 days, 45 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
22:06on time on timePassed
22:21 / 22:22≈ on time ≈ +1 minPassed
22:30 / 22:32≈ on time ≈ +1 minPassed
22:45 / 22:46≈ on time ≈ +2 minPassed
22:56+1 min +3 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 11 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 NovOlten 22:54+4 min+4 min
Mon 9 NovOlten 22:58+1 min—
Sun 8 NovOlten 22:58+1 min—
Sat 7 NovOlten 22:58+1 min+1 min
Fri 6 NovOlten 22:580 min—
Thu 5 NovOlten 22:58+2 min+2 min
Wed 4 NovOlten 22:570 min—
Tue 3 NovOlten 22:59+3 min+3 min
Mon 2 NovOlten 22:59+3 min+3 min
Sun 1 NovOlten 22:59+3 min+3 min
Sat 31 OctOlten 22:570 min—
Fri 30 OctOlten 22:570 min—
Thu 29 OctOlten 22:570 min—
Wed 28 OctOlten 22:570 min—
Tue 27 OctOlten 22:570 min—
Mon 26 OctOlten 22:58+1 min—
Sun 25 OctOlten 23:00+3 min+3 min
Sat 24 OctOlten 22:570 min—
Thu 22 OctOlten 22:580 min—
Wed 21 OctOlten 22:59+2 min+2 min
Tue 20 OctBaden 22:25+5 min+5 min
Mon 19 OctOlten 22:57+1 min—
Sun 18 OctOlten 22:57No data—
Sat 17 OctOlten 22:59+2 min+2 min
Fri 16 OctOlten 23:01+3 min+3 min
Thu 15 OctOlten 22:570 min—
Wed 14 OctOlten 22:59+1 min+1 min
Tue 13 OctOlten 23:00+3 min+3 min
Mon 12 OctOlten 22:560 min—
Sun 11 OctOlten 22:58+1 min+1 min