Train Arriva 32055 Kerkrade Centrum – Maastricht Randwyck

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

It has not run yet today

Last recorded run: Friday 6 November +1 min

Next service: today 17:31 from Kerkrade Centrum · Sat 7 Nov

Next departure 17: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
88%
14/16 runs under 3 min
RT coverage: 1 full · 15 partial · 71 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

  • Sun 18 Oct Max en route +4 min · last fix heading to Maastricht +4 min
  • Sat 10 Oct Max en route +4 min · last fix heading to Maastricht +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 14
  • 3–10 min 13% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=2
  • 100% W n=2
  • 100% T n=1
  • 100% F n=2
  • 67% S n=3
  • 67% S n=3

Stops and timetable

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

Last 90 days, 16 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
17:31on time on time
17:33— —
17:36— —
17:39— —
17:43 / 17:54— —
17:57— —
18:00— —
18:04— —
18:07— —
18:10 / 18:11— —
18:14— —
18:17— —
18:20— —
18:23 / 18:27— —
18: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
Fri 6 NovMaastricht 18:40Partial coverage+1 min—
Thu 5 NovValkenburg 18:24No data—
Wed 4 NovHouthem-St. Gerlach 18:28No data—
Tue 3 NovValkenburg 18:24No data—
Mon 2 NovSchin op Geul 18:19No data—
Sun 1 NovMaastricht 18:43Partial coverage+2 min+2 min
Sat 31 OctMaastricht 18:43Partial coverage+2 min+3 min
Fri 30 OctMaastricht 18:41No data—
Thu 29 OctVoerendaal 18:14No data—
Wed 28 OctValkenburg 18:32Partial coverage0 min—
Tue 27 OctKlimmen-Ransdaal 18:18No data—
Mon 26 OctSchin op Geul 18:35Partial coverage0 min—
Sun 25 OctMaastricht 18:52No data—
Sat 24 OctMaastricht 18:51Partial coverage0 min—
Fri 23 OctMaastricht 18:47No data—
Thu 22 OctMaastricht 18:41No data—
Wed 21 OctMaastricht 18:41No data—
Tue 20 OctMaastricht 18:41Partial coverage0 min—
Mon 19 OctMaastricht 18:41No data—
Sun 18 OctMaastricht 18:46Partial coverage+4 min+4 min
Sat 17 OctMaastricht 18:41No data—
Fri 16 OctMaastricht 18:41No data—
Thu 15 OctMaastricht 18:41No data—
Tue 13 OctMaastricht 18:41No data—
Mon 12 OctMaastricht 18:41Partial coverage0 min—
Sun 11 OctMaastricht 18:41Partial coverage0 min—
Sat 10 OctMaastricht 18:45Partial coverage+4 min+4 min
Fri 9 OctMaastricht 18:41Partial coverage0 min+8 min
Thu 8 OctVoerendaal 18:140 min—
Wed 7 OctSchin op Geul 18:21Partial coverage0 min—