P15 831138 Colmar – Munster
Alerts for train 831138
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line P15.
It has not run yet today
Last recorded run: Wednesday 4 November 0 min
Next service: today 19:49 from Colmar · Thu 5 Nov
Last 30 days
Arrival delay at Munster, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Fri 16 Oct Max en route +30 min · last fix heading to Munster +30 min
- Tue 13 Oct Max en route +5 min · last fix heading to Munster +5 min
Distribution · 90 days
13 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 85% · 11
- 3–10 min 8% · 1
- 10–30 min 0% · 0
- 30+ min 8% · 1
On-time by weekday
- 100% M n=3
- 67% T n=3
- 100% W n=3
- 100% T n=2
- 50% F n=2
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (12 stops).
Last 90 days, 13 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 |
|---|---|---|---|
| 19:49 | on time | +4 min | |
| 19:51 | ≈ on time | ≈ +4 min | |
| 19:53 | ≈ on time | ≈ +4 min | |
| 19:55 / 19:56 | ≈ on time | ≈ +4 min | |
| 19:58 / 19:59 | ≈ on time | ≈ +4 min | |
| 20:01 / 20:03 | ≈ on time | ≈ +4 min | |
| 20:05 / 20:06 | ≈ on time | ≈ +4 min | |
| 20:09 | ≈ on time | ≈ +4 min | |
| 20:12 | ≈ on time | ≈ +4 min | |
| 20:15 / 20:16 | ≈ on time | ≈ +4 min | |
| 20:18 / 20:19 | ≈ on time | ≈ +4 min | |
| 20:21 | on time | +4 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 4 Nov | Munster 20:22 | 0 min | — |
| Tue 3 Nov | Munster 20:23 | 0 min | — |
| Mon 2 Nov | Munster 20:22 | 0 min | — |
| Fri 16 Oct | Munster 20:52 | +30 min | +30 min |
| Thu 15 Oct | Munster 20:22 | 0 min | — |
| Wed 14 Oct | Munster 20:22 | 0 min | — |
| Tue 13 Oct | Munster 20:27 | +5 min | +5 min |
| Mon 12 Oct | Munster 20:22 | 0 min | — |
| Fri 9 Oct | Munster 20:22 | 0 min | — |
| Thu 8 Oct | Munster 20:22 | 0 min | — |
| Wed 7 Oct | Munster 20:22 | 0 min | — |
| Tue 6 Oct | Munster 20:22 | 0 min | — |
| Mon 5 Oct | Munster 20:22 | 0 min | — |