Train NS 4064 Rotterdam Centraal – Uitgeest

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

It has not run yet today

Last recorded run: Wednesday 4 November +1 min

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

Next departure 18:24 today · Rotterdam Centraal
On-time · 30 days
96%
22/23 runs under 3 min
RT coverage: 21 full · 2 partial · 4 no data
On-time · 90 days
92%
24/26 runs under 3 min
RT coverage: 24 full · 2 partial · 42 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 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

  • Sat 10 Oct Max en route +3 min · last fix heading to Krommenie-Assendelft +3 min
  • Mon 5 Oct Max en route +4 min · last fix heading to — +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 92% · 24
  • 3–10 min 8% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=3
  • 100% T n=4
  • 100% W n=4
  • 100% T n=4
  • 100% F n=3
  • 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:24on time on time
18:29≈ on time ≈ on time
18:33 / 18:34≈ on time ≈ on time
18:37≈ on time ≈ on time
18:41≈ on time ≈ on time
18:48 / 18:49≈ on time ≈ on time
18:52≈ on time ≈ +1 min
19:01 / 19:03≈ on time ≈ +1 min
19:11≈ on time ≈ +1 min
19:20≈ on time ≈ +1 min
19:23≈ on time ≈ +1 min
19:26≈ on time ≈ +1 min
19:28≈ on time ≈ +1 min
19:32≈ on time ≈ +1 min
19:36≈ on time ≈ +1 min
19:41 / 19:43≈ on time ≈ +1 min
19:48≈ on time ≈ +1 min
19:54≈ on time ≈ +1 min
19:58≈ on time ≈ +1 min
20:00≈ on time ≈ +1 min
20:03 / 20:04≈ on time ≈ +1 min
20:08≈ on time ≈ +1 min
20:12on 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
Wed 4 Nov— 20:14+1 min+1 min
Sun 1 NovWoerden 19:180 min+2 min
Sat 31 OctKrommenie-Assendelft 20:23+1 min+3 min
Fri 30 OctGouda 20:20No data—
Thu 29 Oct— 20:140 min—
Wed 28 Oct— 20:140 min—
Tue 27 Oct— 20:140 min—
Mon 26 OctAmsterdam Sloterdijk 20:14No data—
Sun 25 OctKrommenie-Assendelft 20:21No data—
Sat 24 OctKrommenie-Assendelft 20:230 min—
Fri 23 OctDuivendrecht 20:150 min—
Thu 22 OctLansingerland-Zoetermeer 20:520 min—
Wed 21 OctZoetermeer 20:160 min—
Tue 20 OctLansingerland-Zoetermeer 20:140 min—
Mon 19 Oct— 20:130 min—
Sun 18 OctKrommenie-Assendelft 20:22+1 min+1 min
Sat 17 OctZaandijk Zaanse Schans 20:150 min—
Fri 16 OctZaandam 20:200 min—
Thu 15 OctRotterdam Noord 20:220 min—
Wed 14 OctAmsterdam Sloterdijk 20:08No data—
Tue 13 OctCapelle Schollevaar 20:230 min—
Mon 12 OctNieuwerkerk a/d IJssel 20:070 min—
Sun 11 OctWoerden 19:170 min—
Sat 10 OctKrommenie-Assendelft 20:25Partial coverage+3 min+3 min
Fri 9 OctRotterdam Alexander 20:14Partial coverage0 min—
Thu 8 Oct— 20:150 min—
Wed 7 Oct— 20:18+3 min+3 min
Tue 6 Oct— 20:100 min+8 min
Mon 5 Oct— 19:44+3 min+4 min
Sun 4 OctAmsterdam Muiderpoort 19:53No data—