S26 8620 Muri AG – Olten

View line S26

Muri AG 05:39 → Olten 06:21 Daily 0 h 42 min · 12 stops SBB CFF FFS

It has not run yet today

Last recorded run: Sunday 15 November +1 min

Next service: today 05:39 from Muri AG · Mon 16 Nov

Next departure 05:39 today · Muri AG
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
100%
53/53 runs under 3 min
RT coverage: 53 full · 0 partial · 4 no data
Typical delay
+1min
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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 53
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=7
  • 100% W n=9
  • 100% T n=8
  • 100% F n=7
  • 100% S n=8
  • 100% S n=8

Stops and timetable

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

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