IR17 2826 Olten – Bern

View line IR17

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

✓ Today’s run finished

Today it reached Bern at 15:54 +1 min

  1. Olten15:06
  2. Langenthal15:17
  3. Herzogenbuchsee15:23
  4. Wynigen15:30
  5. Burgdorf15:37
  6. Bern15:53

Next service: tomorrow 15:06 from Olten · Mon 9 Nov

Next departure 15:06 tomorrow · Olten
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
100%
37/37 runs under 3 min
RT coverage: 37 full · 0 partial · 2 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

Distribution · 90 days

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

  • Early 19% · 7
  • On time 81% · 30
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=4
  • 100% W n=4
  • 100% T n=5
  • 100% F n=7
  • 100% 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, 37 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
15:06on time on time
15:17 / 15:18≈ on time ≈ on time
15:23 / 15:24≈ on time ≈ on time
15:30 / 15:31≈ on time ≈ on time
15:37 / 15:38≈ on time ≈ on time
15:53on time +1 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
Sun 8 NovBern 15:54+1 min—
Sat 7 NovBern 15:540 min—
Fri 6 NovBern 15:54+1 min—
Thu 5 NovBern 15:54+1 min—
Wed 4 NovBern 15:540 min—
Tue 3 NovBern 15:54No data—
Mon 2 NovBern 15:54−1 min—
Sun 1 NovBern 15:52−1 min—
Sat 31 OctBern 15:540 min—
Fri 30 OctBern 15:540 min—
Thu 29 OctBern 15:53−1 min—
Wed 28 OctBern 15:540 min—
Tue 27 OctBern 15:540 min—
Mon 26 OctBern 15:540 min—
Sun 25 OctBern 15:54+1 min—
Sat 24 OctBern 15:55+1 min+1 min
Fri 23 OctBern 15:53−1 min—
Thu 22 OctBern 15:52−2 min—
Wed 21 OctBern 15:540 min—
Tue 20 OctBern 15:53−1 min—
Mon 19 OctBern 15:540 min—
Sun 18 OctBern 15:55+1 min—
Sat 17 OctBern 15:53−1 min—
Fri 16 OctBern 15:54−1 min—
Thu 15 OctBern 15:540 min—
Wed 14 OctBern 15:530 min—
Tue 13 OctBern 15:54−1 min—
Mon 12 OctBern 15:540 min—
Sun 11 OctBern 15:540 min—
Sat 10 OctBern 15:540 min—