S20 7718 Olten – Solothurn
Alerts for train 7718
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line S20.
✓ Today’s run finished
Today it reached Solothurn at 11:45 0 min
- Olten11:11
- Wangen bei Olten11:16
- Egerkingen11:21
- Oensingen11:28
- Niederbipp11:30
- Deitingen11:38
- Solothurn11:45
Next service: tomorrow 11:11 from Olten · Mon 9 Nov
Last 30 days
Arrival delay at Solothurn, 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
60 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 60
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=5
- 100% T n=9
- 100% W n=10
- 100% T n=5
- 100% F n=10
- 100% S n=12
- 100% S n=9
Stops and timetable
Timetable of the latest run from the operator’s GTFS (12 stops).
Last 90 days, 60 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 |
|---|---|---|---|
| 11:11 | on time | +1 min | |
| 11:13 | ≈ on time | ≈ on time | |
| 11:16 | ≈ on time | ≈ on time | |
| 11:17 / 11:18 | ≈ on time | ≈ on time | |
| 11:21 / 11:22 | ≈ on time | ≈ +1 min | |
| 11:24 | ≈ on time | ≈ +1 min | |
| 11:28 | ≈ on time | ≈ +1 min | |
| 11:30 | ≈ on time | ≈ +1 min | |
| 11:35 / 11:36 | ≈ on time | ≈ +1 min | |
| 11:38 | ≈ on time | ≈ +1 min | |
| 11:41 | ≈ on time | ≈ +1 min | |
| 11:45 | 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 |
|---|---|---|---|
| Sun 8 Nov | Solothurn 11:44 | 0 min | — |
| Sat 7 Nov | Langendorf 11:49 | 0 min | — |
| Fri 6 Nov | Langendorf 11:52 | −1 min | — |
| Thu 5 Nov | Langendorf 11:52 | No data | — |
| Wed 4 Nov | Langendorf 11:52 | 0 min | — |
| Tue 3 Nov | Langendorf 11:49 | 0 min | — |
| Mon 2 Nov | Langendorf 11:52 | No data | — |
| Sun 1 Nov | Solothurn 11:46 | 0 min | — |
| Sat 31 Oct | Langendorf 11:52 | 0 min | — |
| Fri 30 Oct | Langendorf 11:52 | 0 min | — |
| Thu 29 Oct | Langendorf 11:52 | No data | — |
| Wed 28 Oct | Langendorf 11:52 | 0 min | — |
| Tue 27 Oct | Langendorf 11:52 | 0 min | — |
| Mon 26 Oct | Langendorf 11:53 | No data | — |
| Sun 25 Oct | Solothurn 11:46 | 0 min | — |
| Sat 24 Oct | Langendorf 11:51 | 0 min | — |
| Fri 23 Oct | Langendorf 11:52 | 0 min | — |
| Thu 22 Oct | Langendorf 11:52 | No data | — |
| Wed 21 Oct | Langendorf 11:52 | 0 min | — |
| Tue 20 Oct | Langendorf 11:52 | −1 min | — |
| Mon 19 Oct | Langendorf 11:52 | No data | — |
| Sun 18 Oct | Solothurn 11:47 | 0 min | — |
| Sat 17 Oct | Langendorf 11:52 | 0 min | — |
| Fri 16 Oct | Langendorf 11:53 | +2 min | +2 min |
| Thu 15 Oct | Langendorf 11:52 | No data | — |
| Wed 14 Oct | Langendorf 11:52 | 0 min | — |
| Tue 13 Oct | Langendorf 11:53 | 0 min | — |
| Mon 12 Oct | Langendorf 11:52 | No data | — |
| Sun 11 Oct | Solothurn 11:46 | 0 min | — |
| Sat 10 Oct | Langendorf 11:54 | +1 min | +1 min |