Train Arriva 18969 Maastricht – Aachen Hbf

Maastricht 20:53 → Aachen Hbf 21:42 Daily 0 h 49 min · 9 stops Arriva

It has not run yet today

Last recorded run: Sunday 15 November 0 min

Next service: today 20:53 from Maastricht · Wed 18 Nov

Next departure 20:53 today · Maastricht
On-time · 30 days
100%
5/5 runs under 3 min
RT coverage: 0 full · 5 partial · 3 no data
On-time · 90 days
100%
8/8 runs under 3 min
RT coverage: 3 full · 5 partial · 17 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 Aachen Hbf, 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 8 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
20:53on time on time
20:58— —
21:03— —
21:15 / 21:18— —
21:22— —
21:25— —
21:29 / 21:30— —
21:37 / 21:38— —
21:42— —

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 NovEygelshoven Markt 21:43Partial coverage0 min—
Sat 14 NovEygelshoven Markt 21:43Partial coverage0 min—
Sun 8 NovValkenburg 21:18Partial coverage0 min—
Sat 7 NovEygelshoven Markt 21:44Partial coverage+2 min+2 min
Sun 1 NovEygelshoven Markt 21:42Partial coverage0 min—
Sat 31 OctEygelshoven Markt 21:45No data—
Sun 25 OctEygelshoven Markt 21:42No data—
Sat 24 OctEygelshoven Markt 21:40No data—
Sun 18 OctValkenburg 21:180 min+2 min
Sat 17 OctEygelshoven Markt 21:43No data—
Sun 11 OctEygelshoven Markt 21:420 min—
Sat 10 OctEygelshoven Markt 21:39+1 min—
Sun 4 OctEygelshoven Markt 21:47No data—
Sat 3 OctEygelshoven Markt 21:45No data—
Sun 27 SeptEygelshoven Markt 21:43No data—
Sat 26 SeptEygelshoven Markt 21:42No data—
Sun 20 SeptEygelshoven Markt 21:43No data—
Sat 19 SeptEygelshoven Markt 21:41No data—
Sun 13 SeptEygelshoven Markt 21:44No data—
Sat 12 SeptEygelshoven Markt 21:42No data—
Sun 6 SeptEygelshoven Markt 21:42No data—
Sun 30 AugEygelshoven Markt 21:43No data—
Sat 29 AugEygelshoven Markt 21:40No data—
Sun 23 AugEygelshoven Markt 21:42No data—
Sat 22 AugEygelshoven Markt 21:42No data—