Train NS 2745 Alkmaar – Maastricht

Alkmaar 11:57 → Maastricht 15:00 Daily 3 h 03 min · 13 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Sittard at 14:59 +1 min

  1. Alkmaar11:57
  2. Zaandam12:19
  3. Amsterdam Centraal12:32
  4. Utrecht Centraal13:01
  5. Eindhoven Centraal13:54
  6. Sittard14:45
  7. Maastricht15:00

Next service: tomorrow 11:57 from Alkmaar · Sun 8 Nov

Next departure 11:57 tomorrow · Alkmaar
On-time · 30 days
96%
22/23 runs under 3 min
RT coverage: 22 full · 1 partial · 7 no data
On-time · 90 days
93%
25/27 runs under 3 min
RT coverage: 26 full · 1 partial · 59 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

  • Thu 8 Oct Max en route +5 min · last fix heading to Sittard +4 min
  • Sun 18 Oct Max en route +6 min · last fix heading to Sittard +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 25
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=3
  • 100% W n=4
  • 75% T n=4
  • 100% F n=4
  • 100% S n=5
  • 67% S n=3

Stops and timetable

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

Last 90 days, 27 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
11:57on time on time
12:05≈ on time ≈ on time
12:19≈ on time ≈ on time
12:25 / 12:26≈ on time ≈ on time
12:32 / 12:35≈ on time ≈ on time
12:43≈ on time ≈ +1 min
13:01 / 13:04≈ on time ≈ +1 min
13:32 / 13:34≈ on time ≈ +1 min
13:54 / 13:57≈ on time ≈ +2 min
14:15≈ on time ≈ +2 min
14:28 / 14:30≈ on time ≈ +2 min
14:45 / 14:46≈ on time ≈ +2 min
15:00on time +3 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
Sat 7 NovSittard 14:59Partial coverage+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:030 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—
Wed 21 OctSittard 15:01No data—
Tue 20 OctUtrecht Centraal 15:020 min—
Mon 19 OctSittard 15:010 min—
Sun 18 OctSittard 15:16+4 min+6 min
Sat 17 OctSittard 15:070 min—
Fri 16 OctSittard 15:040 min—
Thu 15 OctSittard 15:02No data—
Wed 14 OctSittard 15:040 min—
Tue 13 OctSittard 15:04No data—
Mon 12 OctSittard 15:050 min—
Sun 11 OctEde-Wageningen 13:51+1 min+1 min
Sat 10 OctSittard 15:130 min—
Fri 9 OctSittard 15:040 min—