S26 8696 Rotkreuz – Olten

View line S26

Rotkreuz 00:23 → Olten 01:22 Fri, Sat 0 h 59 min · 17 stops SBB CFF FFS

It does not run today

Last recorded run: Sunday 15 November +1 min

Next service: Friday 00:23 from Rotkreuz · Fri 20 Nov

Next departure 00:23 Friday · Rotkreuz
On-time · 30 days
78%
7/9 runs under 3 min
RT coverage: 9 full · 0 partial · 0 no data
On-time · 90 days
80%
20/25 runs under 3 min
RT coverage: 25 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +6 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 24 Oct Max en route +15 min · last fix heading to Olten +14 min
  • Wed 2 Sept Max en route +5 min · last fix heading to Dulliken +5 min
  • Sat 10 Oct Max en route +4 min · last fix heading to Olten +4 min
  • Sat 7 Nov Max en route +3 min · last fix heading to Olten +3 min
  • Tue 29 Sept Max en route +3 min · last fix heading to Olten +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 80% · 20
  • 3–10 min 16% · 4
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 50% T n=2
  • 50% W n=2
  • — T n=0
  • 100% F n=3
  • 67% S n=9
  • 100% S n=8

Stops and timetable

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

Last 90 days, 25 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
00:23on time on time
00:26≈ on time ≈ +1 min
00:29≈ on time ≈ +1 min
00:32≈ on time ≈ +1 min
00:35≈ on time ≈ +1 min
00:39≈ on time ≈ +1 min
00:42≈ on time ≈ +1 min
00:46 / 00:47≈ on time ≈ +1 min
00:50≈ on time ≈ +2 min
00:53≈ on time ≈ +2 min
00:58 / 01:00≈ on time ≈ +2 min
01:04≈ on time ≈ +2 min
01:08≈ on time ≈ +3 min
01:12≈ on time ≈ +3 min
01:14≈ on time ≈ +3 min
01:17≈ on time ≈ +3 min
01:22on time +3 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
Sun 15 NovOlten 01:24+1 min+1 min
Sat 14 NovOlten 01:240 min+2 min
Sun 8 NovOlten 01:220 min—
Sat 7 NovOlten 01:27+3 min+3 min
Sun 1 NovOlten 01:24+1 min+1 min
Sat 31 OctOlten 01:230 min—
Sun 25 OctOlten 01:24+1 min—
Sat 24 OctOlten 01:37+14 min+15 min
Sun 18 OctOlten 01:25+2 min+2 min
Sat 17 OctOlten 01:230 min—
Sun 11 OctOlten 01:22−1 min—
Sat 10 OctOlten 01:28+4 min+4 min
Sun 4 OctOlten 01:24+1 min—
Fri 2 OctOlten 01:210 min+3 min
Thu 1 OctOlten 01:22No data—
Wed 30 SeptOlten 20:21−1 min+1 min
Tue 29 SeptOlten 20:21+3 min+3 min
Mon 28 SeptOlten 20:210 min—
Sat 26 SeptOlten 01:210 min+3 min
Fri 25 SeptOlten 20:210 min—
Sun 20 SeptOlten 01:220 min—
Sat 5 SeptOlten 23:200 min—
Wed 2 SeptDulliken 20:20+5 min+5 min
Tue 1 SeptOlten 20:200 min—
Sat 29 AugOlten 01:21+1 min+1 min
Fri 28 AugOlten 20:200 min—