P11 83260 Muellheim (Baden) – Mulhouse
Alerts for train 83260
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 it reached Mulhouse at 07:27 0 min
- Muellheim (Baden)07:03
- Neuenburg (Baden)07:07
- Bantzenheim07:15
- Mulhouse07:27
Next service: tomorrow 07:03 from Muellheim (Baden) · Thu 12 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
- Thu 22 Oct Max en route +60 min · last fix heading to Mulhouse +60 min
- Thu 5 Nov Max en route +45 min · last fix heading to Mulhouse +45 min
- Tue 27 Oct Max en route +20 min · last fix heading to Mulhouse +20 min
Distribution · 90 days
27 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 89% · 24
- 3–10 min 0% · 0
- 10–30 min 4% · 1
- 30+ min 7% · 2
On-time by weekday
- 100% M n=5
- 83% T n=6
- 100% W n=6
- 60% T n=5
- 100% F n=5
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (4 stops).
Last 90 days, 27 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 |
|---|---|---|---|
| 07:03 | on time | on time | |
| 07:07 / 07:08 | ≈ on time | ≈ +1 min | |
| 07:15 | ≈ on time | ≈ +4 min | |
| 07:27 | on time | +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 |
|---|---|---|---|
| Wed 11 Nov | Mulhouse 07:28 | 0 min | — |
| Tue 10 Nov | Mulhouse 07:28 | 0 min | — |
| Mon 9 Nov | Mulhouse 07:28 | 0 min | — |
| Fri 6 Nov | Mulhouse 07:29 | 0 min | — |
| Thu 5 Nov | Mulhouse 08:13 | +45 min | +45 min |
| Wed 4 Nov | Mulhouse 07:28 | 0 min | — |
| Tue 3 Nov | Mulhouse 07:29 | 0 min | — |
| Mon 2 Nov | Mulhouse 07:28 | 0 min | — |
| Fri 30 Oct | Mulhouse 07:28 | 0 min | — |
| Thu 29 Oct | Mulhouse 07:28 | 0 min | — |
| Wed 28 Oct | Mulhouse 07:28 | 0 min | — |
| Tue 27 Oct | Mulhouse 07:48 | +20 min | +20 min |
| Mon 26 Oct | Mulhouse 07:28 | 0 min | — |
| Fri 23 Oct | Mulhouse 07:28 | 0 min | — |
| Thu 22 Oct | Mulhouse 08:28 | +60 min | +60 min |
| Wed 21 Oct | Mulhouse 07:28 | 0 min | — |
| Tue 20 Oct | Mulhouse 07:28 | 0 min | — |
| Fri 16 Oct | Mulhouse 07:29 | 0 min | — |
| Thu 15 Oct | Mulhouse 07:29 | 0 min | — |
| Wed 14 Oct | Mulhouse 07:28 | 0 min | — |
| Tue 13 Oct | Mulhouse 07:28 | 0 min | — |
| Mon 12 Oct | Mulhouse 07:28 | 0 min | — |
| Fri 9 Oct | Mulhouse 07:29 | 0 min | — |
| Thu 8 Oct | Mulhouse 07:28 | 0 min | — |
| Wed 7 Oct | Mulhouse 07:29 | 0 min | — |
| Tue 6 Oct | Mulhouse 07:29 | 0 min | — |
| Mon 5 Oct | StopPoint:OCETrain TE~cef89d1b 07:29 | 0 min | — |