Train Arriva 32051 Kerkrade Centrum – Maastricht Randwyck
✓ Today’s run finished
Today, last fix heading to Maastricht at 17:39 0 min
- Kerkrade Centrum16:31
- Eygelshoven16:36
- Heerlen Woonboulevard16:57
- Klimmen-Ransdaal17:04
- Valkenburg17:10
- Maastricht17:23
- Maastricht Randwyck17:30
Next service: tomorrow 16:31 from Kerkrade Centrum · Sat 7 Nov
Last 30 days
Arrival delay at Maastricht Randwyck, 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
17 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 17
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=2
- 100% T n=2
- 100% W n=3
- 100% T n=2
- 100% F n=2
- 100% S n=3
- 100% S n=3
Stops and timetable
Timetable of the latest run from the operator’s GTFS (15 stops).
Last 90 days, 17 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 |
|---|---|---|---|
| 16:31 | on time | on time | |
| 16:33 | — | — | |
| 16:36 | — | — | |
| 16:39 | — | — | |
| 16:43 / 16:54 | — | — | |
| 16:57 | — | — | |
| 17:00 | — | — | |
| 17:04 | — | — | |
| 17:07 | — | — | |
| 17:10 / 17:11 | — | — | |
| 17:14 | — | — | |
| 17:17 | — | — | |
| 17:20 | — | — | |
| 17:23 / 17:27 | — | — | |
| 17:30 | — | — |
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 6 Nov | Maastricht 17:39Partial coverage | 0 min | — |
| Thu 5 Nov | Maastricht 17:39 | No data | — |
| Wed 4 Nov | Maastricht 17:39Partial coverage | 0 min | — |
| Tue 3 Nov | Maastricht 17:39 | No data | — |
| Mon 2 Nov | Maastricht 17:39 | No data | — |
| Sun 1 Nov | Maastricht 17:42Partial coverage | 0 min | — |
| Sat 31 Oct | Maastricht 17:43Partial coverage | +2 min | +2 min |
| Fri 30 Oct | Maastricht 17:44 | No data | — |
| Thu 29 Oct | Maastricht 17:33Partial coverage | 0 min | — |
| Wed 28 Oct | Maastricht 17:41Partial coverage | 0 min | — |
| Tue 27 Oct | Maastricht 17:41 | No data | — |
| Mon 26 Oct | Maastricht 17:41 | No data | — |
| Sun 25 Oct | Maastricht 17:46 | No data | — |
| Sat 24 Oct | Maastricht 17:45Partial coverage | 0 min | — |
| Fri 23 Oct | Maastricht 17:41 | No data | — |
| Thu 22 Oct | Maastricht 17:44 | No data | — |
| Wed 21 Oct | Maastricht 17:42 | No data | — |
| Tue 20 Oct | Maastricht 17:41Partial coverage | 0 min | — |
| Mon 19 Oct | Maastricht 17:41 | No data | — |
| Sun 18 Oct | Maastricht 17:41Partial coverage | 0 min | — |
| Sat 17 Oct | Maastricht 17:41 | No data | — |
| Fri 16 Oct | Maastricht 17:41 | No data | — |
| Thu 15 Oct | Maastricht 17:41 | No data | — |
| Tue 13 Oct | Maastricht 17:41 | No data | — |
| Mon 12 Oct | Maastricht 17:41Partial coverage | 0 min | — |
| Sun 11 Oct | Maastricht 17:41Partial coverage | 0 min | — |
| Sat 10 Oct | Maastricht 17:42Partial coverage | +1 min | +1 min |
| Fri 9 Oct | Maastricht 17:41Partial coverage | 0 min | — |
| Thu 8 Oct | Maastricht 17:34Partial coverage | 0 min | — |
| Wed 7 Oct | Maastricht 17:41Partial coverage | +1 min | +1 min |