S26 8656 Rotkreuz – Olten

View line S26

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

✓ Today’s run finished

Today it reached Olten at 15:21 0 min

  1. Rotkreuz14:23
  2. Mühlau14:32
  3. Muri AG14:39
  4. Dottikon-Dintikon14:50
  5. Lenzburg14:58
  6. Däniken SO15:13
  7. Olten15:21

Next service: tomorrow 14:23 from Rotkreuz · Sun 15 Nov

Next departure 14:23 tomorrow · Rotkreuz
On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
99%
66/67 runs under 3 min
RT coverage: 67 full · 0 partial · 3 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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 27 Aug Max en route +5 min · last fix heading to Olten +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 99% · 66
  • 3–10 min 1% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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