Train NS 2745 Alkmaar → Maastricht

Alkmaar 12:01 → Maastricht 15:03 Daily 3 h 02 min · 13 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 20 November 0 min

Next service: today 12:01 from Alkmaar · Sat 21 Nov

Next departure 12:01 today · Alkmaar
On-time · 30 days
84%
21/25 runs under 3 min
RT coverage: 22 full · 3 partial · 4 no data
On-time · 90 days
85%
34/40 runs under 3 min
RT coverage: 34 full · 6 partial · 48 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Mon 9 Nov Max en route +31 min · last fix heading to Sittard +31 min
  • Sun 15 Nov Max en route +6 min · last fix heading to Weert +6 min
  • Thu 8 Oct Max en route +5 min · last fix heading to Sittard +4 min
  • Wed 11 Nov Max en route +4 min · last fix heading to Sittard +4 min
  • Wed 18 Nov Max en route +4 min · last fix heading to Sittard +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 85% · 34
  • 3–10 min 13% · 5
  • 10–30 min 0% · 0
  • 30+ min 3% · 1

On-time by weekday

  • 83% M n=6
  • 100% T n=5
  • 67% W n=6
  • 83% T n=6
  • 100% F n=6
  • 100% S n=6
  • 60% S n=5

Stops and timetable

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

Last 90 days, 40 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:01on time on time
12:09≈ on time ≈ on time
12:25≈ on time ≈ +1 min
12:31≈ on time ≈ +1 min
12:37 / 12:39≈ on time ≈ +1 min
12:47≈ on time ≈ +1 min
13:06 / 13:09≈ on time ≈ +2 min
13:36 / 13:38≈ on time ≈ +2 min
13:58 / 14:00≈ on time ≈ +3 min
14:17≈ on time ≈ +3 min
14:30 / 14:31≈ on time ≈ +4 min
14:46 / 14:47≈ on time ≈ +4 min
15:03on time +4 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
Fri 20 NovSittard 15:02Partial coverage0 min—
Thu 19 NovSittard 14:590 min—
Wed 18 NovSittard 15:04+4 min+4 min
Tue 17 NovSittard 14:590 min—
Mon 16 NovSittard 15:000 min+1 min
Sun 15 NovWeert 14:40+6 min+6 min
Sat 14 NovWeert 14:38+3 min+4 min
Fri 13 NovSittard 15:04Partial coverage+1 min—
Thu 12 NovSittard 14:59+1 min+1 min
Wed 11 NovSittard 15:09+4 min+4 min
Tue 10 NovSittard 14:590 min+2 min
Mon 9 NovSittard 15:03+31 min+31 min
Sun 8 NovSittard 14:59+1 min+2 min
Sat 7 NovSittard 14:59+1 min+2 min
Fri 6 NovSittard 15:02No data—
Thu 5 NovSittard 15:070 min—
Wed 4 NovSittard 14:590 min—
Tue 3 NovSittard 14:59No data—
Mon 2 NovSittard 15:04No data—
Sun 1 NovArnhem Centraal 14:05+3 min+3 min
Sat 31 OctSittard 15:03Partial coverage0 min+2 min
Fri 30 OctSittard 15:150 min—
Thu 29 OctSittard 15:000 min—
Wed 28 OctSittard 15:010 min—
Tue 27 OctSittard 15:020 min—
Mon 26 OctSittard 15:010 min—
Sun 25 OctSittard 15:24No data—
Sat 24 OctSittard 15:010 min—
Fri 23 OctSittard 15:060 min—
Thu 22 OctSittard 15:010 min—