S3 17316 Olten → Laufen

View line S3

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

S3 17316 Olten–Laufen: final delay under 3 min on 28 of its 28 runs with data in the last 30 days (100%). Median final delay: 0 min. Running now, on time. Expected at Laufen: 06:37. TrainsRadar data as of 22 Nov 2026, 06:18 (GMT+1).

Running now · updated 06:18

Position estimated from the timetable

Between Dornach-Arlesheim and Aesch BL 0 min

Estimated arrival at Laufen 06:37 · 41 km/h

  1. Olten05:17
  2. Sissach05:31
  3. Liestal05:39
  4. Muttenz05:50
  5. Dornach-Arlesheim06:18
  6. Aesch BL06:21
  7. Laufen06:37

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

On-time · 30 days
100%
28/28 runs under 3 min
RT coverage: 27 full · 1 partial · 2 no data
On-time · 90 days
100%
63/63 runs under 3 min
RT coverage: 62 full · 1 partial · 3 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: 0 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

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 100% · 63
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

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