Train NS 4068 Rotterdam Centraal – Uitgeest

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

It has not run yet today

Last recorded run: Saturday 14 November +2 min

Next service: today 19:24 from Rotterdam Centraal · Sun 15 Nov

Next departure 19:24 today · Rotterdam Centraal
On-time · 30 days
92%
22/24 runs under 3 min
RT coverage: 23 full · 1 partial · 5 no data
On-time · 90 days
79%
26/33 runs under 3 min
RT coverage: 32 full · 1 partial · 25 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+6min
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

  • Fri 9 Oct Max en route +8 min · last fix heading to — +8 min
  • Fri 13 Nov Max en route +8 min · last fix heading to — +7 min
  • Wed 7 Oct Max en route +7 min · last fix heading to — +7 min
  • Sat 10 Oct Max en route +8 min · last fix heading to Krommenie-Assendelft +6 min
  • Sun 18 Oct Max en route +4 min · last fix heading to Krommenie-Assendelft +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 79% · 26
  • 3–10 min 21% · 7
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 67% T n=3
  • 75% W n=4
  • 100% T n=5
  • 50% F n=6
  • 83% S n=6
  • 75% S n=4

Stops and timetable

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

Last 90 days, 33 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:24on time on time
19:29≈ on time ≈ on time
19:33 / 19:34≈ on time ≈ +1 min
19:37≈ on time ≈ +1 min
19:41≈ on time ≈ +1 min
19:48 / 19:49≈ on time ≈ +1 min
19:52≈ on time ≈ +2 min
20:01 / 20:03≈ on time ≈ +2 min
20:11≈ on time ≈ +3 min
20:20≈ on time ≈ +3 min
20:23≈ on time ≈ +3 min
20:26≈ on time ≈ +4 min
20:28≈ on time ≈ +4 min
20:32≈ on time ≈ +4 min
20:36≈ on time ≈ +4 min
20:41 / 20:43≈ on time ≈ +4 min
20:48≈ on time ≈ +5 min
20:54≈ on time ≈ +5 min
20:58≈ on time ≈ +5 min
21:00≈ on time ≈ +6 min
21:03 / 21:04≈ on time ≈ +6 min
21:08≈ on time ≈ +6 min
21:12on time +6 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
Sat 14 NovKrommenie-Assendelft 21:23Partial coverage+2 min+2 min
Fri 13 Nov— 21:27+7 min+8 min
Thu 12 Nov— 21:14+1 min+1 min
Wed 11 Nov— 21:140 min—
Tue 10 Nov— 21:140 min—
Mon 9 Nov— 21:14+1 min+1 min
Sun 8 NovKrommenie-Assendelft 21:22+1 min+1 min
Sat 7 NovKrommenie-Assendelft 21:220 min—
Fri 6 Nov— 21:140 min+1 min
Thu 5 Nov— 21:140 min—
Wed 4 Nov— 21:19No data—
Tue 3 Nov— 21:18No data—
Mon 2 Nov— 21:140 min—
Sun 1 NovWoerden 20:170 min—
Sat 31 OctKrommenie-Assendelft 21:230 min—
Fri 30 Oct— 21:180 min—
Thu 29 Oct— 21:15+2 min+3 min
Wed 28 Oct— 21:210 min—
Tue 27 Oct— 21:14No data—
Mon 26 OctLansingerland-Zoetermeer 19:47No data—
Sun 25 OctKrommenie-Assendelft 21:24No data—
Sat 24 OctKrommenie-Assendelft 21:230 min—
Fri 23 OctDen Haag Centraal 21:16+3 min+3 min
Thu 22 Oct— 21:160 min—
Wed 21 Oct— 21:270 min—
Tue 20 Oct— 21:150 min—
Mon 19 Oct— 21:140 min—
Sun 18 OctKrommenie-Assendelft 21:25+4 min+4 min
Sat 17 OctZaandijk Zaanse Schans 21:160 min—
Fri 16 OctGouda 21:10+4 min+4 min