Train NS 2741 Alkmaar – Maastricht

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

✓ Today’s run finished

Today, last fix heading to Sittard at 14:02 0 min

  1. Alkmaar11:01
  2. Zaandam11:25
  3. Amsterdam Centraal11:37
  4. Utrecht Centraal12:06
  5. Eindhoven Centraal12:58
  6. Sittard13:46
  7. Maastricht14:03

Next service: tomorrow 11:01 from Alkmaar · Sat 21 Nov

Next departure 11:01 tomorrow · Alkmaar
On-time · 30 days
84%
21/25 runs under 3 min
RT coverage: 22 full · 3 partial · 5 no data
On-time · 90 days
89%
34/38 runs under 3 min
RT coverage: 34 full · 4 partial · 50 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
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

  • Wed 18 Nov Max en route +14 min · last fix heading to Sittard +14 min
  • Sat 14 Nov Max en route +7 min · last fix heading to Weert +6 min
  • Thu 19 Nov Max en route +5 min · last fix heading to Sittard +5 min
  • Sun 8 Nov Max en route +8 min · last fix heading to Sittard +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 34
  • 3–10 min 8% · 3
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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