Train NS 7465 Uitgeest – Amsterdam Centraal

Uitgeest 17:03 → Amsterdam Centraal 17:37 Daily 0 h 34 min · 8 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Sunday 8 November +2 min

Next service: today 17:03 from Uitgeest · Mon 9 Nov

Next departure 17:03 today · Uitgeest
On-time · 30 days
93%
13/14 runs under 3 min
RT coverage: 13 full · 1 partial · 8 no data
On-time · 90 days
95%
18/19 runs under 3 min
RT coverage: 18 full · 1 partial · 44 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: +1 min

Last 30 days

Arrival delay at Amsterdam 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 +5 min · last fix heading to Abcoude +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 18
  • 3–10 min 5% · 1
  • 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
  • 67% T n=3
  • 100% F n=5
  • 100% S n=1
  • 100% S n=1

Stops and timetable

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

Last 90 days, 19 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:03on time on time
17:08≈ on time ≈ on time
17:10 / 17:16≈ on time ≈ on time
17:19≈ on time ≈ on time
17:22≈ on time ≈ on time
17:25≈ on time ≈ on time
17:31≈ on time ≈ on time
17:37on 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
Sun 8 NovAmsterdam Sloterdijk 17:47Partial coverage+2 min+2 min
Sat 7 NovAmsterdam Sloterdijk 17:440 min—
Fri 6 NovBunnik 18:44+1 min—
Thu 5 NovMaarssen 18:39No data—
Wed 4 NovMaarssen 18:39No data—
Tue 3 NovMaarssen 18:39No data—
Mon 2 NovBreukelen 18:390 min—
Fri 30 OctBunnik 18:470 min—
Thu 29 OctAbcoude 18:47+5 min+5 min
Wed 28 OctMaarssen 18:400 min—
Tue 27 OctAbcoude 18:40No data—
Mon 26 OctBreukelen 18:400 min—
Fri 23 OctUtrecht Zuilen 18:310 min—
Thu 22 OctAmsterdam Sloterdijk 17:440 min—
Wed 21 OctUtrecht Zuilen 18:41No data—
Tue 20 OctUtrecht Zuilen 18:410 min—
Mon 19 OctBunnik 18:460 min—
Fri 16 OctBunnik 18:470 min—
Thu 15 OctUtrecht Vaartsche Rijn 18:43No data—
Wed 14 OctBunnik 18:48No data—
Tue 13 OctBunnik 18:48No data—
Mon 12 OctBunnik 18:480 min—
Fri 9 OctBunnik 18:47+1 min—
Thu 8 OctAbcoude 18:400 min—
Wed 7 OctBreukelen 18:400 min—
Tue 6 OctAbcoude 18:390 min—
Mon 5 OctBreukelen 19:100 min—
Fri 2 OctBunnik 18:47No data—
Thu 1 OctAbcoude 18:15No data—
Wed 30 SeptBreukelen 18:18No data—