Train NS 4072 Rotterdam Centraal – Uitgeest

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

It has not run yet today

Last recorded run: Friday 13 November 0 min

Next service: today 20:24 from Rotterdam Centraal · Sat 14 Nov

Next departure 20:24 today · Rotterdam Centraal
On-time · 30 days
82%
18/22 runs under 3 min
RT coverage: 21 full · 1 partial · 6 no data
On-time · 90 days
83%
25/30 runs under 3 min
RT coverage: 28 full · 2 partial · 24 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: +9 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

  • Thu 12 Nov Max en route +21 min · last fix heading to — +20 min
  • Wed 4 Nov Max en route +9 min · last fix heading to — +9 min
  • Mon 2 Nov Max en route +9 min · last fix heading to — +9 min
  • Wed 11 Nov Max en route +5 min · last fix heading to — +5 min
  • Sat 10 Oct Max en route +5 min · last fix heading to Wormerveer +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 83% · 25
  • 3–10 min 13% · 4
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 100% T n=3
  • 50% W n=4
  • 50% T n=2
  • 100% F n=6
  • 80% 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, 30 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
20:24on time on time
20:29≈ on time ≈ on time
20:33 / 20:34≈ on time ≈ +1 min
20:37≈ on time ≈ +1 min
20:41≈ on time ≈ +1 min
20:48 / 20:49≈ on time ≈ +1 min
20:52≈ on time ≈ +2 min
21:01 / 21:03≈ on time ≈ +2 min
21:11≈ on time ≈ +3 min
21:20≈ on time ≈ +3 min
21:23≈ on time ≈ +3 min
21:26≈ on time ≈ +4 min
21:28≈ on time ≈ +4 min
21:32≈ on time ≈ +4 min
21:36≈ on time ≈ +4 min
21:41 / 21:43≈ on time ≈ +5 min
21:48≈ on time ≈ +5 min
21:54≈ on time ≈ +5 min
21:58≈ on time ≈ +6 min
22:00≈ on time ≈ +6 min
22:03 / 22:04≈ on time ≈ +6 min
22:08≈ on time ≈ +6 min
22: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
Fri 13 Nov— 22:140 min—
Thu 12 Nov— 22:54+20 min+21 min
Wed 11 Nov— 22:19+5 min+5 min
Tue 10 Nov— 22:130 min—
Mon 9 Nov— 22:140 min—
Sun 8 NovKrommenie-Assendelft 22:24+3 min+4 min
Sat 7 NovKrommenie-Assendelft 22:220 min—
Fri 6 Nov— 22:140 min+1 min
Thu 5 Nov— 22:14No data—
Wed 4 Nov— 22:24+9 min+9 min
Tue 3 Nov— 22:20No data—
Mon 2 Nov— 22:29+9 min+9 min
Sun 1 NovWoerden 21:180 min—
Sat 31 OctKrommenie-Assendelft 22:22Partial coverage0 min—
Fri 30 Oct— 22:130 min—
Wed 28 Oct— 22:130 min—
Tue 27 Oct— 22:140 min—
Mon 26 Oct— 22:150 min—
Sun 25 OctKrommenie-Assendelft 22:21No data—
Sat 24 OctKrommenie-Assendelft 22:200 min—
Fri 23 Oct— 22:16+1 min+3 min
Thu 22 Oct— 22:16No data—
Wed 21 Oct— 22:14No data—
Tue 20 Oct— 22:14No data—
Mon 19 Oct— 22:150 min—
Sun 18 OctKrommenie-Assendelft 22:22+1 min+1 min
Sat 17 OctZaandijk Zaanse Schans 22:150 min—
Fri 16 Oct— 22:10+3 min+3 min
Thu 15 Oct— 22:08No data—
Wed 14 Oct— 22:06No data—