S3 17345 Laufen – Olten
Alerts for train 17345
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 Olten at 13:40 0 min
- Laufen12:20
- Duggingen12:32
- Münchenstein12:42
- Muttenz13:06
- Liestal13:17
- Sissach13:25
- Olten13:40
Next service: tomorrow 12:20 from Laufen · Sun 8 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
Distribution · 90 days
57 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 57
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=4
- 100% T n=10
- 100% W n=9
- 100% T n=6
- 100% F n=11
- 100% 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, 57 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 |
|---|---|---|---|
| 12:20 | on time | on time | |
| 12:24 | ≈ on time | ≈ on time | |
| 12:30 | ≈ on time | ≈ on time | |
| 12:32 | ≈ on time | ≈ on time | |
| 12:36 | ≈ on time | ≈ on time | |
| 12:39 | ≈ on time | ≈ on time | |
| 12:42 | ≈ on time | ≈ on time | |
| 12:45 | ≈ on time | ≈ on time | |
| 12:49 / 13:00 | ≈ on time | ≈ on time | |
| 13:06 | ≈ on time | ≈ on time | |
| 13:10 | ≈ on time | ≈ on time | |
| 13:13 | ≈ on time | ≈ +1 min | |
| 13:17 | ≈ on time | ≈ +1 min | |
| 13:20 | ≈ on time | ≈ +1 min | |
| 13:22 | ≈ on time | ≈ +1 min | |
| 13:25 | ≈ on time | ≈ +1 min | |
| 13:28 | ≈ on time | ≈ +1 min | |
| 13:32 | ≈ on time | ≈ +1 min | |
| 13:40 | 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 |
|---|---|---|---|
| Sat 7 Nov | Olten 13:39 | 0 min | — |
| Fri 6 Nov | Olten 13:44 | +3 min | +3 min |
| Thu 5 Nov | Olten 13:39 | 0 min | — |
| Wed 4 Nov | Olten 13:42 | +1 min | — |
| Tue 3 Nov | Olten 13:42 | +1 min | — |
| Mon 2 Nov | Olten 13:39 | No data | — |
| Sun 1 Nov | Olten 13:41 | 0 min | — |
| Sat 31 Oct | Olten 13:41 | +1 min | — |
| Fri 30 Oct | Olten 13:41 | 0 min | +3 min |
| Thu 29 Oct | Olten 13:41 | No data | — |
| Wed 28 Oct | Olten 13:42 | 0 min | — |
| Tue 27 Oct | Olten 13:42 | +1 min | — |
| Mon 26 Oct | Olten 13:41 | No data | — |
| Sun 25 Oct | Olten 13:41 | 0 min | — |
| Sat 24 Oct | Olten 13:42 | +1 min | +1 min |
| Fri 23 Oct | Olten 13:41 | 0 min | — |
| Thu 22 Oct | Olten 13:41 | No data | — |
| Wed 21 Oct | Olten 13:42 | +1 min | — |
| Tue 20 Oct | Olten 13:42 | 0 min | — |
| Mon 19 Oct | Olten 13:41 | No data | — |
| Sun 18 Oct | Tecknau 13:33 | 0 min | — |
| Sat 17 Oct | Tecknau 13:33 | 0 min | — |
| Fri 16 Oct | Olten 13:42 | 0 min | — |
| Thu 15 Oct | Olten 13:41 | No data | — |
| Wed 14 Oct | Olten 13:42 | +1 min | +1 min |
| Tue 13 Oct | Olten 13:41 | 0 min | — |
| Mon 12 Oct | Olten 13:41 | No data | — |
| Sun 11 Oct | Olten 13:42 | +1 min | — |
| Sat 10 Oct | Olten 13:41 | −1 min | — |
| Fri 9 Oct | Olten 13:41 | 0 min | — |