S26 8628 Rotkreuz – Olten

View line S26

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

✓ Today’s run finished

Today it reached Olten at 14:22 +1 min

  1. Rotkreuz13:23
  2. Mühlau13:32
  3. Muri AG13:39
  4. Dottikon-Dintikon13:50
  5. Lenzburg13:58
  6. Däniken SO14:13
  7. Olten14:21

Next service: tomorrow 13:23 from Rotkreuz · Tue 17 Nov

Next departure 13: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
96%
69/72 runs under 3 min
RT coverage: 72 full · 0 partial · 3 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 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

  • Tue 1 Sept Max en route +4 min · last fix heading to Olten +4 min
  • Wed 2 Sept Max en route +4 min · last fix heading to Olten +4 min
  • Wed 14 Oct Max en route +3 min · last fix heading to Olten +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 69
  • 3–10 min 4% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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