S9 17930 Olten → Sissach

View line S9

Olten 16:36 → Sissach 16:58 Daily 0 h 22 min · 8 stops SBB CFF FFS

S9 17930 Olten–Sissach: final delay under 3 min on 27 of its 28 runs with data in the last 30 days (96%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 21:03 (GMT+1).

✓ Today’s run finished

Today it reached Sissach at 16:59 +1 min

  1. Olten16:36
  2. Trimbach16:40
  3. Läufelfingen16:45
  4. Rümlingen16:49
  5. Sommerau16:51
  6. Diepflingen16:53
  7. Sissach16:58

Next service: tomorrow 16:36 from Olten · Mon 23 Nov

Next departure 16:36 tomorrow · Olten
On-time · 30 days
96%
27/28 runs under 3 min
RT coverage: 28 full · 0 partial · 0 no data
On-time · 90 days
98%
45/46 runs under 3 min
RT coverage: 46 full · 0 partial · 0 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 Sissach, 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 17 Nov Max en route +7 min · last fix heading to Sissach +7 min

Distribution · 90 days

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

  • Early 17% · 8
  • On time 80% · 37
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 46 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
16:36on time on time
16:40≈ on time ≈ on time
16:45≈ on time ≈ on time
16:47≈ on time ≈ +1 min
16:49≈ on time ≈ +1 min
16:51≈ on time ≈ +1 min
16:53≈ on time ≈ +1 min
16:58on 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 NovSissach 16:59+1 min—
Sat 21 NovSissach 16:58−1 min—
Fri 20 NovSissach 16:58−1 min—
Thu 19 NovSissach 16:59+1 min+1 min
Wed 18 NovSissach 16:58−1 min—
Tue 17 NovSissach 17:07+7 min+7 min
Mon 16 NovSissach 16:590 min—
Fri 13 NovSissach 16:590 min—
Thu 12 NovSissach 16:590 min—
Wed 11 NovSissach 16:59−1 min—
Tue 10 NovSissach 16:590 min—
Mon 9 NovSissach 16:58−1 min—
Sun 8 NovSissach 16:590 min—
Sat 7 NovSissach 16:580 min—
Fri 6 NovSissach 16:59+1 min+1 min
Thu 5 NovSissach 16:57−1 min—
Wed 4 NovSissach 16:590 min—
Tue 3 NovSissach 16:58−1 min—
Mon 2 NovSissach 16:59−1 min—
Sun 1 NovSissach 16:58−1 min—
Sat 31 OctSissach 16:57−1 min—
Fri 30 OctSissach 16:58−1 min—
Thu 29 OctSissach 16:58−1 min—
Wed 28 OctSissach 16:590 min—
Tue 27 OctSissach 16:58−2 min—
Mon 26 OctSissach 16:590 min—
Sun 25 OctSissach 16:590 min—
Sat 24 OctSissach 16:57−2 min—
Fri 23 OctSissach 16:590 min—
Thu 22 OctSissach 16:590 min—