IR17 2847 Bern – Olten

View line IR17

Bern 00:07 → Olten 00:55 Daily 0 h 48 min · 6 stops BLS

✓ Today’s run finished

Today it reached Olten at 00:59 +4 min

  1. Bern00:07
  2. Burgdorf00:22
  3. Wynigen00:28
  4. Herzogenbuchsee00:35
  5. Langenthal00:41
  6. Olten00:55

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

Next departure 00:07 tomorrow · Bern
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
97%
71/73 runs under 3 min
RT coverage: 73 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +1 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 7 Nov Max en route +4 min · last fix heading to Olten +4 min
  • Fri 14 Aug Max en route +5 min · last fix heading to Olten +3 min

Distribution · 90 days

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

  • Early 14% · 10
  • On time 84% · 61
  • 3–10 min 3% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=12
  • 100% T n=11
  • 100% W n=10
  • 100% T n=10
  • 90% F n=10
  • 91% S n=11
  • 100% S n=9

Stops and timetable

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

Last 90 days, 73 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
00:07on time on time
00:22 / 00:23≈ on time ≈ +1 min
00:28 / 00:29≈ on time ≈ +1 min
00:35 / 00:36≈ on time ≈ +1 min
00:41 / 00:42≈ on time ≈ +1 min
00:55on time +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 00:59+4 min+4 min
Fri 6 NovOlten 00:54−1 min—
Thu 5 NovOlten 00:540 min—
Wed 4 NovOlten 01:020 min—
Tue 3 NovOlten 00:54−1 min—
Mon 2 NovOlten 01:03+1 min—
Sun 1 NovOlten 00:54−2 min—
Sat 31 OctOlten 00:55−1 min—
Fri 30 OctOlten 00:58+2 min+2 min
Thu 29 OctOlten 00:57+1 min—
Wed 28 OctOlten 00:57+1 min+2 min
Tue 27 OctOlten 00:56−1 min—
Mon 26 OctOlten 00:55−1 min—
Sun 25 OctOlten 00:55−1 min—
Sat 24 OctOlten 00:58+2 min+2 min
Fri 23 OctOlten 00:54−2 min+5 min
Thu 22 OctOlten 00:54−2 min—
Wed 21 OctOlten 00:560 min—
Tue 20 OctOlten 00:550 min+1 min
Mon 19 OctOlten 00:55−1 min—
Sun 18 OctOlten 00:560 min—
Sat 17 OctOlten 00:56−1 min—
Fri 16 OctOlten 00:560 min+2 min
Thu 15 OctOlten 00:57+1 min+1 min
Wed 14 OctOlten 00:560 min—
Tue 13 OctOlten 00:560 min—
Mon 12 OctOlten 00:55−1 min—
Sun 11 OctOlten 00:570 min—
Sat 10 OctOlten 00:56−1 min—
Fri 9 OctOlten 00:55−1 min—