Train Arriva 32016 Maastricht Randwyck – Kerkrade Centrum

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

✓ Today’s run finished

Today, last fix heading to Chevremont at 08:44 +6 min

  1. Maastricht Randwyck07:35
  2. Maastricht Noord07:44
  3. Valkenburg07:54
  4. Klimmen-Ransdaal08:02
  5. Heerlen Woonboulevard08:08
  6. Chevremont08:24
  7. Kerkrade Centrum08:27

Next service: tomorrow 07:35 from Maastricht Randwyck · Wed 11 Nov

Next departure 07:35 tomorrow · Maastricht Randwyck
On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 0 full · 18 partial · 11 no data
On-time · 90 days
96%
23/24 runs under 3 min
RT coverage: 0 full · 24 partial · 64 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +1 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

  • Tue 10 Nov Max en route +6 min · last fix heading to Chevremont +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 23
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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