S3 17322 Olten – Laufen

View line S3

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

✓ Today’s run finished

Today it reached Laufen at 14:07 0 min

  1. Olten12:48
  2. Sissach13:02
  3. Liestal13:10
  4. Muttenz13:20
  5. Münchenstein13:44
  6. Duggingen13:53
  7. Laufen14:07

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

Next departure 12:48 tomorrow · Olten
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
96%
44/46 runs under 3 min
RT coverage: 46 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 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

  • Fri 11 Sept Max en route +10 min · last fix heading to Grellingen +9 min
  • Fri 9 Oct Max en route +3 min · last fix heading to Laufen +3 min

Distribution · 90 days

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

  • Early 4% · 2
  • On time 91% · 42
  • 3–10 min 4% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=8
  • 100% W n=9
  • 100% T n=8
  • 60% F n=5
  • 100% S n=4
  • 100% S n=6

Stops and timetable

Timetable of the latest run from the operator’s GTFS (19 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
12:48on time on time
12:55≈ on time ≈ on time
12:58≈ on time ≈ on time
13:02≈ on time ≈ on time
13:04≈ on time ≈ on time
13:06≈ on time ≈ on time
13:10≈ on time ≈ on time
13:13≈ on time ≈ on time
13:16 / 13:17≈ on time ≈ on time
13:20≈ on time ≈ on time
13:26 / 13:38≈ on time ≈ on time
13:41≈ on time ≈ +1 min
13:44≈ on time ≈ +1 min
13:48≈ on time ≈ +1 min
13:51≈ on time ≈ +1 min
13:53≈ on time ≈ +1 min
13:56 / 13:58≈ on time ≈ +1 min
14:03≈ on time ≈ +1 min
14: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
Thu 5 NovLaufen 08:080 min—
Wed 4 NovLaufen 08:080 min—
Tue 3 NovLaufen 08:080 min—
Mon 2 NovLaufen 08:080 min—
Sun 1 NovLaufen 08:080 min—
Sat 31 OctLaufen 08:080 min—
Fri 30 OctLaufen 08:09+1 min—
Thu 29 OctLaufen 08:09+1 min—
Wed 28 OctLaufen 08:09+1 min—
Tue 27 OctLaufen 08:080 min—
Mon 26 OctLaufen 08:080 min—
Sun 25 OctLaufen 08:08+1 min—
Sat 24 OctLaufen 08:080 min—
Fri 23 OctLaufen 08:080 min—
Thu 22 OctLaufen 08:080 min—
Wed 21 OctLaufen 08:080 min—
Tue 20 OctLaufen 08:080 min—
Mon 19 OctLaufen 08:080 min—
Sun 18 OctLaufen 08:09+1 min+1 min
Sat 17 OctLaufen 08:080 min—
Fri 16 OctLaufen 08:080 min—
Thu 15 OctLaufen 08:080 min—
Wed 14 OctLaufen 08:080 min—
Tue 13 OctLaufen 08:080 min—
Mon 12 OctLaufen 08:08+1 min—
Sun 11 OctLaufen 08:080 min—
Sat 10 OctLaufen 08:080 min—
Fri 9 OctLaufen 08:11+3 min+3 min
Thu 8 OctLaufen 08:080 min—
Wed 7 OctLaufen 08:080 min—