IR17 2846 Olten – Bern

View line IR17

Olten 00:37 → Bern 01:26 Fri, Sat, Sun 0 h 49 min · 6 stops BLS

✓ Today’s run finished

Today it reached Bern at 01:27 +1 min

  1. Olten00:37
  2. Langenthal00:49
  3. Herzogenbuchsee00:54
  4. Wynigen01:01
  5. Burgdorf01:08
  6. Bern01:26

Next service: Friday 00:37 from Olten · Fri 13 Nov

Next departure 00:37 Friday · Olten
On-time · 30 days
89%
8/9 runs under 3 min
RT coverage: 9 full · 0 partial · 0 no data
On-time · 90 days
88%
23/26 runs under 3 min
RT coverage: 26 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +3 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 24 Oct Max en route +13 min · last fix heading to Bern +13 min
  • Sun 4 Oct Max en route +7 min · last fix heading to Bern +7 min
  • Sat 26 Sept Max en route +5 min · last fix heading to Bern +5 min

Distribution · 90 days

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

  • Early 4% · 1
  • On time 85% · 22
  • 3–10 min 8% · 2
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • — T n=0
  • 100% W n=7
  • — T n=0
  • 100% F n=5
  • 67% 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, 26 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
00:37on time +1 min
00:49 / 00:50≈ on time ≈ +1 min
00:54 / 00:55≈ on time ≈ +1 min
01:01 / 01:02≈ on time ≈ +2 min
01:08 / 01:10≈ on time ≈ +3 min
01:26on time +4 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
Sat 7 NovBern 01:28+1 min—
Sun 1 NovBern 01:270 min—
Sat 31 OctBern 01:25−2 min—
Sun 25 OctBern 01:27+1 min—
Sat 24 OctBern 01:40+13 min+13 min
Sun 18 OctBern 01:27−1 min—
Sat 17 OctBern 01:280 min—
Sun 11 OctBern 01:27−1 min—
Sat 10 OctBern 01:29+1 min+1 min
Sun 4 OctBern 01:38+7 min+7 min
Fri 2 OctBern 01:25+2 min+2 min
Wed 30 SeptBern 01:26+1 min+2 min
Sat 26 SeptBern 01:26+5 min+5 min
Fri 25 SeptBern 01:260 min+1 min
Wed 23 SeptBern 01:260 min+16 min
Wed 16 SeptBern 01:250 min+2 min
Fri 11 SeptBern 01:260 min+2 min
Wed 9 SeptBern 01:25+2 min+4 min
Mon 31 AugBern 00:010 min+2 min
Sun 30 AugBern 00:010 min+29 min
Fri 28 AugBern 00:01−1 min+5 min
Wed 26 AugBern 00:010 min+4 min
Mon 24 AugBern 00:020 min—
Wed 19 AugBern 01:250 min+3 min
Fri 14 AugBern 01:25+1 min+3 min
Wed 12 AugBern 01:250 min+2 min