Train NS 7475 Uitgeest – Amsterdam Centraal

Uitgeest 19:33 → Amsterdam Centraal 20:02 Mon, Tue, Wed, Thu, Fri 0 h 29 min · 8 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 20:04 +1 min

  1. Uitgeest19:33
  2. Krommenie-Assendelft19:38
  3. Wormerveer19:41
  4. Koog aan de Zaan19:47
  5. Zaandam19:50
  6. Amsterdam Sloterdijk19:56
  7. Amsterdam Centraal20:02

Next service: Monday 19:33 from Uitgeest · Mon 9 Nov

Next departure 19:33 Monday · Uitgeest
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 13 full · 0 partial · 9 no data
On-time · 90 days
93%
13/14 runs under 3 min
RT coverage: 14 full · 0 partial · 15 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

  • Tue 6 Oct Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 13
  • 3–10 min 7% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 14 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
19:33on time +1 min
19:38≈ on time ≈ +1 min
19:41≈ on time ≈ +1 min
19:44≈ on time ≈ +1 min
19:47≈ on time ≈ +2 min
19:50≈ on time ≈ +2 min
19:56≈ on time ≈ +2 min
20:02on 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
Fri 6 Nov— 20:04+1 min—
Thu 5 Nov— 20:03No data—
Wed 4 Nov— 20:08+3 min+3 min
Tue 3 Nov— 20:09No data—
Mon 2 Nov— 20:14No data—
Fri 30 Oct— 20:03No data—
Thu 29 Oct— 20:030 min—
Wed 28 Oct— 20:03No data—
Tue 27 Oct— 20:040 min—
Mon 26 Oct— 20:150 min—
Fri 23 Oct— 20:040 min—
Thu 22 Oct— 20:100 min—
Wed 21 Oct— 20:060 min—
Tue 20 Oct— 20:030 min—
Mon 19 Oct— 20:04No data—
Fri 16 OctZaandam 20:040 min—
Thu 15 Oct— 20:05No data—
Wed 14 OctKoog aan de Zaan 20:04No data—
Tue 13 Oct— 20:03No data—
Mon 12 Oct— 20:040 min—
Fri 9 Oct— 20:040 min—
Thu 8 Oct— 02:250 min—
Tue 6 Oct— 20:09+3 min+3 min
Mon 17 AugZaandijk Zaanse Schans 19:58No data—
Fri 14 AugAmsterdam Sloterdijk 20:10No data—
Thu 13 AugAmsterdam Sloterdijk 20:18No data—
Wed 12 AugAmsterdam Sloterdijk 20:10No data—
Tue 11 AugAmsterdam Sloterdijk 20:10No data—
Mon 10 AugAmsterdam Sloterdijk 20:10No data—