Train NS 7414 Utrecht Centraal – Uitgeest

Utrecht Centraal 06:38 → Uitgeest 07:57 Mon, Tue, Wed, Thu, Fri 1 h 19 min · 18 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Friday 6 November No data

Next service: Monday 06:38 from Utrecht Centraal · Mon 9 Nov

Next departure 06:38 Monday · Utrecht Centraal
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 14 full · 6 partial · 1 no data
On-time · 90 days
100%
23/23 runs under 3 min
RT coverage: 15 full · 8 partial · 40 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Uitgeest, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 23
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=5
  • 100% W n=5
  • 100% T n=5
  • 100% F n=4
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 23 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
06:38on time on time
06:41≈ on time ≈ on time
06:45≈ on time ≈ on time
06:50≈ on time ≈ on time
06:58≈ on time ≈ on time
07:01≈ on time ≈ on time
07:04 / 07:10≈ on time ≈ on time
07:13≈ on time ≈ +1 min
07:17≈ on time ≈ +1 min
07:20≈ on time ≈ +1 min
07:25 / 07:27≈ on time ≈ +1 min
07:33≈ on time ≈ +1 min
07:40≈ on time ≈ +1 min
07:43≈ on time ≈ +1 min
07:46≈ on time ≈ +1 min
07:49≈ on time ≈ +1 min
07:53≈ on time ≈ +1 min
07:57on time +1 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 6 NovKrommenie-Assendelft 08:07No data—
Thu 5 NovKrommenie-Assendelft 08:08Partial coverage0 min—
Wed 4 NovKrommenie-Assendelft 08:07+2 min+2 min
Tue 3 NovKrommenie-Assendelft 08:07Partial coverage0 min—
Mon 2 NovKrommenie-Assendelft 08:080 min—
Fri 30 OctKrommenie-Assendelft 08:070 min—
Thu 29 OctKrommenie-Assendelft 08:07Partial coverage0 min—
Wed 28 OctKrommenie-Assendelft 08:080 min—
Tue 27 OctKrommenie-Assendelft 08:07Partial coverage0 min—
Mon 26 OctKrommenie-Assendelft 08:100 min—
Fri 23 OctKrommenie-Assendelft 08:070 min—
Thu 22 OctKrommenie-Assendelft 08:07Partial coverage0 min—
Wed 21 OctKrommenie-Assendelft 08:090 min—
Tue 20 OctKrommenie-Assendelft 08:07Partial coverage0 min—
Mon 19 OctKrommenie-Assendelft 08:070 min—
Fri 16 OctZaandijk Zaanse Schans 08:040 min—
Thu 15 OctZaandijk Zaanse Schans 08:000 min—
Wed 14 OctZaandijk Zaanse Schans 08:000 min—
Tue 13 OctZaandijk Zaanse Schans 08:000 min—
Mon 12 OctZaandijk Zaanse Schans 08:000 min—
Fri 9 OctKrommenie-Assendelft 08:07+1 min—
Thu 8 OctKrommenie-Assendelft 08:07Partial coverage0 min—
Wed 7 OctKrommenie-Assendelft 08:09+1 min+2 min
Tue 6 OctKrommenie-Assendelft 08:07Partial coverage0 min—
Mon 5 OctAmsterdam Muiderpoort 07:35No data—
Fri 2 OctKrommenie-Assendelft 08:08No data—
Thu 1 OctKrommenie-Assendelft 08:07No data—
Wed 30 SeptKrommenie-Assendelft 08:07No data—
Tue 29 SeptKrommenie-Assendelft 08:07No data—
Mon 28 SeptKrommenie-Assendelft 08:07No data—