P14 832771 Wesserling – Mulhouse
Alerts for train 832771
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 has not run yet today
Last recorded run: Wednesday 4 November 0 min
Next service: today 10:49 from Wesserling · Fri 6 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
Distribution · 90 days
22 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 22
- 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=5
- 100% W n=4
- 100% T n=4
- 100% F n=4
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (14 stops).
Last 90 days, 22 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 |
|---|---|---|---|
| 10:49 | on time | on time | |
| 10:51 / 10:52 | ≈ on time | ≈ on time | |
| 10:54 | ≈ on time | ≈ on time | |
| 10:57 / 10:58 | ≈ on time | ≈ on time | |
| 11:00 / 11:01 | ≈ on time | ≈ on time | |
| 11:03 / 11:04 | ≈ on time | ≈ on time | |
| 11:07 | ≈ on time | ≈ on time | |
| 11:09 | ≈ on time | ≈ on time | |
| 11:10 / 11:11 | ≈ on time | ≈ on time | |
| 11:13 | ≈ on time | ≈ on time | |
| 11:15 / 11:17 | ≈ on time | ≈ on time | |
| 11:20 / 11:22 | ≈ on time | ≈ on time | |
| 11:31 | ≈ on time | ≈ on time | |
| 11:36 | on time | on time |
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 |
|---|---|---|---|
| Wed 4 Nov | Mulhouse 11:37 | 0 min | — |
| Tue 3 Nov | Mulhouse 11:37 | 0 min | — |
| Mon 2 Nov | Mulhouse 11:37 | 0 min | — |
| Fri 30 Oct | Mulhouse 11:37 | 0 min | — |
| Thu 29 Oct | Mulhouse 11:37 | 0 min | — |
| Tue 27 Oct | Mulhouse 11:37 | 0 min | — |
| Mon 26 Oct | Mulhouse 11:37 | 0 min | — |
| Fri 23 Oct | Mulhouse 11:37 | 0 min | — |
| Thu 22 Oct | Mulhouse 11:37 | 0 min | — |
| Wed 21 Oct | Mulhouse 11:37 | 0 min | — |
| Tue 20 Oct | Mulhouse 11:38 | 0 min | — |
| Mon 19 Oct | Mulhouse 11:37 | 0 min | — |
| Fri 16 Oct | Mulhouse 11:37 | 0 min | — |
| Thu 15 Oct | Mulhouse 11:37 | 0 min | — |
| Wed 14 Oct | Mulhouse 11:37 | 0 min | — |
| Tue 13 Oct | Mulhouse 11:37 | 0 min | — |
| Mon 12 Oct | Mulhouse 11:38 | 0 min | — |
| Fri 9 Oct | Mulhouse 11:38 | 0 min | — |
| Thu 8 Oct | Mulhouse 11:37 | 0 min | — |
| Wed 7 Oct | Mulhouse 11:37 | 0 min | — |
| Tue 6 Oct | Mulhouse 11:37 | 0 min | — |
| Mon 5 Oct | StopPoint:OCETrain TE~cef89d1b 11:37 | 0 min | — |