S3 17349 Laufen → Olten

View line S3

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

S3 17349 Laufen–Olten: final delay under 3 min on 24 of its 24 runs with data in the last 30 days (100%). Median final delay: 0 min. Running now, on time. Expected at Olten: 14:40. TrainsRadar data as of 22 Nov 2026, 14:33 (GMT+1).

Running now · updated 14:33

Position estimated from the timetable

Between Tecknau and Olten 0 min

Estimated arrival at Olten 14:40 · 83 km/h

  1. Laufen13:20
  2. Duggingen13:32
  3. Münchenstein13:42
  4. Muttenz14:06
  5. Liestal14:17
  6. Tecknau14:32
  7. Olten14:40

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

On-time · 30 days
100%
24/24 runs under 3 min
RT coverage: 23 full · 1 partial · 6 no data
On-time · 90 days
99%
66/67 runs under 3 min
RT coverage: 66 full · 1 partial · 12 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

  • Tue 6 Oct Max en route +5 min · last fix heading to Olten +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 99% · 66
  • 3–10 min 1% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 91% T n=11
  • 100% W n=10
  • 100% T n=4
  • 100% F n=12
  • 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, 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 10Today
13:20on time on timePassed
13:24≈ on time ≈ on timePassed
13:30≈ on time ≈ on timePassed
13:32≈ on time ≈ on timePassed
13:36≈ on time ≈ on timePassed
13:39≈ on time ≈ on timePassed
13:42≈ on time ≈ on timePassed
13:45≈ on time ≈ on timePassed
13:49 / 14:00≈ on time ≈ +1 minPassed
14:06≈ on time ≈ +1 minPassed
14:10≈ on time ≈ +1 minPassed
14:13≈ on time ≈ +1 minPassed
14:17≈ on time ≈ +1 minPassed
14:20≈ on time ≈ +1 minPassed
14:22≈ on time ≈ +1 minPassed
14:25≈ on time ≈ +1 minPassed
14:28≈ on time ≈ +1 minPassed
14:32≈ on time ≈ +1 minPassed
14:40on time +1 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
Sun 22 NovTecknau 14:29Partial coverage0 min—
Sat 21 NovOlten 14:42+1 min+1 min
Fri 20 NovOlten 14:390 min—
Thu 19 NovOlten 14:39No data—
Wed 18 NovOlten 14:390 min—
Tue 17 NovZwingen 13:230 min—
Mon 16 NovOlten 14:39No data—
Sun 15 NovTecknau 14:330 min—
Sat 14 NovTecknau 14:330 min—
Fri 13 NovOlten 14:390 min—
Thu 12 NovOlten 14:42No data—
Wed 11 NovOlten 14:390 min—
Tue 10 NovOlten 14:390 min—
Mon 9 NovOlten 14:39No data—
Sun 8 NovOlten 14:420 min—
Sat 7 NovOlten 14:390 min—
Fri 6 NovOlten 14:42+1 min—
Thu 5 NovOlten 14:39No data—
Wed 4 NovOlten 14:42+1 min+1 min
Tue 3 NovOlten 14:390 min—
Mon 2 NovOlten 14:39No data—
Sun 1 NovOlten 14:410 min—
Sat 31 OctOlten 14:410 min—
Fri 30 OctOlten 14:410 min—
Thu 29 OctOlten 14:410 min—
Wed 28 OctOlten 14:420 min—
Tue 27 OctOlten 14:420 min—
Mon 26 OctOlten 14:410 min—
Sun 25 OctOlten 14:43+2 min+3 min
Sat 24 OctOlten 14:41+1 min—