Train Arriva 32009 Kerkrade Centrum – Maastricht Randwyck

Kerkrade Centrum 06:01 → Maastricht Randwyck 07:00 Mon, Tue, Wed, Thu, Fri, Sat 0 h 59 min · 15 stops Arriva

✓ Today’s run finished

Today, last fix heading to Maastricht at 07:14 0 min

  1. Kerkrade Centrum06:01
  2. Eygelshoven06:06
  3. Heerlen Woonboulevard06:27
  4. Klimmen-Ransdaal06:34
  5. Valkenburg06:40
  6. Maastricht06:54
  7. Maastricht Randwyck07:00

Next service: tomorrow 06:01 from Kerkrade Centrum · Fri 6 Nov

Next departure 06:01 tomorrow · Kerkrade Centrum
On-time · 30 days
100%
24/24 runs under 3 min
RT coverage: 19 full · 5 partial · 1 no data
On-time · 90 days
100%
25/25 runs under 3 min
RT coverage: 20 full · 5 partial · 48 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

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

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

On-time by weekday

  • 100% M n=3
  • 100% T n=5
  • 100% W n=4
  • 100% T n=5
  • 100% F n=4
  • 100% S n=4
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (15 stops).

Last 90 days, 25 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
06:01on time on time
06:03≈ on time ≈ on time
06:06≈ on time ≈ on time
06:09≈ on time ≈ on time
06:13 / 06:24≈ on time ≈ on time
06:27≈ on time ≈ +1 min
06:30≈ on time ≈ +1 min
06:34≈ on time ≈ +1 min
06:37≈ on time ≈ +1 min
06:40 / 06:42≈ on time ≈ +1 min
06:45≈ on time ≈ +1 min
06:48≈ on time ≈ +1 min
06:51≈ on time ≈ +2 min
06:54 / 06:57≈ on time ≈ +2 min
07:00on time +2 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

DateLast stopFinalMax
Thu 5 NovMaastricht 07:14Partial coverage0 min—
Wed 4 NovMaastricht 07:090 min—
Tue 3 NovMaastricht 07:090 min—
Mon 2 NovMaastricht 07:12No data—
Sat 31 OctMaastricht 07:14+3 min+4 min
Fri 30 OctMaastricht 07:14+2 min+3 min
Thu 29 OctMaastricht 07:14Partial coverage+2 min+4 min
Wed 28 OctMaastricht 07:110 min—
Tue 27 OctMaastricht 07:110 min—
Mon 26 OctMaastricht 07:13+2 min+2 min
Sat 24 OctMaastricht 07:13+2 min+2 min
Fri 23 OctMaastricht 07:12+1 min—
Thu 22 OctMaastricht 07:11Partial coverage0 min—
Wed 21 OctMaastricht 07:120 min—
Tue 20 OctMaastricht 07:110 min—
Mon 19 OctMaastricht 07:110 min—
Sat 17 OctMaastricht 07:12+1 min—
Fri 16 OctMaastricht 07:110 min—
Thu 15 OctMaastricht 07:12Partial coverage+1 min—
Tue 13 OctMaastricht 07:110 min—
Mon 12 OctMaastricht 07:110 min—
Sat 10 OctMaastricht 07:110 min—
Fri 9 OctMaastricht 07:110 min—
Thu 8 OctMaastricht 07:11Partial coverage+1 min—
Wed 7 OctMaastricht 07:110 min—
Tue 6 OctMaastricht 07:120 min—
Mon 5 OctMaastricht 07:12No data—
Sat 3 OctMaastricht 07:11No data—
Fri 2 OctMaastricht 07:12No data—
Thu 1 OctMaastricht 07:11No data—