S26 8664 Rotkreuz – Olten

View line S26

Rotkreuz 16:23 → Olten 17:21 Daily 0 h 58 min · 16 stops SBB CFF FFS

It has not run yet today

Last recorded run: Tuesday 17 November +2 min

Next service: today 16:23 from Rotkreuz · Wed 18 Nov

Next departure 16:23 today · Rotkreuz
On-time · 30 days
93%
27/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
97%
69/71 runs under 3 min
RT coverage: 71 full · 0 partial · 1 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

  • Thu 22 Oct Max en route +4 min · last fix heading to Olten +4 min
  • Thu 12 Nov Max en route +3 min · last fix heading to Olten +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 69
  • 3–10 min 3% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=10
  • 100% T n=10
  • 100% W n=9
  • 78% T n=9
  • 100% F n=11
  • 100% S n=11
  • 100% S n=11

Stops and timetable

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

Last 90 days, 71 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
16:23on time on time
16:26≈ on time ≈ on time
16:29≈ on time ≈ on time
16:32≈ on time ≈ on time
16:35≈ on time ≈ +1 min
16:39≈ on time ≈ +1 min
16:42≈ on time ≈ +1 min
16:46 / 16:47≈ on time ≈ +1 min
16:50≈ on time ≈ +1 min
16:53≈ on time ≈ +1 min
16:58 / 17:00≈ on time ≈ +1 min
17:07 / 17:08≈ on time ≈ +2 min
17:11≈ on time ≈ +2 min
17:13≈ on time ≈ +2 min
17:16≈ on time ≈ +2 min
17:21+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
Tue 17 NovOlten 17:24+2 min+2 min
Mon 16 NovOlten 17:22+1 min—
Sun 15 NovOlten 17:23+1 min+1 min
Sat 14 NovOlten 17:220 min—
Fri 13 NovOlten 17:230 min—
Thu 12 NovOlten 17:24+3 min+3 min
Wed 11 NovOlten 17:220 min—
Tue 10 NovOlten 17:23+1 min+1 min
Mon 9 NovOlten 17:24+3 min+3 min
Sun 8 NovOlten 17:220 min—
Sat 7 NovOlten 17:22+2 min+2 min
Fri 6 NovOlten 17:24+3 min+3 min
Thu 5 NovOlten 17:220 min—
Wed 4 NovOlten 17:23+1 min—
Tue 3 NovOlten 17:23+1 min—
Mon 2 NovOlten 17:23+1 min—
Sun 1 NovOlten 17:220 min—
Sat 31 OctOlten 17:210 min—
Fri 30 OctOlten 17:220 min—
Thu 29 OctOlten 17:23+1 min—
Wed 28 OctOlten 17:23+1 min—
Tue 27 OctOlten 17:24+2 min+2 min
Mon 26 OctOlten 17:24+1 min+1 min
Sun 25 OctOlten 17:220 min—
Sat 24 OctOlten 17:24+2 min+2 min
Fri 23 OctOlten 17:23+1 min+1 min
Thu 22 OctOlten 17:26+4 min+4 min
Wed 21 OctOlten 17:23+1 min—
Tue 20 OctOlten 17:230 min—
Mon 19 OctOlten 17:23+1 min+1 min