P14 832793 Kruth – Mulhouse
Alerts for train 832793
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line P14.
It does not run today
Last recorded run: Friday 13 November 0 min
Next service: Monday 18:36 from Kruth · Mon 16 Nov
Last 30 days
Arrival delay at Mulhouse, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Wed 4 Nov Max en route +10 min · last fix heading to Mulhouse +10 min
- Thu 12 Nov Max en route +5 min · last fix heading to Mulhouse +5 min
Distribution · 90 days
18 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 89% · 16
- 3–10 min 6% · 1
- 10–30 min 6% · 1
- 30+ min 0% · 0
On-time by weekday
- 100% M n=4
- 100% T n=4
- 67% W n=3
- 67% T n=3
- 100% F n=4
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (17 stops).
Last 90 days, 18 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 |
|---|---|---|---|
| 18:36 | on time | on time | |
| 18:38 | ≈ on time | ≈ on time | |
| 18:41 / 18:42 | ≈ on time | ≈ on time | |
| 18:43 / 18:48 | ≈ on time | ≈ on time | |
| 18:50 / 18:51 | ≈ on time | ≈ on time | |
| 18:53 | ≈ on time | ≈ on time | |
| 18:56 / 18:57 | ≈ on time | ≈ +1 min | |
| 19:00 | ≈ on time | ≈ +1 min | |
| 19:02 / 19:03 | ≈ on time | ≈ +1 min | |
| 19:06 / 19:07 | ≈ on time | ≈ +1 min | |
| 19:09 | ≈ on time | ≈ +1 min | |
| 19:10 / 19:11 | ≈ on time | ≈ +1 min | |
| 19:13 | ≈ on time | ≈ +1 min | |
| 19:15 / 19:17 | ≈ on time | ≈ +1 min | |
| 19:20 / 19:22 | ≈ on time | ≈ +1 min | |
| 19:31 | ≈ on time | ≈ +1 min | |
| 19:35 | on time | +2 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 |
|---|---|---|---|
| Fri 13 Nov | Mulhouse 19:34 | 0 min | — |
| Thu 12 Nov | Mulhouse 19:39 | +5 min | +5 min |
| Wed 11 Nov | Mulhouse 19:34 | No data | — |
| Tue 10 Nov | Mulhouse 19:34 | 0 min | +5 min |
| Mon 9 Nov | Mulhouse 19:34 | 0 min | — |
| Fri 6 Nov | Mulhouse 19:35 | 0 min | — |
| Wed 4 Nov | Mulhouse 19:44 | +10 min | +10 min |
| Tue 3 Nov | Mulhouse 19:37 | 0 min | — |
| Mon 2 Nov | Mulhouse 19:34 | 0 min | — |
| Fri 16 Oct | Mulhouse 19:36 | 0 min | — |
| Thu 15 Oct | Mulhouse 19:36 | 0 min | — |
| Wed 14 Oct | Mulhouse 19:36 | 0 min | — |
| Tue 13 Oct | Mulhouse 19:37 | 0 min | — |
| Mon 12 Oct | Mulhouse 19:36 | 0 min | — |
| Fri 9 Oct | Mulhouse 19:36 | 0 min | — |
| Thu 8 Oct | Mulhouse 19:37 | 0 min | — |
| Wed 7 Oct | Mulhouse 19:36 | 0 min | — |
| Tue 6 Oct | Mulhouse 19:36 | 0 min | — |
| Mon 5 Oct | Mulhouse 19:36 | 0 min | — |