S3 17337 Laufen – Olten

View line S3

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

✓ Today’s run finished

Today it reached Olten at 11:42 +2 min

  1. Laufen10:20
  2. Duggingen10:32
  3. Münchenstein10:42
  4. Muttenz11:06
  5. Liestal11:17
  6. Sissach11:25
  7. Olten11:40

Next service: tomorrow 10:20 from Laufen · Thu 19 Nov

Next departure 10:20 tomorrow · Laufen
On-time · 30 days
93%
27/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
95%
70/74 runs under 3 min
RT coverage: 74 full · 0 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: +3 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

  • Thu 8 Oct Max en route +14 min · last fix heading to Olten +14 min
  • Wed 30 Sept Max en route +7 min · last fix heading to Olten +7 min
  • Tue 20 Oct Max en route +5 min · last fix heading to Olten +5 min
  • Sat 7 Nov Max en route +3 min · last fix heading to Olten +3 min

Distribution · 90 days

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

  • Early 1% · 1
  • On time 93% · 69
  • 3–10 min 4% · 3
  • 10–30 min 1% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=11
  • 90% T n=10
  • 91% W n=11
  • 88% T n=8
  • 100% F n=12
  • 91% S n=11
  • 100% S n=11

Stops and timetable

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

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