S3 17351 Laufen – Olten

View line S3

Laufen 13:50 → Olten 15:10 Daily 1 h 20 min · 19 stops SBB CFF FFS

✓ Today’s run finished

Today it reached Olten at 15:10 0 min

  1. Laufen13:50
  2. Duggingen14:02
  3. Münchenstein14:12
  4. Muttenz14:36
  5. Liestal14:47
  6. Sissach14:55
  7. Olten15:10

Next service: tomorrow 13:50 from Laufen · Fri 20 Nov

Next departure 13:50 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%
64/67 runs under 3 min
RT coverage: 67 full · 0 partial · 4 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

  • Mon 19 Oct Max en route +25 min · last fix heading to Olten +25 min
  • Wed 23 Sept Max en route +8 min · last fix heading to Liestal +7 min
  • Thu 12 Nov Max en route +4 min · last fix heading to Olten +4 min

Distribution · 90 days

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

  • Early 1% · 1
  • On time 94% · 63
  • 3–10 min 3% · 2
  • 10–30 min 1% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 67 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
13:50on time on time
13:54≈ on time ≈ on time
14:00≈ on time ≈ on time
14:02≈ on time ≈ on time
14:06≈ on time ≈ on time
14:09≈ on time ≈ on time
14:12≈ on time ≈ on time
14:15≈ on time ≈ on time
14:19 / 14:30≈ on time ≈ on time
14:36≈ on time ≈ +1 min
14:40≈ on time ≈ +1 min
14:43≈ on time ≈ +1 min
14:47≈ on time ≈ +1 min
14:50≈ on time ≈ +1 min
14:52≈ on time ≈ +1 min
14:55≈ on time ≈ +1 min
14:58≈ on time ≈ +1 min
15:02≈ on time ≈ +1 min
15:10on 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
Thu 19 NovOlten 15:090 min—
Wed 18 NovOlten 15:12+1 min+1 min
Tue 17 NovOlten 15:090 min—
Mon 16 NovOlten 15:090 min—
Sun 15 NovTecknau 14:590 min—
Sat 14 NovTecknau 14:590 min—
Fri 13 NovOlten 15:090 min—
Thu 12 NovOlten 15:13+4 min+4 min
Wed 11 NovOlten 15:090 min—
Tue 10 NovOlten 15:090 min—
Mon 9 NovOlten 15:090 min—
Sun 8 NovOlten 15:12+1 min+1 min
Sat 7 NovOlten 15:090 min—
Fri 6 NovOlten 15:090 min—
Thu 5 NovOlten 15:090 min—
Wed 4 NovOlten 15:09−1 min—
Tue 3 NovOlten 15:12+1 min—
Mon 2 NovOlten 15:120 min—
Sun 1 NovOlten 15:110 min—
Sat 31 OctOlten 15:110 min—
Fri 30 OctOlten 15:12+1 min+2 min
Thu 29 OctOlten 15:110 min—
Wed 28 OctOlten 15:110 min—
Tue 27 OctOlten 15:120 min—
Mon 26 OctOlten 15:110 min—
Sun 25 OctOlten 15:110 min—
Sat 24 OctOlten 15:110 min—
Fri 23 OctOlten 15:110 min—
Thu 22 OctOlten 15:110 min—
Wed 21 OctOlten 15:10−1 min—