Train Arriva 18928 Aachen Hbf – Maastricht
✓ Today’s run finished
Today, last fix heading to Meerssen at 11:49 No data
- Aachen Hbf10:47
- Aachen West10:50
- Eygelshoven Markt11:05
- Landgraaf11:08
- Heerlen11:17
- Meerssen11:35
- Maastricht11:41
Next service: Monday 10:47 from Aachen Hbf · Mon 9 Nov
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
- Thu 8 Oct Max en route +8 min · last fix heading to Meerssen +8 min
- Tue 6 Oct Max en route +6 min · last fix heading to Meerssen +6 min
Distribution · 90 days
13 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 85% · 11
- 3–10 min 15% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=1
- 75% T n=4
- 100% W n=3
- 0% T n=1
- 100% F n=1
- 100% S n=3
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (9 stops).
Last 90 days, 13 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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 10:47 | on time | on time | |
| 10:50 / 10:51 | — | — | |
| 10:59 / 11:01 | — | — | |
| 11:05 | — | — | |
| 11:08 / 11:13 | — | — | |
| 11:17 / 11:19 | — | — | |
| 11:30 | — | — | |
| 11:35 | — | — | |
| 11: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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sat 7 Nov | Meerssen 11:49 | No data | — |
| Fri 6 Nov | Meerssen 11:49 | No data | — |
| Thu 5 Nov | Meerssen 11:49 | No data | — |
| Wed 4 Nov | Meerssen 11:49Partial coverage | 0 min | — |
| Tue 3 Nov | Meerssen 11:49 | No data | — |
| Mon 2 Nov | Meerssen 11:49 | No data | — |
| Sat 31 Oct | Meerssen 11:50Partial coverage | 0 min | — |
| Fri 30 Oct | Meerssen 11:54 | No data | — |
| Thu 29 Oct | Meerssen 11:50 | No data | — |
| Wed 28 Oct | Meerssen 11:51Partial coverage | 0 min | — |
| Tue 27 Oct | Meerssen 11:53Partial coverage | 0 min | — |
| Mon 26 Oct | Meerssen 11:50 | No data | — |
| Sat 24 Oct | Valkenburg 11:44 | 0 min | — |
| Fri 23 Oct | Meerssen 11:54 | No data | — |
| Thu 22 Oct | Meerssen 11:56 | No data | — |
| Wed 21 Oct | Meerssen 11:58 | No data | — |
| Tue 20 Oct | Meerssen 11:51Partial coverage | 0 min | — |
| Mon 19 Oct | Meerssen 11:59Partial coverage | 0 min | — |
| Sat 17 Oct | Meerssen 11:51 | No data | — |
| Fri 16 Oct | Meerssen 11:50 | No data | — |
| Thu 15 Oct | Meerssen 11:50 | No data | — |
| Tue 13 Oct | Meerssen 11:57Partial coverage | 0 min | — |
| Mon 12 Oct | Meerssen 11:51 | No data | — |
| Sat 10 Oct | Meerssen 11:53 | +2 min | +2 min |
| Fri 9 Oct | Meerssen 11:53Partial coverage | +3 min | +3 min |
| Thu 8 Oct | Meerssen 11:59Partial coverage | +8 min | +8 min |
| Wed 7 Oct | Valkenburg 12:01Partial coverage | 0 min | — |
| Tue 6 Oct | Meerssen 11:57Partial coverage | +6 min | +6 min |
| Mon 5 Oct | Meerssen 11:50 | No data | — |
| Sat 3 Oct | Meerssen 11:56 | No data | — |