Train Arriva 32014 Maastricht Randwyck – Kerkrade Centrum

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

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 07:05 from Maastricht Randwyck · Thu 5 Nov

Next departure 07:05 today · Maastricht Randwyck
On-time · 30 days
100%
26/26 runs under 3 min
RT coverage: 0 full · 26 partial · 2 no data
On-time · 90 days
100%
27/27 runs under 3 min
RT coverage: 0 full · 27 partial · 60 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

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

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

On-time by weekday

  • 100% M n=3
  • 100% T n=5
  • 100% W n=4
  • 100% T n=4
  • 100% F n=4
  • 100% S n=4
  • 100% S n=3

Stops and timetable

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

Last 90 days, 27 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
07:05on time on time
07:08 / 07:11— —
07:14— —
07:17— —
07:21— —
07:24— —
07:28 / 07:29— —
07:32— —
07:35— —
07:38— —
07:41 / 07:45— —
07:49— —
07:52— —
07:54— —
07: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
Wed 4 NovChevremont 08:09Partial coverage0 min—
Tue 3 NovChevremont 08:18Partial coverage+1 min—
Mon 2 NovChevremont 08:09No data—
Sun 1 NovChevremont 08:09Partial coverage0 min—
Sat 31 OctChevremont 08:11Partial coverage+1 min+1 min
Fri 30 OctChevremont 08:10Partial coverage0 min—
Thu 29 OctChevremont 08:10Partial coverage0 min—
Wed 28 OctChevremont 08:10Partial coverage0 min—
Tue 27 OctChevremont 08:09Partial coverage0 min—
Mon 26 OctChevremont 08:11Partial coverage+1 min—
Sun 25 OctChevremont 08:11No data—
Sat 24 OctChevremont 08:10Partial coverage0 min—
Fri 23 OctChevremont 08:10Partial coverage0 min—
Thu 22 OctChevremont 08:10Partial coverage0 min—
Wed 21 OctChevremont 08:10Partial coverage0 min—
Tue 20 OctChevremont 08:10Partial coverage0 min—
Mon 19 OctChevremont 08:11Partial coverage0 min—
Sun 18 OctChevremont 08:09Partial coverage0 min—
Sat 17 OctChevremont 08:10Partial coverage0 min—
Fri 16 OctChevremont 08:12Partial coverage0 min—
Thu 15 OctChevremont 08:10Partial coverage0 min—
Tue 13 OctChevremont 08:10Partial coverage0 min—
Mon 12 OctChevremont 08:11Partial coverage0 min—
Sun 11 OctChevremont 08:09Partial coverage0 min—
Sat 10 OctChevremont 08:10Partial coverage0 min—
Fri 9 OctChevremont 08:10Partial coverage0 min—
Thu 8 OctChevremont 08:10Partial coverage0 min—
Wed 7 OctChevremont 08:09Partial coverage0 min—
Tue 6 OctChevremont 08:10Partial coverage0 min—
Mon 5 OctChevremont 08:10No data—