S3 17329 Laufen – Olten

View line S3

Laufen 08:20 → Olten 09:40 Daily 1 h 20 min · 19 stops SBB CFF FFS

✓ Today’s run finished

Today it reached Olten at 09:40 0 min

  1. Laufen08:20
  2. Duggingen08:32
  3. Münchenstein08:42
  4. Muttenz09:06
  5. Liestal09:17
  6. Sissach09:25
  7. Olten09:40

Next service: tomorrow 08:20 from Laufen · Sun 8 Nov

Next departure 08:20 tomorrow · Laufen
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%
67/67 runs under 3 min
RT coverage: 67 full · 0 partial · 7 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 Olten, 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

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

  • Early 3% · 2
  • On time 97% · 65
  • 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=10
  • 100% W n=11
  • 100% T n=9
  • 100% F n=10
  • 100% S n=11
  • 100% S n=8

Stops and timetable

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

Last 90 days, 67 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
08:20on time on time
08:24≈ on time ≈ on time
08:30≈ on time ≈ on time
08:32≈ on time ≈ on time
08:36≈ on time ≈ on time
08:39≈ on time ≈ on time
08:42≈ on time ≈ on time
08:45≈ on time ≈ on time
08:49 / 09:00≈ on time ≈ on time
09:06≈ on time ≈ +1 min
09:10≈ on time ≈ +1 min
09:13≈ on time ≈ +1 min
09:17≈ on time ≈ +1 min
09:20≈ on time ≈ +1 min
09:22≈ on time ≈ +1 min
09:25≈ on time ≈ +1 min
09:28≈ on time ≈ +1 min
09:32≈ on time ≈ +1 min
09:40on 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
Sat 7 NovOlten 09:390 min—
Fri 6 NovOlten 09:390 min—
Thu 5 NovOlten 09:390 min—
Wed 4 NovOlten 09:390 min—
Tue 3 NovOlten 09:42+1 min—
Mon 2 NovOlten 09:420 min—
Sun 1 NovOlten 09:410 min—
Sat 31 OctOlten 09:42+1 min+1 min
Fri 30 OctOlten 09:410 min—
Thu 29 OctOlten 09:410 min—
Wed 28 OctOlten 09:42+1 min+1 min
Tue 27 OctOlten 09:44+2 min+2 min
Mon 26 OctLaufen 11:010 min—
Sun 25 OctOlten 09:410 min—
Sat 24 OctOlten 09:42+1 min—
Fri 23 OctOlten 09:410 min—
Thu 22 OctOlten 09:44+3 min+3 min
Wed 21 OctOlten 09:410 min—
Tue 20 OctOlten 09:42+1 min—
Mon 19 OctOlten 09:410 min—
Sun 18 OctTecknau 09:330 min—
Sat 17 OctTecknau 09:330 min—
Fri 16 OctOlten 09:410 min—
Thu 15 OctOlten 09:410 min—
Wed 14 OctOlten 09:410 min—
Tue 13 OctOlten 09:410 min—
Mon 12 OctOlten 09:410 min—
Sun 11 OctOlten 09:410 min—
Sat 10 OctOlten 09:41−1 min—
Fri 9 OctOlten 09:410 min—