IR17 2812 Olten – Bern

View line IR17

Olten 08:06 → Bern 08:53 Daily 0 h 47 min · 6 stops BLS

✓ Today’s run finished

Today it reached Bern at 08:55 +2 min

  1. Olten08:06
  2. Langenthal08:17
  3. Herzogenbuchsee08:23
  4. Wynigen08:30
  5. Burgdorf08:37
  6. Bern08:53

Next service: tomorrow 08:06 from Olten · Sat 7 Nov

Next departure 08:06 tomorrow · Olten
On-time · 30 days
83%
24/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
82%
28/34 runs under 3 min
RT coverage: 34 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Bern, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sun 4 Oct Max en route +21 min · last fix heading to Bern +21 min
  • Mon 12 Oct Max en route +7 min · last fix heading to Bern +7 min
  • Wed 28 Oct Max en route +4 min · last fix heading to Bern +4 min
  • Tue 3 Nov Max en route +3 min · last fix heading to Bern +3 min
  • Wed 21 Oct Max en route +3 min · last fix heading to Bern +3 min

Distribution · 90 days

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

  • Early 12% · 4
  • On time 71% · 24
  • 3–10 min 15% · 5
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 80% T n=5
  • 40% W n=5
  • 100% T n=5
  • 100% F n=6
  • 100% S n=4
  • 75% S n=4

Stops and timetable

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

Last 90 days, 34 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
08:06on time on time
08:17 / 08:18≈ on time ≈ +1 min
08:23 / 08:24≈ on time ≈ +1 min
08:30 / 08:31≈ on time ≈ +2 min
08:37 / 08:38≈ on time ≈ +2 min
08:53on time +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
Fri 6 NovBern 08:54+2 min+2 min
Thu 5 NovBern 08:54+1 min—
Wed 4 NovBern 08:540 min—
Tue 3 NovBern 08:58+3 min+3 min
Mon 2 NovBern 08:54−1 min—
Sun 1 NovBern 08:53−1 min—
Sat 31 OctBern 08:53−1 min—
Fri 30 OctBern 08:53−1 min+6 min
Thu 29 OctBern 08:540 min—
Wed 28 OctBern 08:58+4 min+4 min
Tue 27 OctBern 08:56+1 min+1 min
Mon 26 OctBern 08:55+1 min—
Sun 25 OctBern 08:53−1 min—
Sat 24 OctBern 08:530 min—
Fri 23 OctBern 08:540 min—
Thu 22 OctBern 08:56+2 min+2 min
Wed 21 OctBern 08:57+3 min+3 min
Tue 20 OctBern 08:550 min—
Mon 19 OctBern 08:540 min—
Sun 18 OctBern 08:54No data—
Sat 17 OctBern 08:540 min—
Fri 16 OctBern 08:540 min—
Thu 15 OctBern 08:54−1 min—
Wed 14 OctBern 08:57+3 min+3 min
Tue 13 OctBern 08:540 min—
Mon 12 OctBern 09:01+7 min+7 min
Sun 11 OctBern 08:52−2 min—
Sat 10 OctBern 08:56+2 min+2 min
Fri 9 OctBern 08:540 min—
Thu 8 OctBern 08:54−1 min—