Train Arriva 32482 Maastricht Randwyck – Sittard

Maastricht Randwyck 22:35 → Sittard 23:02 Daily 0 h 27 min · 6 stops Arriva

Running now · updated 22:47

Position estimated from the timetable

Heading to Sittard 0 min

Estimated arrival at Sittard 23:02 · 73 km/h

  1. Maastricht Randwyck22:35
  2. Maastricht22:38
  3. Bunde22:46
  4. Beek-Elsloo22:52
  5. Geleen-Lutterade22:55
  6. Sittard23:02

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

On-time · 30 days
100%
11/11 runs under 3 min
RT coverage: 9 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
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Sittard, 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

  • 100% M n=1
  • 100% T n=1
  • 100% W n=1
  • 100% T n=1
  • 100% F n=1
  • 100% S n=2
  • 100% S n=4

Stops and timetable

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

Last 90 days, 10 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:35on time on time
22:38 / 22:41≈ on time ≈ on time
22:46≈ on time ≈ on time
22:52≈ on time ≈ on time
22:55 / 22:57≈ on time ≈ on time
23:02on time on time

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 NovBunde 22:44Partial coverage0 min—
Sat 14 NovGeleen-Lutterade 23:09Partial coverage0 min—
Thu 12 Nov— 23:29+1 min+1 min
Tue 10 Nov— 22:390 min—
Sun 8 NovEcht 23:330 min—
Sat 7 NovEcht 23:240 min—
Fri 6 Nov— 23:290 min—
Wed 4 Nov— 23:280 min—
Mon 2 Nov— 23:280 min—
Sun 1 NovEcht 23:330 min—
Sat 31 OctEcht 23:31No data—
Sun 25 OctEcht 23:32No data—
Sat 24 OctMaastricht Randwyck 22:48No data—
Sun 18 OctEcht 23:330 min—
Sat 17 OctEcht 23:36No data—
Sun 11 OctEcht 23:32No data—
Sun 4 OctEcht 23:32No data—
Sat 3 OctEcht 23:31No data—
Sun 27 SeptEcht 23:33No data—
Sat 26 SeptEcht 23:31No data—
Sun 20 SeptEcht 23:33No data—
Sat 19 SeptGeleen-Lutterade 23:08No data—
Sun 13 SeptEcht 23:33No data—
Sat 12 SeptEcht 23:31No data—
Sun 6 SeptGeleen-Lutterade 23:11No data—
Sat 5 SeptGeleen-Lutterade 23:11No data—
Sun 30 AugEcht 23:34No data—
Sat 29 AugMaastricht 22:55No data—
Sun 23 AugEcht 23:33No data—
Sat 22 AugEcht 23:31No data—