S3 17328 Olten – Laufen

View line S3

Olten 20:17 → Laufen 21:37 Daily 1 h 20 min · 19 stops SBB CFF FFS

✓ Today’s run finished

Today it reached Laufen at 21:39 +2 min

  1. Olten20:17
  2. Sissach20:31
  3. Liestal20:39
  4. Muttenz20:50
  5. Münchenstein21:14
  6. Duggingen21:23
  7. Laufen21:37

Next service: tomorrow 20:17 from Olten · Tue 17 Nov

Next departure 20:17 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%
58/58 runs under 3 min
RT coverage: 58 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

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 58 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
20:17on time on time
20:24≈ on time ≈ on time
20:27≈ on time ≈ on time
20:31≈ on time ≈ on time
20:33≈ on time ≈ on time
20:35≈ on time ≈ on time
20:39 / 20:40≈ on time ≈ on time
20:43≈ on time ≈ on time
20:46 / 20:47≈ on time ≈ on time
20:50≈ on time ≈ on time
20:56 / 21:08≈ on time ≈ on time
21:11≈ on time ≈ on time
21:14≈ on time ≈ on time
21:18≈ on time ≈ on time
21:21≈ on time ≈ on time
21:23≈ on time ≈ +1 min
21:26 / 21:28≈ on time ≈ +1 min
21:33≈ on time ≈ +1 min
21:37on 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 NovLaufen 09:39+2 min+2 min
Sun 15 NovLaufen 09:380 min—
Sat 14 NovLaufen 09:380 min—
Fri 13 NovLaufen 09:380 min—
Thu 12 NovLaufen 09:380 min—
Wed 11 NovLaufen 09:380 min—
Tue 10 NovLaufen 09:380 min—
Mon 9 NovLaufen 09:380 min—
Sun 8 NovLaufen 09:380 min—
Sat 7 NovLaufen 09:39+1 min+1 min
Fri 6 NovLaufen 09:380 min—
Thu 5 NovLaufen 09:380 min—
Wed 4 NovLaufen 09:380 min—
Tue 3 NovLaufen 09:380 min—
Mon 2 NovLaufen 09:380 min—
Sun 1 NovLaufen 09:380 min—
Sat 31 OctLaufen 09:37−1 min—
Fri 30 OctLaufen 09:37−1 min—
Thu 29 OctLaufen 09:380 min—
Wed 28 OctLaufen 09:380 min—
Tue 27 OctLaufen 09:40+1 min+2 min
Mon 26 OctOlten 11:010 min—
Sun 25 OctLaufen 09:380 min—
Sat 24 OctLaufen 09:380 min—
Fri 23 OctLaufen 09:380 min—
Thu 22 OctLaufen 09:380 min—
Wed 21 OctLaufen 09:41+3 min+3 min
Tue 20 OctLaufen 09:380 min—
Mon 19 OctLaufen 09:380 min—
Sun 18 OctLaufen 09:380 min—