Train Arriva 32031 Kerkrade Centrum – Maastricht Randwyck

Kerkrade Centrum 11:31 → Maastricht Randwyck 12:30 Daily 0 h 59 min · 15 stops Arriva

✓ Today’s run finished

Today, last fix heading to Maastricht at 12:39 No data

  1. Kerkrade Centrum11:31
  2. Eygelshoven11:36
  3. Heerlen Woonboulevard11:57
  4. Klimmen-Ransdaal12:04
  5. Valkenburg12:10
  6. Maastricht12:23
  7. Maastricht Randwyck12:30

Next service: tomorrow 11:31 from Kerkrade Centrum · Sat 7 Nov

Next departure 11:31 tomorrow · Kerkrade Centrum
On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 0 full · 12 partial · 17 no data
On-time · 90 days
100%
15/15 runs under 3 min
RT coverage: 0 full · 15 partial · 73 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 min

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

15 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 0% · 0
  • On time 100% · 15
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=3
  • 100% W n=3
  • 100% T n=1
  • 100% F n=1
  • 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, 15 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.

StopSched.Usually 9 days in 10
11:31on time on time
11:33— —
11:36— —
11:39— —
11:43 / 11:54— —
11:57— —
12:00— —
12:04— —
12:07— —
12:10 / 12:11— —
12:14— —
12:17— —
12:20— —
12:23 / 12:27— —
12: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

DateLast stopFinalMax
Fri 6 NovMaastricht 12:39No data—
Thu 5 NovMaastricht 12:39No data—
Wed 4 NovMaastricht 12:39Partial coverage0 min—
Tue 3 NovMaastricht 12:39No data—
Mon 2 NovMaastricht 12:42No data—
Sun 1 NovMaastricht 12:42Partial coverage0 min—
Sat 31 OctMaastricht 12:41Partial coverage0 min—
Fri 30 OctMaastricht 12:41No data—
Thu 29 OctMaastricht 12:41No data—
Wed 28 OctMaastricht 12:41Partial coverage0 min—
Tue 27 OctMaastricht 12:42Partial coverage0 min—
Mon 26 OctMaastricht 12:41No data—
Sun 25 OctMaastricht 12:47No data—
Sat 24 OctMaastricht 12:41Partial coverage0 min—
Fri 23 OctMaastricht 12:41No data—
Thu 22 OctMaastricht 12:41No data—
Wed 21 OctMaastricht 12:41No data—
Tue 20 OctMaastricht 12:41Partial coverage0 min—
Mon 19 OctMaastricht 12:41No data—
Sun 18 OctMaastricht 12:41Partial coverage0 min—
Sat 17 OctMaastricht 12:41No data—
Fri 16 OctMaastricht 12:41No data—
Thu 15 OctMaastricht 12:50No data—
Tue 13 OctMaastricht 12:41No data—
Mon 12 OctMaastricht 12:45No data—
Sun 11 OctMaastricht 12:41Partial coverage0 min—
Sat 10 OctMaastricht 12:41Partial coverage0 min—
Fri 9 OctMaastricht 12:43Partial coverage+2 min+2 min
Thu 8 OctMaastricht 12:42Partial coverage+1 min—
Wed 7 OctMaastricht 12:42Partial coverage+1 min—