IR35 2399 Bern – Olten

View line IR35

Bern 23:38 → Olten 00:26 Mon, Tue, Wed, Thu, Sun 0 h 48 min · 5 stops SOB

It does not run today

Last recorded run: Thursday 12 November +3 min

Next service: Sunday 23:38 from Bern · Sun 15 Nov

Next departure 23:38 Sunday · Bern
On-time · 30 days
97%
28/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
98%
47/48 runs under 3 min
RT coverage: 48 full · 0 partial · 0 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: +3 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

  • Fri 23 Oct Max en route +19 min · last fix heading to Olten +19 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=9
  • 100% T n=7
  • 100% W n=7
  • 100% T n=7
  • 80% F n=5
  • 100% S n=6
  • 100% S n=7

Stops and timetable

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

Last 90 days, 48 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
23:38on time +1 min
23:55 / 23:56≈ on time ≈ +1 min
00:07 / 00:08≈ on time ≈ +1 min
00:13 / 00:14≈ on time ≈ +2 min
00:26on time +2 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
Thu 12 NovOlten 00:29+3 min+3 min
Wed 11 NovOlten 00:29+3 min+3 min
Tue 10 NovOlten 00:270 min—
Mon 9 NovOlten 00:270 min—
Sun 8 NovOlten 00:24−1 min—
Sat 7 NovOlten 00:270 min—
Fri 6 NovOlten 00:28+1 min—
Thu 5 NovOlten 00:29+2 min+2 min
Wed 4 NovOlten 00:28+1 min—
Tue 3 NovOlten 00:29+1 min+1 min
Mon 2 NovOlten 00:27−1 min—
Sun 1 NovOlten 00:280 min—
Sat 31 OctOlten 00:270 min—
Fri 30 OctOlten 00:270 min—
Thu 29 OctOlten 00:29+2 min+2 min
Wed 28 OctOlten 00:27−1 min—
Tue 27 OctOlten 00:27−1 min+2 min
Mon 26 OctOlten 00:27−1 min—
Sun 25 OctOlten 00:24−2 min—
Sat 24 OctOlten 00:270 min—
Fri 23 OctOlten 00:46+19 min+19 min
Thu 22 OctOlten 00:270 min—
Wed 21 OctOlten 00:27+1 min—
Tue 20 OctOlten 00:270 min—
Mon 19 OctOlten 00:30+3 min+3 min
Sun 18 OctOlten 00:29+2 min+2 min
Sat 17 OctOlten 00:28+2 min+2 min
Fri 16 OctOlten 00:30+2 min+2 min
Thu 15 OctOlten 00:270 min—
Wed 14 OctOlten 00:26−2 min—