S9 17929 Sissach – Olten

View line S9

Sissach 05:31 → Olten 05:53 Daily 0 h 22 min · 8 stops SBB CFF FFS

It has not run yet today

Last recorded run: Friday 13 November 0 min

Next service: tomorrow 05:31 from Sissach · Tue 17 Nov

Next departure 05:31 tomorrow · Sissach
On-time · 30 days
100%
25/25 runs under 3 min
RT coverage: 25 full · 0 partial · 1 no data
On-time · 90 days
98%
39/40 runs under 3 min
RT coverage: 40 full · 0 partial · 1 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

  • Wed 14 Oct Max en route +3 min · last fix heading to Olten +3 min

Distribution · 90 days

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

  • Early 3% · 1
  • On time 95% · 38
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=5
  • 83% W n=6
  • 100% T n=6
  • 100% F n=7
  • 100% S n=5
  • 100% S n=5

Stops and timetable

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

Last 90 days, 40 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:31on time on time
05:34≈ on time ≈ on time
05:36≈ on time ≈ on time
05:38≈ on time ≈ on time
05:40≈ on time ≈ on time
05:43≈ on time ≈ on time
05:47≈ on time ≈ +1 min
05:53on 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
Fri 13 NovOlten 16:280 min—
Thu 12 NovOlten 16:280 min—
Wed 11 NovOlten 16:280 min—
Tue 10 NovOlten 16:270 min—
Mon 9 NovOlten 16:27−1 min—
Sun 8 NovOlten 16:280 min—
Sat 7 NovOlten 16:28+1 min—
Fri 6 NovOlten 16:29+1 min+1 min
Thu 5 NovOlten 16:28−1 min—
Wed 4 NovOlten 16:27−1 min—
Tue 3 NovOlten 16:28No data—
Mon 2 NovOlten 16:280 min+3 min
Sun 1 NovOlten 16:280 min—
Sat 31 OctOlten 16:29+1 min+3 min
Fri 30 OctOlten 16:29+1 min—
Thu 29 OctOlten 16:280 min—
Wed 28 OctOlten 16:280 min—
Tue 27 OctOlten 16:28−1 min—
Mon 26 OctOlten 16:28−1 min—
Sun 25 OctOlten 16:27−1 min—
Sat 24 OctOlten 16:29+1 min—
Fri 23 OctOlten 16:280 min—
Thu 22 OctOlten 16:27−1 min—
Wed 21 OctOlten 16:270 min—
Tue 20 OctOlten 16:290 min—
Mon 19 OctOlten 16:270 min—
Fri 16 OctOlten 16:27−1 min—
Thu 15 OctOlten 16:290 min—
Wed 14 OctOlten 16:31+3 min+3 min
Tue 13 OctOlten 16:28−1 min—