S3 17366 Olten – Laufen

View line S3

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

Running now · updated 17:55

Position estimated from the timetable

Between Tecknau and Gelterkinden 0 min

Estimated arrival at Laufen 19:07 · 81 km/h

  1. Olten17:48
  2. Tecknau17:55
  3. Gelterkinden17:58
  4. Sissach18:02
  5. Liestal18:10
  6. Muttenz18:20
  7. Laufen19:07

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

On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 29 full · 1 partial · 0 no data
On-time · 90 days
97%
57/59 runs under 3 min
RT coverage: 58 full · 1 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

Worst days

  • Tue 20 Oct Max en route +6 min · last fix heading to Laufen +6 min
  • Mon 12 Oct Max en route +5 min · last fix heading to Laufen +5 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 59 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
17:48on time on timePassed
17:55≈ on time ≈ on timePassed
17:58≈ on time ≈ on timeNext
18:02≈ on time ≈ on time
18:04≈ on time ≈ on time
18:06≈ on time ≈ on time
18:10≈ on time ≈ on time
18:13≈ on time ≈ on time
18:16 / 18:17≈ on time ≈ on time
18:20≈ on time ≈ on time
18:26 / 18:38≈ on time ≈ +1 min
18:41≈ on time ≈ +1 min
18:44≈ on time ≈ +1 min
18:48≈ on time ≈ +1 min
18:51≈ on time ≈ +1 min
18:53≈ on time ≈ +1 min
18:56 / 18:58≈ on time ≈ +1 min
19:03≈ on time ≈ +1 min
19:07on 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
Mon 16 NovGelterkinden 17:54Partial coverage0 min—
Sun 15 NovLaufen 19:080 min—
Sat 14 NovLaufen 19:080 min—
Fri 13 NovLaufen 19:080 min—
Thu 12 NovLaufen 19:08+1 min—
Wed 11 NovLaufen 19:09+1 min—
Tue 10 NovLaufen 19:070 min—
Mon 9 NovLaufen 19:09+1 min+1 min
Sun 8 NovLaufen 19:080 min—
Sat 7 NovLaufen 19:070 min—
Fri 6 NovLaufen 19:080 min—
Thu 5 NovLaufen 19:080 min—
Wed 4 NovLaufen 19:080 min—
Tue 3 NovLaufen 19:080 min—
Mon 2 NovLaufen 19:090 min—
Sun 1 NovLaufen 19:09+1 min+1 min
Sat 31 OctLaufen 19:080 min—
Fri 30 OctLaufen 19:10+2 min+2 min
Thu 29 OctLaufen 19:080 min—
Wed 28 OctLaufen 19:080 min—
Tue 27 OctLaufen 19:080 min—
Mon 26 OctLaufen 19:080 min—
Sun 25 OctLaufen 19:080 min—
Sat 24 OctLaufen 19:080 min—
Fri 23 OctLaufen 19:080 min—
Thu 22 OctLaufen 19:080 min—
Wed 21 OctLaufen 19:080 min—
Tue 20 OctLaufen 19:14+6 min+6 min
Mon 19 OctLaufen 19:070 min—
Sun 18 OctLaufen 19:080 min—