Train Arriva 18936 Aachen Hbf – Maastricht

Aachen Hbf 12:47 → Maastricht 13:41 Daily 0 h 54 min · 9 stops Arriva

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 12:47 from Aachen Hbf · Fri 6 Nov

Next departure 12:47 today · Aachen Hbf
On-time · 30 days
75%
12/16 runs under 3 min
RT coverage: 4 full · 12 partial · 12 no data
On-time · 90 days
74%
14/19 runs under 3 min
RT coverage: 4 full · 15 partial · 68 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: 0 min
P90
+18min
9 in 10 runs arrive with less than this
30 days: +10 min

Last 30 days

Arrival delay at Maastricht, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Wed 7 Oct Max en route +29 min · last fix heading to Meerssen +29 min
  • Fri 9 Oct Max en route +29 min · last fix heading to Meerssen +29 min
  • Sat 31 Oct Max en route +16 min · last fix heading to Meerssen +15 min
  • Thu 8 Oct Max en route +6 min · last fix heading to Meerssen +5 min
  • Sat 24 Oct Max en route +4 min · last fix heading to Meerssen +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 74% · 14
  • 3–10 min 11% · 2
  • 10–30 min 16% · 3
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=5
  • 67% W n=3
  • 50% T n=2
  • 0% F n=1
  • 33% S n=3
  • 100% S n=3

Stops and timetable

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

Last 90 days, 19 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
12:47on time on time
12:50 / 12:51— —
12:59 / 13:01— —
13:05— —
13:08 / 13:13— —
13:17 / 13:19— —
13:30— —
13:35— —
13:41— —

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 NovMeerssen 13:54No data—
Wed 4 NovMeerssen 13:52Partial coverage+1 min+2 min
Tue 3 NovMeerssen 13:52Partial coverage0 min—
Mon 2 NovMeerssen 13:54No data—
Sun 1 NovMeerssen 13:51Partial coverage0 min—
Sat 31 OctMeerssen 14:06Partial coverage+15 min+16 min
Fri 30 OctMeerssen 13:50No data—
Thu 29 OctMeerssen 14:12Partial coverage0 min—
Wed 28 OctMeerssen 13:51Partial coverage0 min—
Tue 27 OctMeerssen 13:57Partial coverage0 min—
Mon 26 OctMeerssen 13:52No data—
Sun 25 OctMeerssen 13:52No data—
Sat 24 OctMeerssen 13:49+4 min+4 min
Fri 23 OctLandgraaf 13:57No data—
Thu 22 OctMeerssen 14:17No data—
Wed 21 OctMeerssen 13:54No data—
Tue 20 OctMeerssen 13:51Partial coverage0 min—
Mon 19 OctMeerssen 13:55Partial coverage0 min—
Sun 18 OctMeerssen 13:51+1 min—
Sat 17 OctMeerssen 13:56No data—
Fri 16 OctMeerssen 13:52No data—
Thu 15 OctMeerssen 13:50No data—
Tue 13 OctMeerssen 13:55Partial coverage0 min—
Mon 12 OctMeerssen 13:52No data—
Sun 11 OctMeerssen 13:52+2 min+2 min
Sat 10 OctMeerssen 13:52+1 min+1 min
Fri 9 OctMeerssen 14:17Partial coverage+29 min+29 min
Thu 8 OctMeerssen 13:56Partial coverage+5 min+6 min
Wed 7 OctMeerssen 14:17Partial coverage+29 min+29 min
Tue 6 OctMeerssen 13:53Partial coverage+2 min+2 min