S26 8648 Rotkreuz → Olten

View line S26

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

S26 8648 Rotkreuz–Olten: final delay under 3 min on 22 of its 22 runs with data in the last 30 days (100%). Median final delay: 0 min. Running now, on time. Expected at Olten: 13:21. TrainsRadar data as of 22 Nov 2026, 13:13 (GMT+1).

Running now · updated 13:13

Position estimated from the timetable

Between Däniken SO and Dulliken 0 min

Estimated arrival at Olten 13:21 · 71 km/h

  1. Rotkreuz12:23
  2. Mühlau12:32
  3. Muri AG12:39
  4. Dottikon-Dintikon12:50
  5. Däniken SO13:13
  6. Dulliken13:16
  7. Olten13:21

Today it is running no worse than usual: typical arrival delay is 0 min; 100% of the last 22 runs arrived on time.

On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 21 full · 1 partial · 8 no data
On-time · 90 days
98%
57/58 runs under 3 min
RT coverage: 57 full · 1 partial · 14 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 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

  • Fri 16 Oct Max en route +3 min · last fix heading to Olten +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 98% · 57
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=9
  • 100% W n=10
  • 100% T n=4
  • 92% F n=12
  • 100% S n=10
  • 100% S n=9

Stops and timetable

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

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