S3 17358 Olten – Laufen

View line S3

Olten 15:48 → Laufen 17:07 Daily 1 h 19 min · 19 stops SBB CFF FFS

Running now · updated 17:07

Position estimated from the timetable

Between Zwingen and Laufen 0 min

Estimated arrival at Laufen 17:07 · 16 km/h

  1. Olten15:48
  2. Sissach16:02
  3. Liestal16:10
  4. Muttenz16:20
  5. Münchenstein16:44
  6. Zwingen17:03
  7. Laufen17:07

Today it is running no worse than usual: typical arrival delay is 0 min; 100% of the last 30 runs arrived on time.

On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
100%
55/55 runs under 3 min
RT coverage: 55 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 Laufen, 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 55 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 10Today
15:48on time on timePassed
15:55≈ on time ≈ on timePassed
15:58≈ on time ≈ on timePassed
16:02≈ on time ≈ on timePassed
16:04≈ on time ≈ on timePassed
16:06≈ on time ≈ on timePassed
16:10≈ on time ≈ on timePassed
16:13≈ on time ≈ on timePassed
16:16 / 16:17≈ on time ≈ on timePassed
16:20≈ on time ≈ on timePassed
16:26 / 16:38≈ on time ≈ on timePassed
16:41≈ on time ≈ on timePassed
16:44≈ on time ≈ on timePassed
16:48≈ on time ≈ on timePassed
16:51≈ on time ≈ on timePassed
16:53≈ on time ≈ on timePassed
16:56 / 16:58≈ on time ≈ +1 minPassed
17:03≈ on time ≈ +1 minPassed
17:07on time +1 minNext

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
Thu 19 NovLaufen 17:040 min—
Wed 18 NovLaufen 17:09+2 min+2 min
Tue 17 NovLaufen 17:080 min—
Mon 16 NovLaufen 17:080 min—
Sun 15 NovLaufen 17:070 min—
Sat 14 NovLaufen 17:09+1 min—
Fri 13 NovLaufen 17:080 min—
Thu 12 NovLaufen 17:080 min—
Wed 11 NovLaufen 17:080 min—
Tue 10 NovLaufen 17:070 min—
Mon 9 NovLaufen 17:080 min—
Sun 8 NovLaufen 17:08−1 min—
Sat 7 NovLaufen 17:070 min—
Fri 6 NovLaufen 17:080 min—
Thu 5 NovLaufen 17:080 min—
Wed 4 NovLaufen 17:080 min—
Tue 3 NovLaufen 17:090 min—
Mon 2 NovLaufen 17:090 min—
Sun 1 NovLaufen 17:080 min—
Sat 31 OctLaufen 17:07−1 min—
Fri 30 OctLaufen 17:080 min—
Thu 29 OctLaufen 17:080 min—
Wed 28 OctLaufen 17:080 min—
Tue 27 OctLaufen 17:10+2 min+2 min
Mon 26 OctLaufen 17:080 min—
Sun 25 OctLaufen 17:070 min—
Sat 24 OctLaufen 17:080 min—
Fri 23 OctLaufen 17:09+1 min—
Thu 22 OctLaufen 17:080 min—
Wed 21 OctLaufen 17:080 min—