Train Arriva 32068 Maastricht Randwyck – Kerkrade Centrum

Maastricht Randwyck 20:35 → Kerkrade Centrum 21:27 Daily 0 h 52 min · 15 stops Arriva

It has not run yet today

Last recorded run: Sunday 1 November 0 min

Next service: today 20:35 from Maastricht Randwyck · Fri 6 Nov

Next departure 20:35 today · Maastricht Randwyck
On-time · 30 days
83%
5/6 runs under 3 min
RT coverage: 2 full · 4 partial · 8 no data
On-time · 90 days
83%
5/6 runs under 3 min
RT coverage: 2 full · 4 partial · 26 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +5 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

Worst days

  • Fri 23 Oct Max en route +8 min · last fix heading to — +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 83% · 5
  • 3–10 min 17% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 6 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
20:35on time on time
20:38 / 20:41— —
20:44— —
20:47— —
20:51— —
20:54— —
20:58 / 20:59— —
21:02— —
21:05— —
21:08— —
21:11 / 21:15— —
21:19— —
21:22— —
21:24— —
21:27— —

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
Sun 1 NovChevremont 21:39Partial coverage0 min—
Sat 31 OctChevremont 21:39No data—
Wed 28 Oct— 21:30No data—
Mon 26 Oct— 21:38No data—
Sun 25 OctChevremont 21:40No data—
Sat 24 OctChevremont 21:38No data—
Fri 23 Oct— 21:39+8 min+8 min
Thu 22 Oct— 21:30No data—
Wed 21 Oct— 21:31No data—
Tue 20 Oct— 21:290 min—
Sun 18 OctChevremont 21:43Partial coverage+3 min+3 min
Sat 17 OctChevremont 21:42No data—
Sun 11 OctChevremont 21:40Partial coverage0 min—
Sat 10 OctChevremont 21:38Partial coverage0 min—
Sun 4 OctChevremont 21:39No data—
Sat 3 OctChevremont 21:40No data—
Sun 27 SeptChevremont 21:40No data—
Sat 26 SeptChevremont 21:41No data—
Sun 20 SeptChevremont 21:40No data—
Sat 19 SeptChevremont 21:40No data—
Sun 13 SeptChevremont 21:40No data—
Sat 12 SeptChevremont 21:40No data—
Sun 6 SeptChevremont 21:39No data—
Sat 5 SeptChevremont 21:40No data—
Sun 30 AugChevremont 21:40No data—
Sat 29 AugChevremont 21:38No data—
Sun 23 AugChevremont 21:40No data—
Sat 22 AugChevremont 21:39No data—
Fri 21 AugMaastricht Randwyck 20:49No data—
Sun 16 AugChevremont 21:40No data—