S3 17357 Laufen – Olten

View line S3

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

✓ Today’s run finished

Today it reached Olten at 16:40 0 min

  1. Laufen15:20
  2. Duggingen15:32
  3. Münchenstein15:42
  4. Muttenz16:06
  5. Liestal16:17
  6. Sissach16:25
  7. Olten16:40

Next service: tomorrow 15:20 from Laufen · Fri 6 Nov

Next departure 15:20 tomorrow · Laufen
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
97%
61/63 runs under 3 min
RT coverage: 63 full · 0 partial · 4 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

  • Fri 23 Oct Max en route +4 min · last fix heading to Olten +4 min
  • Fri 21 Aug Max en route +3 min · last fix heading to Olten +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 61
  • 3–10 min 3% · 2
  • 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=8
  • 75% F n=8
  • 100% S n=8
  • 100% S n=10

Stops and timetable

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

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