S3 17341 Laufen – Olten

View line S3

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

✓ Today’s run finished

Today, last fix heading to Olten at 12:39 No data

  1. Laufen11:20
  2. Duggingen11:32
  3. Münchenstein11:42
  4. Muttenz12:06
  5. Liestal12:17
  6. Sissach12:25
  7. Olten12:40

Next service: tomorrow 11:20 from Laufen · Tue 17 Nov

Next departure 11:20 tomorrow · Laufen
On-time · 30 days
95%
21/22 runs under 3 min
RT coverage: 22 full · 0 partial · 8 no data
On-time · 90 days
98%
60/61 runs under 3 min
RT coverage: 61 full · 0 partial · 14 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

  • Fri 6 Nov Max en route +6 min · last fix heading to Olten +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 98% · 60
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=8
  • 100% W n=11
  • 100% T n=7
  • 90% F n=10
  • 100% S n=12
  • 100% S n=10

Stops and timetable

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

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