Train NS 4076 Rotterdam Centraal – Uitgeest

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

It has not run yet today

Last recorded run: Monday 9 November 0 min

Next service: today 21:24 from Rotterdam Centraal · Tue 10 Nov

Next departure 21:24 today · Rotterdam Centraal
On-time · 30 days
82%
18/22 runs under 3 min
RT coverage: 22 full · 0 partial · 7 no data
On-time · 90 days
86%
25/29 runs under 3 min
RT coverage: 29 full · 0 partial · 23 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +6 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 12 Oct Max en route +26 min · last fix heading to — +26 min
  • Fri 16 Oct Max en route +10 min · last fix heading to — +9 min
  • Fri 23 Oct Max en route +8 min · last fix heading to — +6 min
  • Wed 14 Oct Max en route +5 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 86% · 25
  • 3–10 min 10% · 3
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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