S3 17326 Olten – Laufen

View line S3

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

✓ Today’s run finished

Today it reached Laufen at 09:07 0 min

  1. Olten07:48
  2. Sissach08:02
  3. Liestal08:10
  4. Muttenz08:20
  5. Münchenstein08:44
  6. Duggingen08:53
  7. Laufen09:07

Next service: tomorrow 07:48 from Olten · Fri 6 Nov

Next departure 07:48 tomorrow · Olten
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%
47/47 runs under 3 min
RT coverage: 47 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 47 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
07:48on time on time
07:55≈ on time ≈ on time
07:58≈ on time ≈ on time
08:02≈ on time ≈ on time
08:04≈ on time ≈ on time
08:06≈ on time ≈ on time
08:10≈ on time ≈ on time
08:13≈ on time ≈ on time
08:16 / 08:17≈ on time ≈ on time
08:20≈ on time ≈ on time
08:26 / 08:38≈ on time ≈ on time
08:41≈ on time ≈ on time
08:44≈ on time ≈ on time
08:48≈ on time ≈ on time
08:51≈ on time ≈ on time
08:53≈ on time ≈ on time
08:56 / 08:58≈ on time ≈ on time
09:03≈ on time ≈ on time
09:07on time on time

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