S3 17321 Laufen → Olten

View line S3

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

S3 17321 Laufen–Olten: final delay under 3 min on 29 of its 30 runs with data in the last 30 days (97%). Median final delay: +1 min. TrainsRadar data as of 22 Nov 2026, 22:56 (GMT+1).

✓ Today’s run finished

Today it reached Olten at 07:42 +2 min

  1. Laufen06:20
  2. Duggingen06:32
  3. Münchenstein06:42
  4. Muttenz07:06
  5. Liestal07:17
  6. Sissach07:25
  7. Olten07:40

Next service: tomorrow 06:20 from Laufen · Mon 23 Nov

Next departure 06: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
96%
65/68 runs under 3 min
RT coverage: 68 full · 0 partial · 8 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 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

  • Thu 8 Oct Max en route +4 min · last fix heading to Olten +4 min
  • Wed 28 Oct Max en route +3 min · last fix heading to Olten +3 min
  • Wed 26 Aug Max en route +3 min · last fix heading to Olten +3 min

Distribution · 90 days

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

  • Early 1% · 1
  • On time 94% · 64
  • 3–10 min 4% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=8
  • 78% W n=9
  • 89% T n=9
  • 100% F n=11
  • 100% S n=11
  • 100% S n=13

Stops and timetable

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

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