S3 17320 Olten – Laufen

View line S3

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

Running now · updated 06:25

Position estimated from the timetable

Between Tecknau and Gelterkinden 0 min

Estimated arrival at Laufen 07:37 · 81 km/h

  1. Olten06:17
  2. Tecknau06:24
  3. Gelterkinden06:27
  4. Sissach06:31
  5. Liestal06:39
  6. Muttenz06:50
  7. Laufen07:37

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

On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 29 full · 1 partial · 0 no data
On-time · 90 days
93%
51/55 runs under 3 min
RT coverage: 54 full · 1 partial · 0 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: +1 min

Last 30 days

Arrival delay at Laufen, 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 11 Sept Max en route +11 min · last fix heading to Grellingen +11 min
  • Thu 5 Nov Max en route +6 min · last fix heading to Laufen +5 min
  • Sun 18 Oct Max en route +4 min · last fix heading to Laufen +4 min
  • Tue 6 Oct Max en route +3 min · last fix heading to Laufen +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 51
  • 3–10 min 5% · 3
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=10
  • 88% T n=8
  • 100% W n=6
  • 86% T n=7
  • 86% F n=7
  • 100% S n=8
  • 89% S n=9

Stops and timetable

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

Last 90 days, 55 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
06:17on time on timePassed
06:24≈ on time ≈ on timePassed
06:27≈ on time ≈ on timeNext
06:31≈ on time ≈ on time
06:33≈ on time ≈ on time
06:35≈ on time ≈ on time
06:39 / 06:40≈ on time ≈ on time
06:43≈ on time ≈ on time
06:46 / 06:47≈ on time ≈ on time
06:50≈ on time ≈ +1 min
06:56 / 07:08≈ on time ≈ +1 min
07:11≈ on time ≈ +1 min
07:14≈ on time ≈ +1 min
07:18≈ on time ≈ +1 min
07:21≈ on time ≈ +1 min
07:23≈ on time ≈ +1 min
07:26 / 07:28≈ on time ≈ +1 min
07:33≈ on time ≈ +2 min
07:37on 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
Tue 17 NovGelterkinden 06:24Partial coverage0 min—
Mon 16 NovLaufen 07:380 min—
Sun 15 NovLaufen 07:380 min—
Sat 14 NovLaufen 07:380 min—
Fri 13 NovLaufen 07:380 min—
Thu 12 NovLaufen 07:390 min+47 min
Wed 11 NovLaufen 07:39+1 min—
Tue 10 NovLaufen 07:380 min—
Mon 9 NovLaufen 07:380 min—
Sun 8 NovLaufen 07:380 min—
Sat 7 NovLaufen 07:39+1 min—
Fri 6 NovLaufen 07:380 min—
Thu 5 NovLaufen 07:43+5 min+6 min
Wed 4 NovLaufen 07:380 min—
Tue 3 NovLaufen 07:390 min—
Mon 2 NovLaufen 07:380 min—
Sun 1 NovLaufen 07:380 min—
Sat 31 OctLaufen 07:370 min—
Fri 30 OctLaufen 07:380 min—
Thu 29 OctLaufen 07:380 min—
Wed 28 OctLaufen 07:380 min—
Tue 27 OctLaufen 07:380 min—
Mon 26 OctLaufen 07:370 min—
Sun 25 OctLaufen 07:380 min—
Sat 24 OctLaufen 07:380 min—
Fri 23 OctLaufen 07:39+1 min+1 min
Thu 22 OctLaufen 07:39+1 min—
Wed 21 OctLaufen 07:40+1 min+1 min
Tue 20 OctLaufen 07:390 min—
Mon 19 OctLaufen 07:380 min—