IR17 2818 Olten – Bern

View line IR17

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

✓ Today’s run finished

Today it reached Bern at 11:55 +2 min

  1. Olten11:06
  2. Langenthal11:17
  3. Herzogenbuchsee11:23
  4. Wynigen11:30
  5. Burgdorf11:37
  6. Bern11:53

Next service: tomorrow 11:06 from Olten · Mon 16 Nov

Next departure 11:06 tomorrow · Olten
On-time · 30 days
100%
24/24 runs under 3 min
RT coverage: 24 full · 0 partial · 6 no data
On-time · 90 days
97%
33/34 runs under 3 min
RT coverage: 34 full · 0 partial · 9 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

Worst days

  • Sun 4 Oct Max en route +5 min · last fix heading to Bern +5 min

Distribution · 90 days

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

  • Early 15% · 5
  • On time 82% · 28
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=6
  • 100% W n=6
  • 100% T n=2
  • 100% F n=6
  • 100% S n=6
  • 83% S n=6

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