S26 30592 Muri AG – Olten

View line S26

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

It does not run today

Last recorded run: Sunday 8 November No data

Next service: Sunday 05:39 from Muri AG · Sun 15 Nov

Next departure 05:39 Sunday · Muri AG
On-time · 30 days
—
Too little data (0/1 runs with data)
RT coverage: 0 full · 0 partial · 1 no data
On-time · 90 days
100%
8/8 runs under 3 min
RT coverage: 8 full · 0 partial · 2 no data
Typical delay
0min
Median at arrival, 90 days
P90
+1min
9 in 10 runs arrive with less than this

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

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

  • Early 13% · 1
  • On time 88% · 7
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • — T n=0
  • 100% W n=2
  • 100% T n=2
  • 100% F n=2
  • 100% S n=1
  • 100% S n=1

Stops and timetable

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

Last 90 days, 8 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 +1 min
05:42≈ on time ≈ +1 min
05:46 / 05:47≈ on time ≈ +1 min
05:50≈ on time ≈ +1 min
05:53≈ on time ≈ +1 min
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: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 8 NovOlten 00:22No data—
Thu 24 SeptNeuchâtel 15:55−2 min—
Wed 23 SeptNeuchâtel 15:55−1 min+4 min
Mon 21 SeptBiel/Bienne 22:07No data—
Sun 20 SeptBiel/Bienne 22:070 min—
Sat 19 SeptBiel/Bienne 22:080 min—
Fri 18 SeptBiel/Bienne 22:07−1 min—
Fri 4 SeptBurgdorf 00:47−1 min+5 min
Thu 3 SeptLenzburg 07:24+1 min—
Wed 2 SeptLenzburg 07:24+1 min—