Train Arriva 18973 Maastricht – Aachen Hbf

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

✓ Today’s run finished

Today, last fix heading to Eygelshoven Markt at 22:47 +4 min

  1. Maastricht21:53
  2. Meerssen21:58
  3. Heerlen22:15
  4. Landgraaf22:22
  5. Eygelshoven Markt22:25
  6. Herzogenrath22:29
  7. Aachen Hbf22:42

Next service: tomorrow 21:53 from Maastricht · Mon 9 Nov

Next departure 21:53 tomorrow · Maastricht
On-time · 30 days
83%
5/6 runs under 3 min
RT coverage: 3 full · 3 partial · 4 no data
On-time · 90 days
83%
5/6 runs under 3 min
RT coverage: 3 full · 3 partial · 19 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

Worst days

  • Sun 8 Nov Max en route +6 min · last fix heading to Eygelshoven Markt +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 83% · 5
  • 3–10 min 17% · 1
  • 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=2
  • 75% S n=4

Stops and timetable

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

Last 90 days, 6 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
21:53on time on time
21:58— —
22:03— —
22:15 / 22:18— —
22:22— —
22:25— —
22:29 / 22:30— —
22:37 / 22:38— —
22: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 8 NovEygelshoven Markt 22:47Partial coverage+4 min+6 min
Sat 7 NovEygelshoven Markt 22:39Partial coverage0 min—
Sun 1 NovEygelshoven Markt 22:43Partial coverage0 min—
Sat 31 OctEygelshoven Markt 22:39No data—
Sun 25 OctEygelshoven Markt 22:43No data—
Sat 24 OctValkenburg 22:18No data—
Sun 18 OctValkenburg 22:19+1 min+1 min
Sat 17 OctValkenburg 22:17No data—
Sun 11 OctEygelshoven Markt 22:420 min—
Sat 10 OctValkenburg 22:170 min—
Sun 4 OctEygelshoven Markt 22:42No data—
Sat 3 OctEygelshoven Markt 22:42No data—
Sun 27 SeptEygelshoven Markt 22:43No data—
Sat 26 SeptValkenburg 22:18No data—
Sun 20 SeptEygelshoven Markt 22:48No data—
Sat 19 SeptValkenburg 22:17No data—
Sun 13 SeptEygelshoven Markt 22:42No data—
Sat 12 SeptEygelshoven Markt 22:39No data—
Sun 6 SeptEygelshoven Markt 22:42No data—
Sun 30 AugEygelshoven Markt 22:42No data—
Sat 29 AugValkenburg 22:17No data—
Sun 23 AugEygelshoven Markt 22:41No data—
Sat 22 AugValkenburg 22:18No data—
Sun 16 AugEygelshoven Markt 22:42No data—
Sat 15 AugEygelshoven Markt 22:38No data—