S3 17385 Laufen – Olten

View line S3

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

Running now · updated 22:46

Position estimated from the timetable

Between Basel Dreispitz and Basel SBB 0 min

Estimated arrival at Olten 23:40 · 31 km/h

  1. Laufen22:20
  2. Duggingen22:32
  3. Münchenstein22:42
  4. Basel Dreispitz22:45
  5. Basel SBB22:49
  6. Muttenz23:06
  7. Olten23:40

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

On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 29 full · 1 partial · 0 no data
On-time · 90 days
100%
87/87 runs under 3 min
RT coverage: 86 full · 1 partial · 2 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: +2 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

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

  • Early 36% · 31
  • On time 64% · 56
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=12
  • 100% T n=12
  • 100% W n=13
  • 100% T n=11
  • 100% F n=13
  • 100% S n=13
  • 100% S n=13

Stops and timetable

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

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