Train NS 4074 Rotterdam Centraal – Uitgeest

Rotterdam Centraal 20:54 → Uitgeest 22:42 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 20:54 from Rotterdam Centraal · Tue 10 Nov

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

  • Sat 10 Oct Max en route +12 min · last fix heading to Amsterdam Amstel +12 min
  • Mon 2 Nov Max en route +7 min · last fix heading to — +5 min
  • Fri 23 Oct Max en route +6 min · last fix heading to — +5 min
  • Tue 6 Oct Max en route +6 min · last fix heading to — +5 min
  • Mon 12 Oct Max en route +3 min · last fix heading to — +3 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 83% · 24
  • 3–10 min 14% · 4
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=6
  • 75% T n=4
  • 100% W n=4
  • 100% T n=2
  • 75% F n=4
  • 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, 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
20:54on time on time
20:59≈ on time ≈ on time
21:03 / 21:04≈ on time ≈ on time
21:07≈ on time ≈ on time
21:11≈ on time ≈ +1 min
21:18 / 21:19≈ on time ≈ +1 min
21:22≈ on time ≈ +1 min
21:31 / 21:33≈ on time ≈ +1 min
21:41≈ on time ≈ +2 min
21:50≈ on time ≈ +2 min
21:53≈ on time ≈ +2 min
21:56≈ on time ≈ +2 min
21:58≈ on time ≈ +2 min
22:02≈ on time ≈ +2 min
22:06≈ on time ≈ +3 min
22:11 / 22:13≈ on time ≈ +3 min
22:18≈ on time ≈ +3 min
22:24≈ on time ≈ +3 min
22:28≈ on time ≈ +3 min
22:30≈ on time ≈ +3 min
22:33 / 22:34≈ on time ≈ +4 min
22:38≈ on time ≈ +4 min
22:42on time +4 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— 22:430 min+1 min
Sun 8 NovKrommenie-Assendelft 22:52+1 min+2 min
Sat 7 NovKrommenie-Assendelft 22:520 min—
Fri 6 Nov— 22:530 min+24 min
Thu 5 Nov— 22:480 min—
Wed 4 Nov— 22:44+2 min+2 min
Tue 3 Nov— 22:450 min—
Mon 2 Nov— 22:49+5 min+7 min
Sun 1 NovWoerden 21:470 min—
Sat 31 OctKrommenie-Assendelft 22:52Partial coverage0 min—
Fri 30 Oct— 22:46No data—
Wed 28 Oct— 22:450 min—
Tue 27 Oct— 22:440 min—
Mon 26 Oct— 22:430 min—
Sun 25 OctKrommenie-Assendelft 22:54No data—
Sat 24 OctKrommenie-Assendelft 22:480 min—
Fri 23 Oct— 22:54+5 min+6 min
Thu 22 Oct— 22:44No data—
Wed 21 Oct— 22:440 min—
Tue 20 Oct— 22:44No data—
Mon 19 Oct— 22:450 min—
Sun 18 OctKrommenie-Assendelft 22:54+1 min+3 min
Sat 17 OctZaandijk Zaanse Schans 22:470 min—
Fri 16 Oct— 22:36+1 min+1 min
Thu 15 Oct— 22:36No data—
Wed 14 Oct— 22:42No data—
Tue 13 Oct— 22:400 min—
Mon 12 Oct— 22:42+3 min+3 min
Sun 11 OctWoerden 21:470 min—
Sat 10 OctAmsterdam Amstel 23:06Partial coverage+12 min+12 min