S3 17387 Laufen – Olten
Alerts for train 17387
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line S3.
It has not run yet today
Last recorded run: Thursday 12 November 0 min
Next service: today 22:50 from Laufen · Fri 13 Nov
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 29 Aug Max en route +4 min · last fix heading to Olten +4 min
Distribution · 90 days
64 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 31% · 20
- On time 67% · 43
- 3–10 min 2% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=9
- 100% T n=11
- 100% W n=10
- 100% T n=7
- 100% F n=10
- 90% S n=10
- 100% S n=7
Stops and timetable
Timetable of the latest run from the operator’s GTFS (19 stops).
Last 90 days, 64 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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 22:50 | on time | on time | |
| 22:54 | ≈ on time | ≈ on time | |
| 23:00 | ≈ on time | ≈ on time | |
| 23:02 | ≈ on time | ≈ on time | |
| 23:06 | ≈ on time | ≈ on time | |
| 23:09 | ≈ on time | ≈ on time | |
| 23:12 | ≈ on time | ≈ on time | |
| 23:15 | ≈ on time | ≈ +1 min | |
| 23:19 / 23:30 | ≈ on time | ≈ +1 min | |
| 23:36 | ≈ on time | ≈ +1 min | |
| 23:40 | ≈ on time | ≈ +1 min | |
| 23:43 | ≈ on time | ≈ +1 min | |
| 23:47 | ≈ on time | ≈ +1 min | |
| 23:50 | ≈ on time | ≈ +1 min | |
| 23:52 | ≈ on time | ≈ +1 min | |
| 23:55 | ≈ on time | ≈ +1 min | |
| 23:58 | ≈ on time | ≈ +1 min | |
| 00:02 | ≈ on time | ≈ +1 min | |
| 00:12 | on 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Thu 12 Nov | Olten 00:14 | 0 min | — |
| Wed 11 Nov | Olten 00:14 | +2 min | +2 min |
| Tue 10 Nov | Olten 00:13 | −1 min | — |
| Mon 9 Nov | Olten 00:12 | −1 min | — |
| Sun 8 Nov | Olten 00:13 | No data | — |
| Sat 7 Nov | Olten 00:09 | −1 min | — |
| Fri 6 Nov | Olten 00:09 | 0 min | — |
| Thu 5 Nov | Olten 00:09 | −1 min | — |
| Wed 4 Nov | Olten 00:13 | +1 min | — |
| Tue 3 Nov | Olten 00:12 | −1 min | +2 min |
| Mon 2 Nov | Olten 00:12 | −1 min | — |
| Sun 1 Nov | Olten 00:12 | −2 min | — |
| Sat 31 Oct | Olten 00:11 | 0 min | — |
| Fri 30 Oct | Olten 00:11 | 0 min | — |
| Thu 29 Oct | Olten 00:11 | −2 min | — |
| Wed 28 Oct | Olten 00:12 | −1 min | — |
| Tue 27 Oct | Olten 00:12 | −1 min | — |
| Mon 26 Oct | Olten 00:12 | −1 min | +3 min |
| Sun 25 Oct | Olten 00:11 | −1 min | — |
| Sat 24 Oct | Olten 00:11 | 0 min | — |
| Fri 23 Oct | Olten 00:11 | 0 min | — |
| Thu 22 Oct | Olten 00:12 | −2 min | — |
| Wed 21 Oct | Olten 00:12 | −1 min | +2 min |
| Tue 20 Oct | Olten 00:11 | −2 min | +2 min |
| Mon 19 Oct | Olten 00:12 | −1 min | +2 min |
| Sun 18 Oct | Tecknau 00:02 | +1 min | — |
| Sat 17 Oct | Tecknau 00:02 | +1 min | +1 min |
| Fri 16 Oct | Olten 00:11 | 0 min | +1 min |
| Thu 15 Oct | Olten 00:11 | −2 min | — |
| Wed 14 Oct | Olten 00:15 | +2 min | +2 min |