IR35 2599 Bern – Olten

View line IR35

Bern 22:33 → Olten 23:25 Daily 0 h 52 min · 5 stops SBB CFF FFS

It has not run yet today

Last recorded run: Thursday 19 November −1 min

Next service: today 22:33 from Bern · Fri 20 Nov

Next departure 22:33 today · Bern
On-time · 30 days
93%
27/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
96%
43/45 runs under 3 min
RT coverage: 45 full · 0 partial · 0 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: −1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Sat 24 Oct Max en route +4 min · last fix heading to Olten +4 min
  • Fri 23 Oct Max en route +4 min · last fix heading to Olten +4 min

Distribution · 90 days

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

  • Early 38% · 17
  • On time 58% · 26
  • 3–10 min 4% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 45 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
22:33on time +2 min
22:48 / 22:51≈ on time ≈ +2 min
23:02 / 23:03≈ on time ≈ +2 min
23:09 / 23:10≈ on time ≈ +2 min
23:251 min early +3 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 19 NovOlten 23:24−1 min—
Wed 18 NovOlten 23:24−2 min—
Tue 17 NovOlten 23:24−2 min—
Mon 16 NovOlten 23:23−3 min—
Sun 15 NovOlten 23:240 min—
Sat 14 NovOlten 23:24−2 min—
Fri 13 NovOlten 23:24−1 min—
Thu 12 NovOlten 23:25+2 min+2 min
Wed 11 NovOlten 23:24−1 min—
Tue 10 NovOlten 23:24−1 min—
Mon 9 NovOlten 23:24−3 min—
Sun 8 NovOlten 23:24−3 min—
Sat 7 NovOlten 23:240 min—
Fri 6 NovOlten 23:24−1 min—
Thu 5 NovOlten 23:24−3 min—
Wed 4 NovOlten 23:24−1 min—
Tue 3 NovOlten 23:24−1 min—
Mon 2 NovOlten 23:240 min—
Sun 1 NovOlten 23:24−1 min—
Sat 31 OctOlten 23:25−1 min—
Fri 30 OctOlten 23:25−1 min—
Thu 29 OctOlten 23:24−2 min—
Wed 28 OctOlten 23:270 min—
Tue 27 OctOlten 23:260 min—
Mon 26 OctOlten 23:26−1 min—
Sun 25 OctOlten 23:28+3 min+3 min
Sat 24 OctOlten 23:29+4 min+4 min
Fri 23 OctOlten 23:30+4 min+4 min
Thu 22 OctOlten 23:25−1 min—
Wed 21 OctOlten 23:24−3 min—