S3 17316 Olten – Laufen
Alerts for train 17316
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.
✓ Today’s run finished
Today it reached Laufen at 06:37 0 min
- Olten05:17
- Sissach05:31
- Liestal05:39
- Muttenz05:50
- Münchenstein06:14
- Duggingen06:23
- Laufen06:37
Next service: tomorrow 05:17 from Olten · Fri 20 Nov
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
61 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 61
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=8
- 100% T n=9
- 100% W n=11
- 100% T n=9
- 100% F n=10
- 100% S n=7
- 100% S n=7
Stops and timetable
Timetable of the latest run from the operator’s GTFS (19 stops).
Last 90 days, 61 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 |
|---|---|---|---|
| 05:17 | on time | on time | |
| 05:24 | ≈ on time | ≈ on time | |
| 05:27 | ≈ on time | ≈ on time | |
| 05:31 | ≈ on time | ≈ on time | |
| 05:33 | ≈ on time | ≈ on time | |
| 05:35 | ≈ on time | ≈ on time | |
| 05:39 / 05:40 | ≈ on time | ≈ on time | |
| 05:43 | ≈ on time | ≈ on time | |
| 05:46 / 05:47 | ≈ on time | ≈ on time | |
| 05:50 | ≈ on time | ≈ on time | |
| 05:56 / 06:08 | ≈ on time | ≈ on time | |
| 06:11 | ≈ on time | ≈ on time | |
| 06:14 | ≈ on time | ≈ on time | |
| 06:18 | ≈ on time | ≈ on time | |
| 06:21 | ≈ on time | ≈ +1 min | |
| 06:23 | ≈ on time | ≈ +1 min | |
| 06:26 / 06:28 | ≈ on time | ≈ +1 min | |
| 06:33 | ≈ on time | ≈ +1 min | |
| 06:37 | 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 19 Nov | Laufen 06:39 | 0 min | — |
| Wed 18 Nov | Laufen 06:38 | 0 min | — |
| Tue 17 Nov | Laufen 06:38 | 0 min | — |
| Mon 16 Nov | Laufen 06:38 | 0 min | — |
| Sun 15 Nov | Laufen 06:38 | 0 min | — |
| Sat 14 Nov | Laufen 06:38 | 0 min | — |
| Fri 13 Nov | Laufen 06:38 | 0 min | — |
| Thu 12 Nov | Laufen 06:38 | 0 min | — |
| Wed 11 Nov | Laufen 06:38 | 0 min | — |
| Tue 10 Nov | Laufen 06:38 | 0 min | — |
| Mon 9 Nov | Laufen 06:38 | 0 min | — |
| Sun 8 Nov | Laufen 06:39 | No data | — |
| Sat 7 Nov | Laufen 06:39 | +1 min | +1 min |
| Fri 6 Nov | Laufen 06:39 | 0 min | — |
| Thu 5 Nov | Laufen 06:38 | 0 min | — |
| Wed 4 Nov | Laufen 06:38 | 0 min | — |
| Tue 3 Nov | Laufen 06:38 | 0 min | — |
| Mon 2 Nov | Laufen 06:38 | 0 min | — |
| Sun 1 Nov | Laufen 06:37 | −1 min | — |
| Sat 31 Oct | Laufen 06:38 | 0 min | — |
| Fri 30 Oct | Laufen 06:38 | 0 min | — |
| Thu 29 Oct | Laufen 06:39 | 0 min | — |
| Wed 28 Oct | Laufen 06:39 | 0 min | — |
| Tue 27 Oct | Laufen 06:38 | 0 min | — |
| Mon 26 Oct | Laufen 06:38 | 0 min | — |
| Sun 25 Oct | Laufen 06:38 | No data | — |
| Sat 24 Oct | Laufen 06:38 | 0 min | — |
| Fri 23 Oct | Laufen 06:38 | 0 min | — |
| Thu 22 Oct | Laufen 06:40 | +1 min | +1 min |
| Wed 21 Oct | Laufen 06:41 | +3 min | +3 min |