S3 17367 Laufen – Olten

View line S3

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

Running now · updated 19:10

Position estimated from the timetable

Between Tecknau and Olten 0 min

Estimated arrival at Olten 19:10 · 69 km/h

  1. Laufen17:50
  2. Duggingen18:02
  3. Münchenstein18:12
  4. Muttenz18:36
  5. Liestal18:47
  6. Tecknau19:02
  7. Olten19:10

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

On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
98%
83/85 runs under 3 min
RT coverage: 85 full · 0 partial · 2 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

Worst days

  • Wed 7 Oct Max en route +14 min · last fix heading to Olten +14 min
  • Wed 11 Nov Max en route +12 min · last fix heading to Olten +12 min

Distribution · 90 days

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

  • Early 1% · 1
  • On time 96% · 82
  • 3–10 min 0% · 0
  • 10–30 min 2% · 2
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 85 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
17:50on time on timePassed
17:54≈ on time ≈ on timePassed
18:00≈ on time ≈ on timePassed
18:02≈ on time ≈ on timePassed
18:06≈ on time ≈ on timePassed
18:09≈ on time ≈ +1 minPassed
18:12≈ on time ≈ +1 minPassed
18:15≈ on time ≈ +1 minPassed
18:19 / 18:30≈ on time ≈ +1 minPassed
18:36≈ on time ≈ +1 minPassed
18:40≈ on time ≈ +1 minPassed
18:43≈ on time ≈ +1 minPassed
18:47≈ on time ≈ +1 minPassed
18:50≈ on time ≈ +2 minPassed
18:52≈ on time ≈ +2 minPassed
18:55≈ on time ≈ +2 minPassed
18:58≈ on time ≈ +2 minPassed
19:02≈ on time ≈ +2 minPassed
19:10on time +2 minNext

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
Tue 17 NovOlten 19:090 min—
Mon 16 NovOlten 19:090 min—
Sun 15 NovTecknau 19:03+2 min+2 min
Sat 14 NovTecknau 18:590 min+2 min
Fri 13 NovOlten 19:13+2 min+2 min
Thu 12 NovOlten 19:110 min—
Wed 11 NovOlten 19:23+12 min+12 min
Tue 10 NovOlten 19:13+2 min+2 min
Mon 9 NovOlten 19:09−1 min—
Sun 8 NovOlten 19:090 min—
Sat 7 NovOlten 19:090 min—
Fri 6 NovOlten 19:13+2 min+2 min
Thu 5 NovOlten 19:09−1 min—
Wed 4 NovOlten 19:12+1 min+1 min
Tue 3 NovOlten 19:13+1 min+1 min
Mon 2 NovOlten 19:14+3 min+3 min
Sun 1 NovOlten 19:120 min—
Sat 31 OctOlten 19:110 min—
Fri 30 OctOlten 19:14+3 min+3 min
Thu 29 OctOlten 19:110 min—
Wed 28 OctOlten 19:12+1 min—
Tue 27 OctOlten 19:13+2 min+2 min
Mon 26 OctOlten 19:110 min—
Sun 25 OctOlten 19:13+2 min+2 min
Sat 24 OctOlten 19:12+1 min+1 min
Fri 23 OctOlten 19:12+1 min—
Thu 22 OctOlten 19:110 min—
Wed 21 OctOlten 19:110 min—
Tue 20 OctOlten 19:120 min—
Mon 19 OctOlten 19:110 min—