IR17 2849 Bern – Olten

View line IR17

Bern 01:09 → Olten 01:58 Fri, Sat 0 h 49 min · 6 stops BLS

Running now · updated 01:59

Between Langenthal and Olten −1 min

Estimated arrival at Olten 01:58 · 17 km/h

  1. Bern01:09
  2. Burgdorf01:24
  3. Wynigen01:30
  4. Herzogenbuchsee01:37
  5. Langenthal01:43
  6. Olten01:58

Today it is running no worse than usual: typical arrival delay is 0 min; 100% of the last 9 runs arrived on time.

On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 9 full · 0 partial · 0 no data
On-time · 90 days
93%
26/28 runs under 3 min
RT coverage: 28 full · 0 partial · 1 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: +1 min

Last 30 days

Arrival delay at Olten, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Thu 17 Sept Max en route +8 min · last fix heading to Olten +8 min
  • Sat 5 Sept Max en route +8 min · last fix heading to Olten +7 min

Distribution · 90 days

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

  • Early 7% · 2
  • On time 86% · 24
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • — T n=0
  • 100% W n=3
  • 80% T n=5
  • 100% F n=3
  • 89% S n=9
  • 100% S n=8

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 10Today
01:09on time +1 minPassed
01:24 / 01:25≈ on time ≈ +2 minPassed
01:30 / 01:31≈ on time ≈ +1 minPassed
01:37 / 01:38≈ on time ≈ +2 minPassed
01:43 / 01:44≈ on time ≈ +2 minPassed
01:58on time +2 minNext

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
Sat 7 NovOlten 01:59−1 min—
Sun 1 NovOlten 01:590 min—
Sat 31 OctOlten 01:590 min—
Sun 25 OctOlten 01:590 min—
Sat 24 OctOlten 02:00+2 min+2 min
Sun 18 OctOlten 01:590 min—
Sat 17 OctOlten 01:590 min—
Sun 11 OctOlten 01:58−1 min—
Sat 10 OctOlten 02:000 min—
Mon 5 OctOlten 01:59No data—
Sun 4 OctOlten 02:00+2 min+2 min
Thu 1 OctOlten 01:580 min—
Wed 30 SeptOlten 01:580 min+1 min
Thu 24 SeptOlten 01:570 min+4 min
Wed 23 SeptOlten 01:580 min+3 min
Sat 19 SeptOlten 01:58−1 min+3 min
Fri 18 SeptOlten 01:57−1 min+3 min
Thu 17 SeptOlten 01:57+8 min+8 min
Sun 13 SeptOlten 01:570 min+2 min
Sat 12 SeptOlten 01:57+3 min+3 min
Sun 6 SeptOlten 01:57+1 min+12 min
Sat 5 SeptOlten 01:57+7 min+8 min
Fri 4 SeptOlten 01:570 min+2 min
Thu 3 SeptOlten 23:540 min—
Sun 16 AugOlten 01:570 min+2 min
Sat 15 AugOlten 01:57−1 min+2 min
Fri 14 AugOlten 01:57−1 min+3 min
Thu 13 AugOlten 01:570 min—
Wed 12 AugOlten 01:57+1 min+1 min