Train Arriva 32079 Kerkrade Centrum – Maastricht Randwyck

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

It has not run yet today

Last recorded run: Sunday 1 November +1 min

Next service: today 23:31 from Kerkrade Centrum · Sun 8 Nov

Next departure 23:31 today · Kerkrade Centrum
On-time · 30 days
100%
5/5 runs under 3 min
RT coverage: 3 full · 2 partial · 6 no data
On-time · 90 days
100%
5/5 runs under 3 min
RT coverage: 3 full · 2 partial · 18 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 5 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
23:31on time on time
23:33— —
23:36— —
23:39— —
23:43 / 23:54— —
23:57— —
00:00— —
00:04— —
00:07— —
00:10 / 00:11— —
00:14— —
00:17— —
00:20— —
00:23 / 00:27— —
00: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
Sun 1 NovMaastricht 00:42Partial coverage+1 min—
Wed 28 Oct— 00:33No data—
Mon 26 Oct— 00:320 min—
Sun 25 OctMaastricht 00:41No data—
Fri 23 Oct— 00:35+2 min+2 min
Thu 22 Oct— 00:35No data—
Wed 21 Oct— 00:39No data—
Tue 20 Oct— 00:32No data—
Sun 18 OctMaastricht 00:41Partial coverage0 min—
Sat 17 OctMaastricht 00:41No data—
Sun 11 OctMaastricht Noord 00:350 min—
Sun 4 OctMaastricht Noord 00:35No data—
Sat 3 OctMaastricht 00:41No data—
Sun 27 SeptMaastricht 00:42No data—
Sat 26 SeptLandgraaf 23:53No data—
Sun 20 SeptMaastricht 00:41No data—
Sun 13 SeptMaastricht 00:41No data—
Sat 12 SeptLandgraaf 23:53No data—
Sun 6 SeptMaastricht 00:41No data—
Sun 30 AugMaastricht 00:41No data—
Sun 23 AugMaastricht 00:42No data—
Sat 22 AugHeerlen Woonboulevard 00:11No data—
Sun 16 AugLandgraaf 23:55No data—