Train Arriva 18920 Aachen Hbf – Maastricht

Aachen Hbf 08:47 → Maastricht 09:41 Mon, Tue, Wed, Thu, Fri, Sat 0 h 54 min · 9 stops Arriva

✓ Today’s run finished

Today, last fix heading to Meerssen at 09:49 0 min

  1. Aachen Hbf08:47
  2. Aachen West08:50
  3. Eygelshoven Markt09:05
  4. Landgraaf09:08
  5. Heerlen09:17
  6. Meerssen09:35
  7. Maastricht09:41

Next service: Monday 08:47 from Aachen Hbf · Mon 9 Nov

Next departure 08:47 Monday · Aachen Hbf
On-time · 30 days
92%
12/13 runs under 3 min
RT coverage: 3 full · 10 partial · 12 no data
On-time · 90 days
94%
15/16 runs under 3 min
RT coverage: 3 full · 13 partial · 60 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +1 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 4 Nov Max en route +9 min · last fix heading to Meerssen +9 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 15
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 16 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
08:47on time on time
08:50 / 08:51— —
08:59 / 09:01— —
09:05— —
09:08 / 09:13— —
09:17 / 09:19— —
09:30— —
09:35— —
09: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
Sat 7 NovMeerssen 09:49Partial coverage0 min+4 min
Fri 6 NovMeerssen 09:57No data—
Thu 5 NovMeerssen 09:52No data—
Wed 4 NovMeerssen 09:59Partial coverage+9 min+9 min
Tue 3 NovMeerssen 09:49No data—
Mon 2 NovMeerssen 09:58Partial coverage0 min—
Sat 31 OctMeerssen 09:50Partial coverage+1 min+2 min
Fri 30 OctMeerssen 09:51No data—
Thu 29 OctMeerssen 09:50Partial coverage0 min—
Wed 28 OctMeerssen 09:52Partial coverage0 min—
Tue 27 OctMeerssen 09:51No data—
Mon 26 OctMeerssen 09:51No data—
Sat 24 OctMeerssen 09:490 min—
Fri 23 OctMeerssen 09:51No data—
Thu 22 OctMeerssen 09:50No data—
Wed 21 OctMeerssen 09:53No data—
Tue 20 OctMeerssen 09:51Partial coverage0 min—
Mon 19 OctMeerssen 09:56Partial coverage0 min—
Sat 17 OctMeerssen 09:510 min—
Fri 16 OctMeerssen 09:50No data—
Thu 15 OctMeerssen 09:50No data—
Tue 13 OctMeerssen 09:55Partial coverage0 min—
Mon 12 OctMeerssen 09:52No data—
Sat 10 OctMeerssen 09:52+1 min+1 min
Fri 9 OctMeerssen 09:53Partial coverage+1 min+1 min
Thu 8 OctMeerssen 09:52Partial coverage+2 min+2 min
Wed 7 OctMeerssen 09:50Partial coverage0 min—
Tue 6 OctMeerssen 09:51Partial coverage0 min—
Mon 5 OctMeerssen 09:51No data—
Sat 3 OctMeerssen 09:50No data—