Train Arriva 32050 Maastricht Randwyck – Kerkrade Centrum

Maastricht Randwyck 16:05 → Kerkrade Centrum 16:57 Daily 0 h 52 min · 15 stops Arriva

It has not run yet today

Last recorded run: Friday 6 November +3 min

Next service: today 16:05 from Maastricht Randwyck · Sat 7 Nov

Next departure 16:05 today · Maastricht Randwyck
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 0 full · 13 partial · 15 no data
On-time · 90 days
100%
17/17 runs under 3 min
RT coverage: 0 full · 17 partial · 70 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 Kerkrade Centrum, 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=3
  • 100% W n=3
  • 100% T n=1
  • 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.

StopSched.Usually 9 days in 10
16:05on time on time
16:08 / 16:11— —
16:14— —
16:17— —
16:21— —
16:24— —
16:28 / 16:29— —
16:32— —
16:35— —
16:38— —
16:41 / 16:45— —
16:49— —
16:52— —
16:54— —
16:57— —

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 NovChevremont 17:12Partial coverage+3 min+3 min
Thu 5 NovChevremont 17:08No data—
Wed 4 NovChevremont 17:08Partial coverage0 min—
Tue 3 NovChevremont 17:08No data—
Mon 2 NovChevremont 17:08No data—
Sun 1 NovChevremont 17:10Partial coverage0 min—
Sat 31 OctChevremont 17:11Partial coverage+1 min+1 min
Fri 30 OctChevremont 17:11No data—
Thu 29 OctChevremont 17:08No data—
Wed 28 OctChevremont 17:08Partial coverage0 min—
Tue 27 OctChevremont 17:08Partial coverage0 min—
Mon 26 OctChevremont 17:11No data—
Sun 25 OctChevremont 17:16No data—
Sat 24 OctChevremont 17:10Partial coverage0 min—
Fri 23 OctChevremont 17:16No data—
Thu 22 OctChevremont 17:11No data—
Wed 21 OctChevremont 17:10No data—
Tue 20 OctChevremont 17:10Partial coverage0 min—
Mon 19 OctChevremont 17:10No data—
Sun 18 OctChevremont 17:10Partial coverage0 min—
Sat 17 OctChevremont 17:11No data—
Fri 16 OctChevremont 17:11No data—
Thu 15 OctChevremont 17:10No data—
Tue 13 OctChevremont 17:10No data—
Mon 12 OctChevremont 17:10Partial coverage0 min—
Sun 11 OctChevremont 17:10Partial coverage+1 min—
Sat 10 OctChevremont 17:10Partial coverage0 min—
Fri 9 OctChevremont 17:10Partial coverage0 min—
Thu 8 OctChevremont 17:08Partial coverage0 min—
Wed 7 OctChevremont 17:08Partial coverage0 min—