IR17 2838 Olten – Bern

View line IR17

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

✓ Today’s run finished

Today, last fix heading to Bern at 21:55 No data

  1. Olten21:06
  2. Langenthal21:17
  3. Herzogenbuchsee21:23
  4. Wynigen21:30
  5. Burgdorf21:37
  6. Bern21:53

Next service: tomorrow 21:06 from Olten · Fri 13 Nov

Next departure 21:06 tomorrow · Olten
On-time · 30 days
89%
24/27 runs under 3 min
RT coverage: 27 full · 0 partial · 3 no data
On-time · 90 days
90%
36/40 runs under 3 min
RT coverage: 40 full · 0 partial · 3 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: +2 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

  • Mon 5 Oct Max en route +7 min · last fix heading to Bern +7 min
  • Sat 7 Nov Max en route +5 min · last fix heading to Bern +5 min
  • Fri 30 Oct Max en route +4 min · last fix heading to Bern +4 min
  • Sun 25 Oct Max en route +4 min · last fix heading to Bern +4 min

Distribution · 90 days

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

  • Early 25% · 10
  • On time 65% · 26
  • 3–10 min 10% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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