Train Arriva 32481 Sittard – Maastricht Randwyck

Sittard 22:31 → Maastricht Randwyck 22:55 Daily 0 h 24 min · 6 stops Arriva

Running now · updated 22:25

Position estimated from the timetable

Heading to Maastricht Randwyck 0 min

Estimated arrival at Maastricht Randwyck 22:55

  1. Sittard22:31
  2. Geleen-Lutterade22:35
  3. Beek-Elsloo22:39
  4. Bunde22:44
  5. Maastricht22:50
  6. Maastricht Randwyck22:55

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

On-time · 30 days
100%
7/7 runs under 3 min
RT coverage: 5 full · 2 partial · 4 no data
On-time · 90 days
100%
11/11 runs under 3 min
RT coverage: 9 full · 2 partial · 19 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

Distribution · 90 days

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

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

On-time by weekday

  • — M n=0
  • — T n=0
  • 100% W n=1
  • — T n=0
  • 100% F n=2
  • 100% S n=3
  • 100% S n=5

Stops and timetable

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

Last 90 days, 11 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
22:31on time on time
22:35≈ on time ≈ on time
22:39≈ on time ≈ on time
22:44 / 22:45≈ on time ≈ +1 min
22:50 / 22:52≈ on time ≈ +1 min
22:55on time +1 min

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
Sun 15 NovSittard 22:24Partial coverage0 min—
Sat 14 NovMaastricht 23:04Partial coverage0 min—
Fri 13 Nov— 22:58+1 min+1 min
Sun 8 NovMaastricht 23:040 min—
Sat 7 NovMaastricht 23:040 min—
Sun 1 NovMaastricht 23:040 min—
Sat 31 OctMaastricht 23:06No data—
Sun 25 OctMaastricht 23:07No data—
Sat 24 OctBeek-Elsloo 22:48No data—
Sun 18 OctMaastricht 23:07+1 min—
Sat 17 OctMaastricht 23:06No data—
Tue 13 Oct— 22:58No data—
Sun 11 OctMaastricht 23:07+1 min—
Sat 10 OctRoermond 22:180 min—
Fri 9 Oct— 22:59+2 min+2 min
Wed 7 Oct— 22:570 min—
Sun 4 OctMaastricht 23:06No data—
Sat 3 OctMaastricht 23:06No data—
Sun 27 SeptMaastricht 23:06No data—
Sat 26 SeptMaastricht 23:06No data—
Sun 20 SeptMaastricht 23:06No data—
Sat 19 SeptMaastricht 23:06No data—
Sun 13 SeptMaastricht 23:06No data—
Sat 12 SeptMaastricht 23:06No data—
Sun 6 SeptMaastricht 23:06No data—
Sat 5 SeptMaastricht 23:06No data—
Sun 30 AugMaastricht 23:06No data—
Sat 29 AugBeek-Elsloo 22:53No data—
Sun 23 AugMaastricht 23:06No data—
Sat 22 AugMaastricht 23:06No data—