S3 17391 Laufen – Olten

View line S3

Laufen 23:50 → Olten 01:12 Daily 1 h 22 min · 19 stops SBB CFF FFS

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 23:50 from Laufen · Thu 5 Nov

Next departure 23:50 today · Laufen
On-time · 30 days
89%
25/28 runs under 3 min
RT coverage: 28 full · 0 partial · 0 no data
On-time · 90 days
91%
64/70 runs under 3 min
RT coverage: 70 full · 0 partial · 16 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: +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

  • Sat 26 Sept Max en route +7 min · last fix heading to Olten +6 min
  • Thu 22 Oct Max en route +11 min · last fix heading to Olten +6 min
  • Mon 12 Oct Max en route +4 min · last fix heading to Olten +3 min
  • Sun 9 Aug Max en route +9 min · last fix heading to Olten +3 min
  • Wed 30 Sept Max en route +4 min · last fix heading to Olten +3 min

Distribution · 90 days

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

  • Early 17% · 12
  • On time 74% · 52
  • 3–10 min 9% · 6
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 89% M n=9
  • 100% T n=11
  • 91% W n=11
  • 86% T n=7
  • 100% F n=11
  • 82% S n=11
  • 90% S n=10

Stops and timetable

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

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