IR17 2825 Bern – Olten

View line IR17

Bern 14:07 → Olten 14:54 Daily 0 h 47 min · 6 stops BLS

Running now · updated 14:43

Position estimated from the timetable

Between Langenthal and Olten No data

Estimated arrival at Olten 14:54 · 88 km/h

  1. Bern14:07
  2. Burgdorf14:20
  3. Wynigen14:26
  4. Herzogenbuchsee14:33
  5. Langenthal14:39
  6. Olten14:54
On-time · 30 days
96%
26/27 runs under 3 min
RT coverage: 27 full · 0 partial · 3 no data
On-time · 90 days
95%
42/44 runs under 3 min
RT coverage: 44 full · 0 partial · 3 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Sat 14 Nov Max en route +8 min · last fix heading to Olten +8 min
  • Sat 10 Oct Max en route +5 min · last fix heading to Olten +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 42
  • 3–10 min 5% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 44 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
14:07on time +1 minPassed
14:20 / 14:21≈ on time ≈ +1 minPassed
14:26 / 14:27≈ on time ≈ +1 minPassed
14:33 / 14:34≈ on time ≈ +1 minPassed
14:39 / 14:41≈ +1 min ≈ +2 minPassed
14:54+1 min +2 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
Wed 18 NovLangenthal 14:39Partial coverageNo data—
Tue 17 NovOlten 14:57+2 min+2 min
Mon 16 NovOlten 14:540 min—
Sun 15 NovOlten 14:540 min—
Sat 14 NovOlten 15:03+8 min+8 min
Fri 13 NovOlten 14:540 min—
Thu 12 NovOlten 14:57+2 min+2 min
Wed 11 NovOlten 14:540 min—
Tue 10 NovOlten 14:540 min—
Mon 9 NovOlten 14:54No data—
Sun 8 NovOlten 14:540 min—
Sat 7 NovOlten 14:540 min—
Fri 6 NovOlten 14:57+2 min+2 min
Thu 5 NovOlten 14:54No data—
Wed 4 NovOlten 14:58+2 min+2 min
Tue 3 NovOlten 14:58+2 min+2 min
Mon 2 NovOlten 14:57+1 min+1 min
Sun 1 NovOlten 14:550 min—
Sat 31 OctOlten 14:56+1 min+1 min
Fri 30 OctOlten 14:56+1 min—
Thu 29 OctOlten 14:560 min—
Wed 28 OctOlten 14:550 min—
Tue 27 OctOlten 14:56+1 min—
Mon 26 OctOlten 14:56+1 min—
Sun 25 OctOlten 14:56+1 min+1 min
Sat 24 OctOlten 14:57+2 min+2 min
Fri 23 OctOlten 14:55+1 min—
Thu 22 OctOlten 14:56+1 min—
Wed 21 OctOlten 14:56+1 min—
Tue 20 OctOlten 14:58+3 min+3 min