Train Arriva 32415 Sittard – Maastricht Randwyck

Sittard 06:01 → Maastricht Randwyck 06:25 Mon, Tue, Wed, Thu, Fri 0 h 24 min · 6 stops Arriva

✓ Today’s run finished

Today, last fix heading to Maastricht at 06:37 0 min

  1. Sittard06:01
  2. Geleen-Lutterade06:05
  3. Beek-Elsloo06:09
  4. Bunde06:14
  5. Maastricht06:20
  6. Maastricht Randwyck06:25

Next service: tomorrow 06:01 from Sittard · Fri 6 Nov

Next departure 06:01 tomorrow · Sittard
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 0 full · 20 partial · 1 no data
On-time · 90 days
95%
20/21 runs under 3 min
RT coverage: 0 full · 21 partial · 41 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

  • Thu 15 Oct Max en route +9 min · last fix heading to Maastricht +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 20
  • 3–10 min 5% · 1
  • 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
  • 80% T n=5
  • 100% F n=4
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 21 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
06:01on time on time
06:05— —
06:09— —
06:14 / 06:15— —
06:20 / 06:22— —
06:25— —

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 06:37Partial coverage0 min—
Wed 4 NovMaastricht 06:34Partial coverage0 min—
Tue 3 NovMaastricht 06:34Partial coverage0 min—
Mon 2 NovMaastricht 06:38No data—
Fri 30 OctMaastricht 06:38Partial coverage+2 min+2 min
Thu 29 OctMaastricht 06:36Partial coverage0 min—
Wed 28 OctMaastricht 06:37Partial coverage+1 min—
Tue 27 OctMaastricht 06:36Partial coverage0 min—
Mon 26 OctMaastricht 06:36Partial coverage0 min—
Fri 23 OctMaastricht 06:36Partial coverage0 min—
Thu 22 OctMaastricht 06:36Partial coverage0 min—
Wed 21 OctMaastricht 06:36Partial coverage0 min—
Tue 20 OctMaastricht 06:36Partial coverage0 min—
Mon 19 OctMaastricht 06:36Partial coverage0 min—
Fri 16 OctMaastricht 06:36Partial coverage0 min—
Thu 15 OctMaastricht 06:44Partial coverage+8 min+9 min
Tue 13 OctMaastricht 06:37Partial coverage+1 min+1 min
Mon 12 OctMaastricht 06:36Partial coverage0 min+2 min
Fri 9 OctMaastricht 06:36Partial coverage+1 min—
Thu 8 OctMaastricht 06:37Partial coverage0 min—
Wed 7 OctMaastricht 06:36Partial coverage0 min—
Tue 6 OctMaastricht 06:36Partial coverage0 min—
Mon 5 OctMaastricht 06:38No data—
Fri 2 OctMaastricht 06:36No data—
Thu 1 OctMaastricht 06:36No data—
Wed 30 SeptMaastricht 06:37No data—
Tue 29 SeptMaastricht 06:36No data—
Mon 28 SeptMaastricht 06:36No data—
Fri 25 SeptMaastricht 06:36No data—
Thu 24 SeptMaastricht 06:36No data—