Train NS 2743 Alkmaar – Maastricht

Alkmaar 11:27 → Maastricht 14:30 Daily 3 h 03 min · 13 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 11:27 from Alkmaar · Thu 5 Nov

Next departure 11:27 today · Alkmaar
On-time · 30 days
95%
21/22 runs under 3 min
RT coverage: 17 full · 5 partial · 7 no data
On-time · 90 days
94%
51/54 runs under 3 min
RT coverage: 49 full · 5 partial · 31 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
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

  • Fri 9 Oct Max en route +13 min · last fix heading to Sittard +10 min
  • Mon 21 Sept Max en route +5 min · last fix heading to Castricum +5 min
  • Tue 6 Oct Max en route +4 min · last fix heading to Sittard +4 min

Distribution · 90 days

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

  • Early 19% · 10
  • On time 76% · 41
  • 3–10 min 6% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 90% M n=10
  • 89% T n=9
  • 100% W n=9
  • 100% T n=8
  • 89% F n=9
  • 100% S n=4
  • 100% S n=5

Stops and timetable

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

Last 90 days, 54 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:27on time on time
11:35≈ on time ≈ on time
11:49≈ on time ≈ on time
11:55 / 11:56≈ on time ≈ on time
12:02 / 12:04≈ on time ≈ on time
12:12≈ on time ≈ on time
12:31 / 12:34≈ on time ≈ on time
13:02 / 13:04≈ on time ≈ on time
13:24 / 13:27≈ on time ≈ +1 min
13:45≈ on time ≈ +1 min
13:58 / 14:00≈ on time ≈ +1 min
14:15 / 14:16≈ on time ≈ on time
14:30on time on time

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
Wed 4 NovSittard 14:29Partial coverage0 min+1 min
Tue 3 NovSittard 14:29No data—
Mon 2 NovSittard 14:29Partial coverage0 min—
Sun 1 NovArnhem Centraal 13:35+1 min—
Sat 31 OctSittard 14:340 min—
Fri 30 OctSittard 14:320 min—
Thu 29 OctSittard 14:310 min—
Wed 28 OctSittard 14:580 min—
Tue 27 OctSittard 14:32No data—
Mon 26 OctSittard 14:310 min—
Sun 25 OctSittard 14:34No data—
Sat 24 OctSittard 14:310 min—
Fri 23 OctSittard 14:310 min—
Thu 22 OctSittard 14:300 min—
Wed 21 OctSittard 14:370 min—
Tue 20 OctSittard 14:310 min—
Mon 19 OctSittard 14:33Partial coverage0 min—
Sun 18 OctSittard 14:350 min—
Sat 17 OctSittard 14:350 min—
Fri 16 OctSittard 14:35No data—
Thu 15 OctSittard 14:30No data—
Wed 14 OctSittard 14:31No data—
Tue 13 OctSittard 14:360 min—
Mon 12 OctSittard 14:32No data—
Sun 11 OctEde-Wageningen 13:22+2 min+2 min
Sat 10 OctSittard 14:340 min—
Fri 9 OctSittard 14:53+10 min+13 min
Thu 8 OctSittard 14:31Partial coverage0 min—
Wed 7 OctSittard 14:32Partial coverage+1 min—
Tue 6 OctSittard 14:38+4 min+4 min