Train NS 7446 Utrecht Centraal – Uitgeest

Utrecht Centraal 14:38 → Uitgeest 15:57 Daily 1 h 19 min · 18 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 14:38 from Utrecht Centraal · Sat 7 Nov

Next departure 14:38 today · Utrecht Centraal
On-time · 30 days
100%
11/11 runs under 3 min
RT coverage: 6 full · 5 partial · 10 no data
On-time · 90 days
100%
15/15 runs under 3 min
RT coverage: 7 full · 8 partial · 48 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 15 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
14:38on time on time
14:41≈ on time ≈ on time
14:45≈ on time ≈ on time
14:50≈ on time ≈ on time
14:58≈ on time ≈ on time
15:01≈ on time ≈ on time
15:04 / 15:05≈ on time ≈ on time
15:08≈ on time ≈ on time
15:12≈ on time ≈ on time
15:15≈ on time ≈ on time
15:20 / 15:22≈ on time ≈ on time
15:28≈ on time ≈ on time
15:35≈ on time ≈ on time
15:38≈ on time ≈ on time
15:41≈ on time ≈ on time
15:44 / 15:49≈ on time ≈ on time
15:52≈ on time ≈ on time
15:57on 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
Fri 6 NovKrommenie-Assendelft 16:18No data—
Thu 5 NovKrommenie-Assendelft 16:08No data—
Wed 4 NovKrommenie-Assendelft 16:04Partial coverage+1 min+1 min
Tue 3 NovKrommenie-Assendelft 16:09No data—
Mon 2 NovKrommenie-Assendelft 16:07Partial coverage0 min—
Fri 30 OctKrommenie-Assendelft 16:09No data—
Thu 29 OctKrommenie-Assendelft 16:08Partial coverage0 min—
Wed 28 OctKrommenie-Assendelft 16:07No data—
Tue 27 OctKrommenie-Assendelft 16:07No data—
Mon 26 OctKrommenie-Assendelft 16:07Partial coverage0 min—
Fri 23 OctKrommenie-Assendelft 16:07No data—
Thu 22 OctWormerveer 16:110 min—
Wed 21 OctKrommenie-Assendelft 16:06No data—
Tue 20 OctKrommenie-Assendelft 16:060 min—
Mon 19 OctKrommenie-Assendelft 16:08Partial coverage0 min—
Fri 16 OctZaandijk Zaanse Schans 16:040 min—
Thu 15 OctZaandijk Zaanse Schans 16:000 min—
Wed 14 OctZaandijk Zaanse Schans 16:00No data—
Tue 13 OctZaandijk Zaanse Schans 16:00No data—
Mon 12 OctZaandijk Zaanse Schans 16:000 min—
Fri 9 OctKrommenie-Assendelft 16:080 min—
Thu 8 OctKrommenie-Assendelft 16:06Partial coverage0 min—
Wed 7 OctKrommenie-Assendelft 16:07Partial coverage0 min+1 min
Tue 6 OctKrommenie-Assendelft 16:07Partial coverage+1 min—
Mon 5 OctAmsterdam Muiderpoort 15:350 min—
Fri 2 OctKrommenie-Assendelft 16:07No data—
Thu 1 OctKrommenie-Assendelft 16:07No data—
Wed 30 SeptKrommenie-Assendelft 16:07No data—
Tue 29 SeptKrommenie-Assendelft 16:07No data—
Mon 28 SeptKrommenie-Assendelft 16:07No data—