IR17 2820 Olten – Bern

View line IR17

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

✓ Today’s run finished

Today it reached Bern at 12:53 0 min

  1. Olten12:06
  2. Langenthal12:17
  3. Herzogenbuchsee12:23
  4. Wynigen12:30
  5. Burgdorf12:37
  6. Bern12:53

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

Next departure 12:06 tomorrow · Olten
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 21 full · 0 partial · 9 no data
On-time · 90 days
96%
27/28 runs under 3 min
RT coverage: 28 full · 0 partial · 10 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

Worst days

  • Sat 17 Oct Max en route +7 min · last fix heading to Bern +7 min

Distribution · 90 days

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

  • Early 25% · 7
  • On time 71% · 20
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=5
  • 100% W n=6
  • 100% T n=2
  • 100% F n=5
  • 80% S n=5
  • 100% S n=4

Stops and timetable

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

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