Train NS 2917 Amsterdam Centraal – Maastricht

Amsterdam Centraal 05:39 → Maastricht 08:01 Mon, Tue, Wed, Thu, Fri, Sat 2 h 22 min · 9 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Tuesday 10 November +4 min

Next service: today 05:39 from Amsterdam Centraal · Wed 11 Nov

Next departure 05:39 today · Amsterdam Centraal
On-time · 30 days
60%
12/20 runs under 3 min
RT coverage: 17 full · 3 partial · 1 no data
On-time · 90 days
68%
17/25 runs under 3 min
RT coverage: 22 full · 3 partial · 40 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +5 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

  • Thu 15 Oct Max en route +12 min · last fix heading to Sittard +12 min
  • Mon 9 Nov Max en route +6 min · last fix heading to Sittard +6 min
  • Tue 13 Oct Max en route +5 min · last fix heading to Sittard +5 min
  • Fri 30 Oct Max en route +6 min · last fix heading to Sittard +5 min
  • Mon 26 Oct Max en route +6 min · last fix heading to Sittard +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 68% · 17
  • 3–10 min 28% · 7
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 60% M n=5
  • 67% T n=6
  • 80% W n=5
  • 80% T n=5
  • 50% F n=4
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 25 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
05:39on time on time
05:47≈ on time ≈ on time
06:06 / 06:09≈ on time ≈ +1 min
06:36 / 06:38≈ on time ≈ +2 min
06:58 / 07:00≈ on time ≈ +3 min
07:17≈ on time ≈ +4 min
07:30 / 07:31≈ on time ≈ +4 min
07:46 / 07:47≈ on time ≈ +5 min
08:01on time +5 min

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
Tue 10 NovSittard 08:09Partial coverage+4 min+4 min
Mon 9 NovSittard 08:14+6 min+6 min
Fri 6 NovSittard 08:24No data—
Thu 5 NovSittard 08:190 min—
Wed 4 NovSittard 08:03+1 min+1 min
Tue 3 NovSittard 08:04Partial coverage+2 min+2 min
Mon 2 NovSittard 08:140 min—
Fri 30 OctSittard 08:07+5 min+6 min
Thu 29 OctSittard 08:05+1 min+1 min
Wed 28 OctSittard 08:070 min—
Tue 27 OctSittard 08:03Partial coverage+2 min+3 min
Mon 26 OctSittard 08:13+5 min+6 min
Fri 23 OctSittard 08:08+4 min+4 min
Thu 22 OctSittard 08:030 min—
Wed 21 OctSittard 08:020 min—
Tue 20 OctSittard 08:030 min—
Mon 19 OctSittard 08:140 min—
Fri 16 OctSittard 08:050 min—
Thu 15 OctSittard 08:25+12 min+12 min
Wed 14 OctSittard 08:09+4 min+4 min
Tue 13 OctSittard 08:22+5 min+5 min
Mon 12 OctSittard 08:040 min—
Fri 9 OctSittard 08:05+1 min+1 min
Thu 8 OctSittard 08:030 min—
Wed 7 OctSittard 08:020 min—
Tue 6 OctSittard 08:020 min—
Mon 5 OctSittard 08:02No data—
Fri 2 OctSittard 08:02No data—
Thu 1 OctSittard 08:03No data—
Wed 30 SeptSittard 08:01No data—