IR17 2829 Bern – Olten

View line IR17

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

✓ Today’s run finished

Today it reached Olten at 16:54 0 min

  1. Bern16:07
  2. Burgdorf16:20
  3. Wynigen16:26
  4. Herzogenbuchsee16:33
  5. Langenthal16:39
  6. Olten16:54

Next service: tomorrow 16:07 from Bern · Wed 18 Nov

Next departure 16:07 tomorrow · Bern
On-time · 30 days
93%
27/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
93%
40/43 runs under 3 min
RT coverage: 43 full · 0 partial · 2 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

  • Mon 9 Nov Max en route +4 min · last fix heading to Olten +4 min
  • Sat 24 Oct Max en route +3 min · last fix heading to Olten +3 min
  • Sat 10 Oct Max en route +3 min · last fix heading to Olten +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 40
  • 3–10 min 7% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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