IR17 2834 Olten – Bern

View line IR17

Olten 19:06 → Bern 19:53 Daily 0 h 47 min · 6 stops BLS

It has not run yet today

Last recorded run: Saturday 7 November −1 min

Next service: today 19:06 from Olten · Sun 8 Nov

Next departure 19:06 today · Olten
On-time · 30 days
100%
28/28 runs under 3 min
RT coverage: 28 full · 0 partial · 1 no data
On-time · 90 days
100%
37/37 runs under 3 min
RT coverage: 37 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: −1 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

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

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

Distribution · 90 days

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

  • Early 24% · 9
  • On time 76% · 28
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=6
  • 100% W n=5
  • 100% T n=5
  • 100% F n=5
  • 100% S n=5
  • 100% S n=5

Stops and timetable

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

Last 90 days, 37 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 10
19:06on time on time
19:17 / 19:18≈ on time ≈ on time
19:23 / 19:24≈ on time ≈ on time
19:30 / 19:31≈ on time ≈ on time
19:37 / 19:38≈ on time ≈ on time
19:53on time +1 min

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
Sat 7 NovBern 19:53−1 min—
Fri 6 NovBern 19:540 min—
Thu 5 NovBern 19:53−1 min—
Wed 4 NovBern 19:540 min—
Tue 3 NovBern 19:53−1 min—
Mon 2 NovBern 19:53−1 min—
Sun 1 NovBern 19:53−1 min—
Sat 31 OctBern 19:540 min—
Fri 30 OctBern 19:52−2 min—
Thu 29 OctBern 19:53−1 min—
Wed 28 OctBern 19:55+1 min—
Tue 27 OctBern 19:53−1 min—
Mon 26 OctBern 19:550 min—
Sun 25 OctBern 19:53−1 min—
Sat 24 OctBern 19:540 min—
Fri 23 OctBern 19:53−1 min—
Thu 22 OctBern 19:54−1 min—
Wed 21 OctBern 19:540 min—
Tue 20 OctBern 19:540 min—
Mon 19 OctBern 19:540 min—
Sun 18 OctBern 19:52−1 min—
Sat 17 OctBern 19:53−1 min—
Fri 16 OctBern 19:56+1 min+1 min
Thu 15 OctBern 19:540 min—
Wed 14 OctBern 19:54−1 min—
Tue 13 OctBern 19:55+1 min—
Mon 12 OctBern 19:52−1 min—
Sun 11 OctBern 19:54No data—
Sat 10 OctBern 19:53−1 min—
Fri 9 OctBern 19:540 min—