IR17 2811 Bern → Olten

View line IR17

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

IR17 2811 Bern–Olten: final delay under 3 min on 25 of its 29 runs with data in the last 30 days (86%). Median final delay: +1 min. TrainsRadar data as of 22 Nov 2026, 07:36 (GMT+1).

Running now · updated 07:35

Position estimated from the timetable

Between Herzogenbuchsee and Langenthal No data

Estimated arrival at Olten 07:54 · 75 km/h

  1. Bern07:07
  2. Burgdorf07:20
  3. Wynigen07:26
  4. Herzogenbuchsee07:33
  5. Langenthal07:40
  6. Olten07:54
On-time · 30 days
86%
25/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
90%
44/49 runs under 3 min
RT coverage: 49 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 17 Nov Max en route +6 min · last fix heading to Olten +6 min
  • Thu 15 Oct Max en route +4 min · last fix heading to Olten +4 min
  • Thu 12 Nov Max en route +3 min · last fix heading to Olten +3 min
  • Mon 16 Nov Max en route +3 min · last fix heading to Olten +3 min
  • Tue 27 Oct Max en route +3 min · last fix heading to Olten +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 44
  • 3–10 min 10% · 5
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 86% M n=7
  • 71% T n=7
  • 100% W n=7
  • 71% T n=7
  • 100% F n=7
  • 100% S n=7
  • 100% S n=7

Stops and timetable

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

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