P11 83268 Müllheim im Markgräflerland – Mulhouse
Alerts for train 83268
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line P11.
✓ Today’s run finished
Today, last fix heading to Mulhouse at 13:28 No data
- Müllheim im Markgräflerland13:03
- Neuenburg(Baden)13:07
- Bantzenheim13:14
- Mulhouse13:27
Next service: tomorrow 13:03 from Müllheim im Markgräflerland · Sun 15 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 28 Oct Max en route +40 min · last fix heading to Mulhouse +40 min
- Sun 18 Oct Max en route +5 min · last fix heading to Mulhouse +5 min
Distribution · 90 days
38 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 95% · 36
- 3–10 min 3% · 1
- 10–30 min 0% · 0
- 30+ min 3% · 1
On-time by weekday
- 100% M n=3
- 100% T n=6
- 83% W n=6
- 100% T n=2
- 100% F n=5
- 100% S n=9
- 86% S n=7
Stops and timetable
Timetable of the latest run from the operator’s GTFS (4 stops).
Last 90 days, 38 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 |
|---|---|---|---|
| 13:03 | on time | on time | |
| 13:07 / 13:08 | ≈ on time | ≈ on time | |
| 13:14 / 13:15 | ≈ on time | ≈ on time | |
| 13:27 | 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 |
|---|---|---|---|
| Sat 14 Nov | Mulhouse 13:28 | No data | — |
| Fri 13 Nov | Mulhouse 13:28 | No data | — |
| Thu 12 Nov | Mulhouse 13:28 | No data | — |
| Wed 11 Nov | Mulhouse 13:28 | No data | — |
| Tue 10 Nov | Mulhouse 13:28 | No data | — |
| Mon 9 Nov | Mulhouse 13:28 | No data | — |
| Sun 8 Nov | Mulhouse 13:28 | 0 min | — |
| Sat 7 Nov | Mulhouse 13:28 | 0 min | — |
| Fri 6 Nov | Mulhouse 13:28 | 0 min | — |
| Thu 5 Nov | Mulhouse 13:28 | No data | — |
| Wed 4 Nov | Mulhouse 13:28 | 0 min | — |
| Tue 3 Nov | Mulhouse 13:28 | 0 min | — |
| Mon 2 Nov | Mulhouse 13:28 | No data | — |
| Sun 1 Nov | Mulhouse 13:28 | 0 min | — |
| Sat 31 Oct | Mulhouse 13:28 | 0 min | — |
| Fri 30 Oct | Mulhouse 13:28 | 0 min | — |
| Thu 29 Oct | Mulhouse 13:28 | No data | — |
| Wed 28 Oct | Mulhouse 14:08 | +40 min | +40 min |
| Tue 27 Oct | Mulhouse 13:28 | 0 min | — |
| Mon 26 Oct | Mulhouse 13:28 | No data | — |
| Sun 25 Oct | Mulhouse 13:28 | 0 min | — |
| Sat 24 Oct | Mulhouse 13:28 | 0 min | — |
| Fri 23 Oct | Mulhouse 13:28 | 0 min | — |
| Thu 22 Oct | Mulhouse 13:28 | No data | — |
| Wed 21 Oct | Mulhouse 13:28 | 0 min | — |
| Tue 20 Oct | Mulhouse 13:28 | 0 min | — |
| Mon 19 Oct | Mulhouse 13:28 | No data | — |
| Sun 18 Oct | Mulhouse 13:33 | +5 min | +5 min |
| Sat 17 Oct | Mulhouse 13:28 | 0 min | — |
| Fri 16 Oct | Mulhouse 13:29 | 0 min | — |