Train NS 7461 Uitgeest – Amsterdam Centraal

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

It has not run yet today

Last recorded run: Sunday 8 November 0 min

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

Next departure 16:03 today · Uitgeest
On-time · 30 days
100%
14/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
0min
9 in 10 runs arrive with less than this
30 days: 0 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

  • Wed 7 Oct Max en route +5 min · last fix heading to Bunnik +4 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=4
  • 100% T n=2
  • 67% W n=3
  • 100% 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
16:03on time on time
16:08≈ on time ≈ on time
16:10 / 16:16≈ on time ≈ on time
16:19≈ on time ≈ +1 min
16:22≈ on time ≈ +1 min
16:25≈ on time ≈ +1 min
16:31≈ on time ≈ +1 min
16:37on 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
Sun 8 NovAmsterdam Sloterdijk 16:45Partial coverage0 min—
Sat 7 NovAmsterdam Sloterdijk 16:47+1 min+1 min
Fri 6 NovBunnik 17:480 min+4 min
Thu 5 NovBunnik 17:48No data—
Wed 4 NovBunnik 17:480 min—
Tue 3 NovBunnik 17:48No data—
Mon 2 NovBunnik 17:48No data—
Fri 30 OctBunnik 17:470 min—
Thu 29 OctBunnik 17:480 min—
Wed 28 OctBunnik 17:48No data—
Tue 27 OctBunnik 17:480 min—
Mon 26 OctBunnik 17:480 min—
Fri 23 OctUtrecht Zuilen 17:370 min—
Thu 22 OctAmsterdam Sloterdijk 16:460 min—
Wed 21 OctUtrecht Zuilen 17:420 min—
Tue 20 OctUtrecht Zuilen 17:42No data—
Mon 19 OctBunnik 17:460 min—
Fri 16 OctBunnik 17:490 min—
Thu 15 OctBunnik 17:48No data—
Wed 14 OctBunnik 17:48No data—
Tue 13 OctBunnik 17:48No data—
Mon 12 OctBunnik 17:480 min—
Fri 9 OctBreukelen 17:290 min—
Thu 8 OctBunnik 17:480 min—
Wed 7 OctBunnik 17:50+4 min+5 min
Tue 6 OctBunnik 17:480 min+3 min
Mon 5 OctEde-Wageningen 18:130 min—
Fri 2 OctBunnik 17:47No data—
Thu 1 OctBunnik 17:48No data—
Wed 30 SeptBunnik 17:48No data—