S6 87724 Konstanz – Engen
Alerts for train 87724
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line S6.
It does not run today
Last recorded run: Sunday 8 November No data
Next service: tomorrow 23:23 from Konstanz · Sat 14 Nov
Last 30 days
Arrival delay at Engen, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Sun 16 Aug Max en route +12 min · last fix heading to Engen +12 min
Distribution · 90 days
5 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 80% · 4
- 3–10 min 0% · 0
- 10–30 min 20% · 1
- 30+ min 0% · 0
On-time by weekday
- 100% M n=1
- — T n=0
- 100% W n=1
- 100% T n=1
- 100% F n=1
- — S n=0
- 0% S n=1
Stops and timetable
Timetable of the latest run from the operator’s GTFS (16 stops).
Last 90 days, 5 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 |
|---|---|---|---|
| 23:23 | on time | +1 min | |
| 23:26 | ≈ on time | ≈ +1 min | |
| 23:27 / 23:28 | ≈ on time | ≈ +1 min | |
| 23:29 / 23:30 | ≈ on time | ≈ +1 min | |
| 23:32 | ≈ on time | ≈ +2 min | |
| 23:34 / 23:35 | ≈ on time | ≈ +2 min | |
| 23:37 / 23:38 | ≈ on time | ≈ +3 min | |
| 23:41 / 23:42 | ≈ on time | ≈ +3 min | |
| 23:44 / 23:46 | ≈ on time | ≈ +4 min | |
| 23:49 | ≈ on time | ≈ +5 min | |
| 23:52 / 23:53 | ≈ on time | ≈ +5 min | |
| 23:56 / 00:00 | ≈ on time | ≈ +6 min | |
| 00:02 | ≈ +1 min | ≈ +7 min | |
| 00:06 / 00:07 | ≈ +1 min | ≈ +7 min | |
| 00:09 / 00:10 | ≈ +1 min | ≈ +8 min | |
| 00:12 | +1 min | +8 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 | Engen 01:13 | No data | — |
| Sat 7 Nov | Engen 01:13 | No data | — |
| Sun 1 Nov | Engen 01:13 | No data | — |
| Sat 31 Oct | Engen 01:13 | No data | — |
| Sun 25 Oct | Engen 02:13 | No data | — |
| Sat 24 Oct | Engen 01:13 | No data | — |
| Sun 18 Oct | Engen 01:14 | No data | — |
| Sat 17 Oct | Engen 01:13 | No data | — |
| Sun 11 Oct | Engen 01:13 | No data | — |
| Sat 10 Oct | Engen 01:14 | No data | — |
| Mon 5 Oct | Engen 01:14 | No data | — |
| Sun 4 Oct | Engen 01:13 | No data | — |
| Fri 2 Oct | Engen 01:11 | +1 min | +3 min |
| Thu 1 Oct | Engen 01:12 | +1 min | +2 min |
| Wed 30 Sept | Engen 01:12 | −1 min | +4 min |
| Mon 17 Aug | Engen 01:11 | +2 min | +2 min |
| Sun 16 Aug | Engen 01:11 | +12 min | +12 min |