IR55 1793 Biel/Bienne – Olten

View line IR55

Biel/Bienne 23:16 → Olten 23:57 Daily 0 h 41 min · 5 stops SBB CFF FFS

It has not run yet today

Last recorded run: Friday 13 November +2 min

Next service: today 23:16 from Biel/Bienne · Sat 14 Nov

Next departure 23:16 today · Biel/Bienne
On-time · 30 days
75%
21/28 runs under 3 min
RT coverage: 28 full · 0 partial · 1 no data
On-time · 90 days
82%
41/50 runs under 3 min
RT coverage: 50 full · 0 partial · 4 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +2 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +4 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 12 Nov Max en route +37 min · last fix heading to Olten +37 min
  • Wed 4 Nov Max en route +10 min · last fix heading to Olten +10 min
  • Wed 14 Oct Max en route +8 min · last fix heading to Olten +8 min
  • Mon 9 Nov Max en route +5 min · last fix heading to Olten +5 min
  • Wed 11 Nov Max en route +4 min · last fix heading to Olten +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 82% · 41
  • 3–10 min 16% · 8
  • 10–30 min 0% · 0
  • 30+ min 2% · 1

On-time by weekday

  • 71% M n=7
  • 100% T n=7
  • 57% W n=7
  • 57% T n=7
  • 100% F n=7
  • 88% S n=8
  • 100% S n=7

Stops and timetable

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

Last 90 days, 50 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:16+1 min +1 min
23:25≈ +1 min ≈ +2 min
23:33≈ +1 min ≈ +2 min
23:45≈ +1 min ≈ +3 min
23:57+1 min +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
Fri 13 NovOlten 23:59+2 min+2 min
Thu 12 NovOlten 00:35+37 min+37 min
Wed 11 NovOlten 00:02+4 min+4 min
Tue 10 NovOlten 23:58−1 min—
Mon 9 NovOlten 00:04+5 min+5 min
Sun 8 NovOlten 23:59+1 min—
Sat 7 NovOlten 23:59+3 min+3 min
Fri 6 NovOlten 23:59+3 min+3 min
Thu 5 NovOlten 00:02+4 min+4 min
Wed 4 NovOlten 00:08+10 min+10 min
Tue 3 NovOlten 23:590 min—
Mon 2 NovOlten 23:59+3 min+3 min
Sun 1 NovOlten 23:59+2 min+2 min
Sat 31 OctOlten 00:01+3 min+3 min
Fri 30 OctOlten 23:57−1 min—
Thu 29 OctOlten 23:580 min—
Wed 28 OctOlten 23:590 min—
Tue 27 OctOlten 23:59+1 min—
Mon 26 OctOlten 00:00+2 min+2 min
Sun 25 OctOlten 23:580 min—
Sat 24 OctOlten 23:59+1 min+1 min
Fri 23 OctOlten 00:00+2 min+2 min
Thu 22 OctOlten 23:59+1 min—
Wed 21 OctOlten 23:580 min—
Tue 20 OctOlten 23:59+1 min—
Mon 19 OctOlten 23:59+1 min+1 min
Sun 18 OctOlten 23:58−1 min—
Sat 17 OctOlten 00:00+3 min+3 min
Fri 16 OctOlten 23:58No data—
Thu 15 OctOlten 00:01+4 min+4 min