S26 8684 Rotkreuz – Olten

View line S26

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

Running now · updated 22:21

Position estimated from the timetable

Between Dulliken and Olten +1 min

Estimated arrival at Olten 22:22 · 9 km/h

  1. Rotkreuz21:23
  2. Mühlau21:32
  3. Muri AG21:39
  4. Dottikon-Dintikon21:50
  5. Lenzburg21:58
  6. Dulliken22:16
  7. Olten22:21

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

On-time · 30 days
93%
28/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
93%
64/69 runs under 3 min
RT coverage: 69 full · 0 partial · 5 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 8 Oct Max en route +4 min · last fix heading to Olten +4 min
  • Sat 7 Nov Max en route +4 min · last fix heading to Olten +4 min
  • Mon 16 Nov Max en route +3 min · last fix heading to Olten +3 min
  • Thu 1 Oct Max en route +3 min · last fix heading to Olten +3 min
  • Fri 18 Sept Max en route +3 min · last fix heading to Lenzburg +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 64
  • 3–10 min 7% · 5
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 69 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
21:23on time on timePassed
21:26≈ on time ≈ on timePassed
21:29≈ on time ≈ on timePassed
21:32≈ on time ≈ on timePassed
21:35≈ on time ≈ +1 minPassed
21:39≈ on time ≈ +1 minPassed
21:42≈ on time ≈ +1 minPassed
21:46 / 21:47≈ on time ≈ +1 minPassed
21:50≈ on time ≈ +1 minPassed
21:53≈ on time ≈ +1 minPassed
21:58 / 22:00≈ on time ≈ +1 minPassed
22:07 / 22:08≈ on time ≈ +2 minPassed
22:11≈ on time ≈ +2 minPassed
22:13≈ on time ≈ +2 minPassed
22:16≈ on time ≈ +2 minPassed
22:21+1 min +2 minNext

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 22:190 min—
Wed 18 NovOlten 22:19−1 min—
Tue 17 NovOlten 22:24+2 min+2 min
Mon 16 NovOlten 22:24+3 min+3 min
Sun 15 NovOlten 22:19−1 min—
Sat 14 NovOlten 22:23+1 min—
Fri 13 NovOlten 22:23+1 min—
Thu 12 NovOlten 22:25+3 min+3 min
Wed 11 NovOlten 22:220 min—
Tue 10 NovOlten 22:220 min—
Mon 9 NovOlten 22:180 min—
Sun 8 NovOlten 22:220 min—
Sat 7 NovOlten 22:24+4 min+4 min
Fri 6 NovOlten 22:230 min—
Thu 5 NovOlten 22:22+1 min—
Wed 4 NovOlten 22:23+1 min—
Tue 3 NovOlten 22:24+1 min+1 min
Mon 2 NovOlten 22:23+1 min—
Sun 1 NovOlten 22:23+1 min—
Sat 31 OctOlten 22:23+1 min+1 min
Fri 30 OctOlten 22:220 min—
Thu 29 OctOlten 22:21−1 min—
Wed 28 OctOlten 22:24+2 min+2 min
Tue 27 OctOlten 22:230 min—
Mon 26 OctOlten 22:25+2 min+2 min
Sun 25 OctOlten 22:220 min—
Sat 24 OctOlten 22:24+3 min+3 min
Fri 23 OctOlten 22:22+1 min+1 min
Thu 22 OctOlten 22:23+1 min—
Wed 21 OctOlten 22:23+1 min+1 min