S3 17333 Laufen → Olten

View line S3

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

Running now · updated 09:29

Position estimated from the timetable

Between Zwingen and Grellingen 0 min

Estimated arrival at Olten 10:40 · 51 km/h

  1. Laufen09:20
  2. Zwingen09:24
  3. Grellingen09:30
  4. Duggingen09:32
  5. Münchenstein09:42
  6. Muttenz10:06
  7. Olten10:40

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

On-time · 30 days
100%
28/28 runs under 3 min
RT coverage: 27 full · 1 partial · 2 no data
On-time · 90 days
97%
76/78 runs under 3 min
RT coverage: 77 full · 1 partial · 6 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

Worst days

  • Sun 11 Oct Max en route +22 min · last fix heading to Olten +22 min
  • Fri 4 Sept Max en route +6 min · last fix heading to Olten +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 76
  • 3–10 min 1% · 1
  • 10–30 min 1% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=11
  • 100% T n=11
  • 100% W n=12
  • 100% T n=9
  • 92% F n=12
  • 100% S n=12
  • 91% S n=11

Stops and timetable

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

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