S26 8640 Rotkreuz – Olten

View line S26

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

It has not run yet today

Last recorded run: Monday 16 November 0 min

Next service: today 10:23 from Rotkreuz · Tue 17 Nov

Next departure 10:23 today · Rotkreuz
On-time · 30 days
96%
27/28 runs under 3 min
RT coverage: 28 full · 0 partial · 1 no data
On-time · 90 days
96%
68/71 runs under 3 min
RT coverage: 71 full · 0 partial · 5 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: +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

  • Wed 14 Oct Max en route +5 min · last fix heading to Olten +5 min
  • Fri 23 Oct Max en route +4 min · last fix heading to Olten +4 min
  • Fri 9 Oct 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 3% · 2
  • On time 93% · 66
  • 3–10 min 4% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=11
  • 100% T n=9
  • 91% W n=11
  • 100% T n=7
  • 83% F n=12
  • 100% S n=9
  • 100% S n=12

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