IR17 2837 Bern – Olten

View line IR17

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

✓ Today’s run finished

Today it reached Olten at 20:54 −1 min

  1. Bern20:07
  2. Burgdorf20:20
  3. Wynigen20:26
  4. Herzogenbuchsee20:33
  5. Langenthal20:39
  6. Olten20:54

Next service: tomorrow 20:07 from Bern · Sun 8 Nov

Next departure 20:07 tomorrow · Bern
On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
97%
34/35 runs under 3 min
RT coverage: 35 full · 0 partial · 0 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

  • Mon 5 Oct Max en route +15 min · last fix heading to Olten +15 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 34
  • 3–10 min 0% · 0
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 100% T n=5
  • 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, 35 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
20:07on time on time
20:20 / 20:21≈ on time ≈ +1 min
20:26 / 20:27≈ on time ≈ +1 min
20:33 / 20:34≈ +1 min ≈ +1 min
20:39 / 20:41≈ +1 min ≈ +2 min
20:54+1 min +2 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 NovOlten 20:54−1 min—
Fri 6 NovOlten 20:57+2 min+3 min
Thu 5 NovOlten 20:540 min—
Wed 4 NovOlten 20:58+3 min+3 min
Tue 3 NovOlten 20:54+1 min—
Mon 2 NovOlten 20:58+2 min+2 min
Sun 1 NovOlten 20:540 min—
Sat 31 OctOlten 20:58+3 min+3 min
Fri 30 OctOlten 20:56+1 min—
Thu 29 OctOlten 20:550 min—
Wed 28 OctOlten 20:57+2 min+2 min
Tue 27 OctOlten 20:56+1 min—
Mon 26 OctOlten 20:550 min—
Sun 25 OctOlten 20:550 min—
Sat 24 OctOlten 20:56+1 min+1 min
Fri 23 OctOlten 20:56+1 min+1 min
Thu 22 OctOlten 20:56+1 min—
Wed 21 OctOlten 20:55+1 min—
Tue 20 OctOlten 20:56+1 min—
Mon 19 OctOlten 20:550 min—
Sun 18 OctOlten 20:56+1 min+1 min
Sat 17 OctOlten 20:56+2 min+2 min
Fri 16 OctOlten 20:56+1 min—
Thu 15 OctOlten 20:56+1 min+1 min
Wed 14 OctOlten 20:56+1 min—
Tue 13 OctOlten 20:550 min—
Mon 12 OctOlten 20:55+1 min—
Sun 11 OctOlten 20:56+1 min+1 min
Sat 10 OctOlten 20:56+1 min+1 min
Fri 9 OctOlten 20:56+1 min—