IR17 2824 Olten – Bern

View line IR17

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

✓ Today’s run finished

Today, last fix heading to Bern at 14:54 No data

  1. Olten14:06
  2. Langenthal14:17
  3. Herzogenbuchsee14:23
  4. Wynigen14:30
  5. Burgdorf14:37
  6. Bern14:53

Next service: tomorrow 14:06 from Olten · Fri 6 Nov

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

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

  • Early 17% · 5
  • On time 83% · 25
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=6
  • 100% W n=5
  • 100% T n=4
  • 100% F n=4
  • 100% S n=4
  • 100% S n=4

Stops and timetable

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

Last 90 days, 30 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
14:06on time on time
14:17 / 14:18≈ on time ≈ on time
14:23 / 14:24≈ on time ≈ on time
14:30 / 14:31≈ on time ≈ on time
14:37 / 14:38≈ on time ≈ on time
14:53on time on time

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