Train Arriva 32027 Kerkrade Centrum – Maastricht Randwyck

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

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 10:31 from Kerkrade Centrum · Fri 6 Nov

Next departure 10:31 today · Kerkrade Centrum
On-time · 30 days
83%
10/12 runs under 3 min
RT coverage: 0 full · 12 partial · 16 no data
On-time · 90 days
86%
12/14 runs under 3 min
RT coverage: 0 full · 14 partial · 73 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

Worst days

  • Sat 24 Oct Max en route +6 min · last fix heading to Maastricht +5 min
  • Fri 9 Oct Max en route +3 min · last fix heading to Maastricht +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 86% · 12
  • 3–10 min 14% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • 100% T n=2
  • 100% W n=3
  • 100% T n=2
  • 0% F n=1
  • 67% 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, 14 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
10:31on time on time
10:33— —
10:36— —
10:39— —
10:43 / 10:54— —
10:57— —
11:00— —
11:04— —
11:07— —
11:10 / 11:11— —
11:14— —
11:17— —
11:20— —
11:23 / 11:27— —
11: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
Thu 5 NovMaastricht 11:42No data—
Wed 4 NovMaastricht 11:39Partial coverage0 min—
Tue 3 NovMaastricht 11:40No data—
Mon 2 NovMaastricht 11:39No data—
Sun 1 NovMaastricht 11:42Partial coverage0 min—
Sat 31 OctMaastricht 11:42Partial coverage0 min—
Fri 30 OctMaastricht 11:41No data—
Thu 29 OctMaastricht 11:41Partial coverage0 min—
Wed 28 OctMaastricht 11:44Partial coverage0 min—
Tue 27 OctMaastricht 11:41No data—
Mon 26 OctMaastricht 11:41No data—
Sun 25 OctMaastricht 11:41No data—
Sat 24 OctMaastricht 11:46Partial coverage+5 min+6 min
Fri 23 OctMaastricht 11:41No data—
Thu 22 OctMaastricht 11:48No data—
Wed 21 OctMaastricht 11:42No data—
Tue 20 OctMaastricht 11:41Partial coverage0 min—
Mon 19 OctMaastricht 11:42No data—
Sun 18 OctMaastricht 11:41Partial coverage0 min—
Sat 17 OctMaastricht 11:41No data—
Fri 16 OctMaastricht 11:41No data—
Thu 15 OctMaastricht 11:42No data—
Tue 13 OctMaastricht 11:45No data—
Mon 12 OctMaastricht 11:41No data—
Sun 11 OctMaastricht 11:42Partial coverage+1 min+1 min
Sat 10 OctMaastricht 11:41Partial coverage0 min—
Fri 9 OctMaastricht 11:44Partial coverage+3 min+3 min
Thu 8 OctMaastricht 11:43Partial coverage+2 min+2 min
Wed 7 OctEygelshoven 12:01Partial coverage0 min—
Tue 6 OctMaastricht 11:42Partial coverage0 min—