Train Arriva 32019 Kerkrade Centrum – Maastricht Randwyck

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

Running now · updated 09:20

Position estimated from the timetable

Heading to Maastricht Randwyck 0 min

Estimated arrival at Maastricht Randwyck 09:30 · 47 km/h

  1. Kerkrade Centrum08:31
  2. Eygelshoven08:36
  3. Heerlen Woonboulevard08:57
  4. Klimmen-Ransdaal09:04
  5. Valkenburg09:10
  6. Maastricht Noord09:20
  7. Maastricht Randwyck09:30

Today it is running no worse than usual: typical arrival delay is 0 min; 95% of the last 21 runs arrived on time.

On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 0 full · 21 partial · 9 no data
On-time · 90 days
97%
29/30 runs under 3 min
RT coverage: 0 full · 30 partial · 58 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

Worst days

  • Wed 18 Nov Max en route +5 min · last fix heading to Maastricht +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 29
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=5
  • 83% W n=6
  • 100% T n=4
  • 100% F n=2
  • 100% S n=6
  • 100% S n=5

Stops and timetable

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

Last 90 days, 30 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 10Today
08:31on time on time
08:33— —
08:36— —
08:39— —
08:43 / 08:54— —
08:57— —
09:00— —
09:04— —
09:07— —
09:10 / 09:11— —
09:14— —
09:17— —
09:20— —
09:23 / 09:27— —
09: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 19 NovMaastricht Noord 09:19Partial coverage0 min—
Wed 18 NovMaastricht 09:44Partial coverage+5 min+5 min
Tue 17 NovMaastricht 09:39Partial coverage0 min—
Mon 16 NovMaastricht 09:42Partial coverage+1 min+2 min
Sun 15 NovMaastricht 09:42Partial coverage+1 min—
Sat 14 NovMaastricht Noord 09:44Partial coverage0 min—
Fri 13 NovMaastricht 09:42Partial coverage0 min—
Thu 12 NovMaastricht 09:39Partial coverage0 min—
Wed 11 NovMaastricht 09:39Partial coverage0 min—
Tue 10 NovMaastricht 09:48Partial coverage0 min+7 min
Mon 9 NovMaastricht 09:44Partial coverage+2 min+3 min
Sun 8 NovMaastricht 09:39Partial coverage0 min—
Sat 7 NovMaastricht 09:42Partial coverage+1 min—
Fri 6 NovMaastricht 09:39No data—
Thu 5 NovMaastricht 10:02No data—
Wed 4 NovMaastricht 09:44Partial coverage0 min+2 min
Tue 3 NovMaastricht 09:39No data—
Mon 2 NovMaastricht 09:39No data—
Sun 1 NovMaastricht 09:41Partial coverage0 min—
Sat 31 OctMaastricht 09:41Partial coverage0 min—
Fri 30 OctMaastricht 09:41No data—
Thu 29 OctMaastricht 09:41Partial coverage0 min—
Wed 28 OctMaastricht 09:46Partial coverage0 min—
Tue 27 OctMaastricht 09:41Partial coverage0 min—
Mon 26 OctMaastricht 09:42No data—
Sun 25 OctMaastricht 09:41No data—
Sat 24 OctSchin op Geul 09:42Partial coverage0 min+11 min
Fri 23 OctMaastricht 09:41No data—
Thu 22 OctMaastricht 09:41No data—
Wed 21 OctMaastricht 09:41Partial coverage0 min—