Train NS 4066 Rotterdam Centraal – Uitgeest

Rotterdam Centraal 18:54 → Uitgeest 20:42 Daily 1 h 48 min · 23 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November +5 min

Next service: today 18:54 from Rotterdam Centraal · Thu 5 Nov

Next departure 18:54 today · Rotterdam Centraal
On-time · 30 days
87%
20/23 runs under 3 min
RT coverage: 22 full · 1 partial · 6 no data
On-time · 90 days
88%
23/26 runs under 3 min
RT coverage: 25 full · 1 partial · 35 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 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

  • Wed 4 Nov Max en route +5 min · last fix heading to — +5 min
  • Wed 7 Oct Max en route +6 min · last fix heading to — +4 min
  • Sat 10 Oct Max en route +3 min · last fix heading to Krommenie-Assendelft +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 23
  • 3–10 min 12% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=3
  • 50% W n=4
  • 100% T n=3
  • 100% F n=4
  • 75% S n=4
  • 100% S n=4

Stops and timetable

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

Last 90 days, 26 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:54on time on time
18:59≈ on time ≈ on time
19:03 / 19:04≈ on time ≈ on time
19:07≈ on time ≈ on time
19:11≈ on time ≈ on time
19:18 / 19:19≈ on time ≈ +1 min
19:22≈ on time ≈ +1 min
19:31 / 19:33≈ on time ≈ +1 min
19:41≈ on time ≈ +1 min
19:50≈ on time ≈ +2 min
19:53≈ on time ≈ +2 min
19:56≈ on time ≈ +2 min
19:58≈ on time ≈ +2 min
20:02≈ on time ≈ +2 min
20:06≈ on time ≈ +2 min
20:11 / 20:13≈ on time ≈ +2 min
20:18≈ on time ≈ +2 min
20:24≈ on time ≈ +3 min
20:28≈ on time ≈ +3 min
20:30≈ on time ≈ +3 min
20:33 / 20:34≈ on time ≈ +3 min
20:38≈ on time ≈ +3 min
20:42on time +3 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
Wed 4 Nov— 20:48+5 min+5 min
Tue 3 Nov— 20:45No data—
Mon 2 Nov— 20:440 min—
Sun 1 NovWoerden 19:470 min—
Sat 31 OctKrommenie-Assendelft 20:57+2 min+2 min
Fri 30 OctRotterdam Centraal 20:44Partial coverage0 min—
Thu 29 Oct— 20:430 min+1 min
Wed 28 Oct— 20:170 min—
Tue 27 Oct— 20:440 min—
Mon 26 OctAbcoude 20:45No data—
Sun 25 OctKrommenie-Assendelft 20:53No data—
Sat 24 OctKrommenie-Assendelft 20:520 min—
Fri 23 OctLansingerland-Zoetermeer 20:440 min+2 min
Thu 22 Oct— 20:500 min—
Wed 21 Oct— 20:440 min—
Tue 20 Oct— 20:430 min—
Mon 19 Oct— 20:430 min—
Sun 18 OctKrommenie-Assendelft 20:55+3 min+3 min
Sat 17 OctZaandijk Zaanse Schans 20:460 min—
Fri 16 OctAmsterdam Holendrecht 20:400 min—
Thu 15 Oct— 20:52No data—
Wed 14 OctBreukelen 20:35No data—
Tue 13 Oct— 20:48No data—
Mon 12 Oct— 20:360 min—
Sun 11 OctWoerden 19:47+1 min+1 min
Sat 10 OctKrommenie-Assendelft 20:56+3 min+3 min
Fri 9 Oct— 20:440 min—
Thu 8 Oct— 20:460 min—
Wed 7 Oct— 20:46+4 min+6 min
Tue 6 Oct— 20:45+2 min+3 min