Train NS 7467 Uitgeest – Utrecht Centraal

Uitgeest 17:33 → Utrecht Centraal 18:50 Daily 1 h 17 min · 18 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 17:33 from Uitgeest · Fri 6 Nov

Next departure 17:33 today · Uitgeest
On-time · 30 days
87%
13/15 runs under 3 min
RT coverage: 12 full · 3 partial · 6 no data
On-time · 90 days
89%
16/18 runs under 3 min
RT coverage: 13 full · 5 partial · 44 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: +3 min

Last 30 days

Arrival delay at Utrecht Centraal, 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 29 Oct Max en route +7 min · last fix heading to Amsterdam Sloterdijk +6 min
  • Mon 2 Nov Max en route +6 min · last fix heading to Amsterdam Centraal +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 16
  • 3–10 min 11% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 100% T n=4
  • 100% W n=2
  • 75% T n=4
  • 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, 18 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
17:33on time +1 min
17:38≈ on time ≈ on time
17:40 / 17:46≈ on time ≈ on time
17:49≈ on time ≈ on time
17:52≈ on time ≈ on time
17:55≈ on time ≈ on time
18:01≈ on time ≈ +1 min
18:07 / 18:09≈ on time ≈ +1 min
18:14≈ on time ≈ +1 min
18:18≈ on time ≈ +1 min
18:21≈ on time ≈ +1 min
18:24≈ on time ≈ +1 min
18:26≈ on time ≈ +1 min
18:30≈ on time ≈ +1 min
18:37≈ on time ≈ +1 min
18:42≈ on time ≈ +1 min
18:47≈ on time ≈ +1 min
18:50on 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
Thu 5 NovAmsterdam Centraal 18:54No data—
Wed 4 NovAmsterdam Muiderpoort 19:22No data—
Tue 3 NovAmsterdam Centraal 18:59Partial coverage0 min—
Mon 2 NovAmsterdam Centraal 18:59Partial coverage+5 min+6 min
Fri 30 OctUtrecht Zuilen 19:050 min—
Thu 29 OctAmsterdam Sloterdijk 19:06+6 min+7 min
Wed 28 OctAmsterdam Centraal 18:510 min—
Tue 27 OctAmsterdam Sloterdijk 18:520 min—
Mon 26 OctAmsterdam Sloterdijk 01:250 min—
Fri 23 OctUtrecht Zuilen 19:020 min—
Thu 22 OctAmsterdam Sloterdijk 18:190 min—
Wed 21 OctAbcoude 19:02No data—
Tue 20 OctMaarssen 19:060 min—
Mon 19 OctMaarssen 18:560 min—
Fri 16 OctUtrecht Zuilen 19:050 min—
Thu 15 OctAbcoude 18:530 min—
Wed 14 OctUtrecht Zuilen 19:03No data—
Tue 13 OctBreukelen 18:52No data—
Mon 12 OctMaarssen 18:58No data—
Fri 9 OctAbcoude 18:550 min—
Thu 8 OctAmsterdam Sloterdijk 18:51Partial coverage0 min—
Wed 7 OctAmsterdam Centraal 18:52Partial coverage0 min+1 min
Tue 6 OctAmsterdam Sloterdijk 18:56Partial coverage+2 min+3 min
Mon 5 OctAmsterdam Muiderpoort 19:43+2 min+2 min
Fri 2 OctMaarssen 19:00No data—
Thu 1 OctAmsterdam Sloterdijk 18:15No data—
Wed 30 SeptAmsterdam Centraal 18:18No data—
Tue 29 SeptAmsterdam Sloterdijk 18:15No data—
Mon 28 SeptAmsterdam Sloterdijk 18:15No data—
Fri 25 SeptAbcoude 18:47No data—