IR35 2387 Bern → Olten

View line IR35

Bern 20:38 → Olten 21:24 Sat, Sun 0 h 46 min · 5 stops SBB CFF FFS

IR35 2387 Bern–Olten: final delay under 3 min on 26 of its 30 runs with data in the last 30 days (87%). Median final delay: +1 min. Running now, on time. Expected at Olten: 21:25. TrainsRadar data as of 21 Nov 2026, 21:09 (GMT+1).

Running now · updated 21:08

Position estimated from the timetable

Between Herzogenbuchsee and Langenthal +1 min

Estimated arrival at Olten 21:25 · 91 km/h

  1. Bern20:38
  2. Burgdorf20:52
  3. Herzogenbuchsee21:04
  4. Langenthal21:10
  5. Olten21:24

Today it is running no worse than usual: typical arrival delay is +1 min; 87% of the last 30 runs arrived on time.

On-time · 30 days
87%
26/30 runs under 3 min
RT coverage: 29 full · 1 partial · 0 no data
On-time · 90 days
91%
43/47 runs under 3 min
RT coverage: 46 full · 1 partial · 0 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 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

  • Sat 7 Nov Max en route +49 min · last fix heading to Olten +49 min
  • Thu 12 Nov Max en route +9 min · last fix heading to Olten +9 min
  • Mon 26 Oct Max en route +4 min · last fix heading to Olten +4 min
  • Mon 9 Nov Max en route +5 min · last fix heading to Olten +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 43
  • 3–10 min 6% · 3
  • 10–30 min 0% · 0
  • 30+ min 2% · 1

On-time by weekday

  • 71% M n=7
  • 100% T n=7
  • 100% W n=7
  • 86% T n=7
  • 100% F n=7
  • 83% S n=6
  • 100% S n=6

Stops and timetable

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

Last 90 days, 47 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
20:38+1 min +1 minPassed
20:52 / 20:53≈ +1 min ≈ +1 minPassed
21:04 / 21:05≈ +1 min ≈ +2 minPassed
21:10 / 21:12≈ +1 min ≈ +2 minNext
21:24+1 min +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
Sat 21 NovHerzogenbuchsee 21:04Partial coverage+1 min—
Fri 20 NovOlten 21:24+1 min+1 min
Thu 19 NovOlten 21:24+1 min+3 min
Wed 18 NovOlten 21:24+2 min+2 min
Tue 17 NovOlten 21:24+1 min—
Mon 16 NovOlten 21:24+1 min+1 min
Sun 15 NovOlten 21:24+1 min—
Sat 14 NovOlten 21:240 min—
Fri 13 NovOlten 21:240 min—
Thu 12 NovOlten 21:34+9 min+9 min
Wed 11 NovOlten 21:240 min—
Tue 10 NovOlten 21:24+1 min—
Mon 9 NovOlten 21:29+3 min+5 min
Sun 8 NovOlten 21:27+2 min+2 min
Sat 7 NovOlten 22:02+49 min+49 min
Fri 6 NovOlten 21:240 min—
Thu 5 NovOlten 21:27+2 min+2 min
Wed 4 NovOlten 21:27+2 min+2 min
Tue 3 NovOlten 21:240 min+2 min
Mon 2 NovOlten 21:240 min—
Sun 1 NovOlten 21:240 min—
Sat 31 OctOlten 21:26+1 min—
Fri 30 OctOlten 21:26+1 min—
Thu 29 OctOlten 21:250 min—
Wed 28 OctOlten 21:26+1 min—
Tue 27 OctOlten 21:27+1 min+1 min
Mon 26 OctOlten 21:29+4 min+4 min
Sun 25 OctOlten 21:25+1 min—
Sat 24 OctOlten 21:25+1 min—
Fri 23 OctOlten 21:26+1 min—