Train NS 7458 Amsterdam Centraal – Uitgeest

Amsterdam Centraal 18:23 → Uitgeest 18:57 Daily 0 h 34 min · 8 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Sunday 8 November +4 min

Next service: today 18:23 from Amsterdam Centraal · Mon 9 Nov

Next departure 18:23 today · Amsterdam Centraal
On-time · 30 days
79%
11/14 runs under 3 min
RT coverage: 12 full · 2 partial · 8 no data
On-time · 90 days
84%
16/19 runs under 3 min
RT coverage: 17 full · 2 partial · 44 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +4 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

Worst days

  • Mon 2 Nov Max en route +15 min · last fix heading to Duivendrecht +15 min
  • Sun 8 Nov Max en route +4 min · last fix heading to Krommenie-Assendelft +4 min
  • Sat 7 Nov Max en route +4 min · last fix heading to Krommenie-Assendelft +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 84% · 16
  • 3–10 min 11% · 2
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 100% T n=1
  • 100% W n=2
  • 100% T n=4
  • 100% F n=5
  • 0% S n=1
  • 0% 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
18:23on time on time
18:28≈ on time ≈ on time
18:35≈ on time ≈ +1 min
18:38≈ on time ≈ +1 min
18:41≈ on time ≈ +1 min
18:45 / 18:49≈ on time ≈ +1 min
18:52≈ on time ≈ +2 min
18:57on time +2 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 NovKrommenie-Assendelft 19:09Partial coverage+4 min+4 min
Sat 7 NovKrommenie-Assendelft 19:09Partial coverage+4 min+4 min
Fri 6 NovZaandijk Zaanse Schans 18:59+2 min+3 min
Thu 5 NovAmsterdam Amstel 18:58No data—
Wed 4 NovAmsterdam Muiderpoort 18:59No data—
Tue 3 NovAmsterdam Amstel 18:59No data—
Mon 2 NovDuivendrecht 19:19+15 min+15 min
Fri 30 OctWormerveer 19:080 min—
Thu 29 OctAmsterdam Holendrecht 18:590 min—
Wed 28 OctAmsterdam Amstel 18:580 min—
Tue 27 OctAmsterdam Bijlmer ArenA 19:05No data—
Mon 26 OctDuivendrecht 19:000 min—
Fri 23 OctKrommenie-Assendelft 19:06+2 min+3 min
Thu 22 OctZaandijk Zaanse Schans 18:590 min—
Wed 21 OctKoog aan de Zaan 18:59No data—
Tue 20 OctZaandijk Zaanse Schans 18:59No data—
Mon 19 OctZaandijk Zaanse Schans 19:010 min—
Fri 16 OctZaandijk Zaanse Schans 19:040 min—
Thu 15 OctAmsterdam Sloterdijk 18:500 min—
Wed 14 OctZaandijk Zaanse Schans 19:00No data—
Tue 13 OctZaandam 18:50No data—
Mon 12 OctKoog aan de Zaan 18:570 min—
Fri 9 OctAmsterdam Sloterdijk 18:59+1 min—
Thu 8 OctUtrecht Vaartsche Rijn 18:590 min—
Wed 7 OctDuivendrecht 19:00+1 min+1 min
Tue 6 OctAmsterdam Holendrecht 18:580 min—
Mon 5 OctAmsterdam Bijlmer ArenA 18:29+1 min+1 min
Fri 2 OctZaandijk Zaanse Schans 19:00No data—
Thu 1 OctAmsterdam Bijlmer ArenA 18:19No data—
Wed 30 SeptDuivendrecht 18:18No data—