Train NS 4070 Rotterdam Centraal – Uitgeest

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

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 19:54 from Rotterdam Centraal · Thu 5 Nov

Next departure 19:54 today · Rotterdam Centraal
On-time · 30 days
91%
20/22 runs under 3 min
RT coverage: 22 full · 0 partial · 6 no data
On-time · 90 days
92%
23/25 runs under 3 min
RT coverage: 25 full · 0 partial · 29 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: +2 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 16 Oct Max en route +12 min · last fix heading to Rotterdam Centraal +12 min
  • Mon 2 Nov Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 4% · 1
  • On time 88% · 22
  • 3–10 min 4% · 1
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 100% T n=2
  • 100% W n=3
  • 100% T n=3
  • 75% F n=4
  • 100% S n=5
  • 100% S n=3

Stops and timetable

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

Last 90 days, 25 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:54on time on time
19:59≈ on time ≈ on time
20:03 / 20:04≈ on time ≈ on time
20:07≈ on time ≈ on time
20:11≈ on time ≈ on time
20:18 / 20:19≈ on time ≈ +1 min
20:22≈ on time ≈ +1 min
20:31 / 20:33≈ on time ≈ +1 min
20:41≈ on time ≈ +1 min
20:50≈ on time ≈ +1 min
20:53≈ on time ≈ +1 min
20:56≈ on time ≈ +1 min
20:58≈ on time ≈ +1 min
21:02≈ on time ≈ +1 min
21:06≈ on time ≈ +1 min
21:11 / 21:13≈ on time ≈ +1 min
21:18≈ on time ≈ +1 min
21:24≈ on time ≈ +1 min
21:28≈ on time ≈ +1 min
21:30≈ on time ≈ +1 min
21:33 / 21:34≈ on time ≈ +2 min
21:38≈ on time ≈ +2 min
21:42on time +2 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— 21:490 min+8 min
Tue 3 Nov— 21:450 min—
Mon 2 Nov— 21:44+4 min+4 min
Sun 1 NovWoerden 20:470 min—
Sat 31 OctKrommenie-Assendelft 21:530 min—
Fri 30 Oct— 22:040 min—
Thu 29 Oct— 21:44+1 min—
Wed 28 Oct— 21:450 min—
Tue 27 Oct— 21:44No data—
Mon 26 Oct— 21:440 min—
Sun 25 OctKrommenie-Assendelft 21:53No data—
Sat 24 OctKrommenie-Assendelft 21:550 min—
Fri 23 Oct— 21:450 min+2 min
Thu 22 Oct— 21:44No data—
Wed 21 Oct— 21:44No data—
Mon 19 Oct— 21:440 min—
Sun 18 OctKrommenie-Assendelft 21:520 min—
Sat 17 OctZaandijk Zaanse Schans 21:460 min—
Fri 16 OctRotterdam Centraal 21:52+12 min+12 min
Thu 15 Oct— 21:380 min—
Wed 14 Oct— 21:40No data—
Tue 13 Oct— 21:40No data—
Mon 12 Oct— 21:380 min—
Sun 11 OctWoerden 20:47+1 min—
Sat 10 OctKrommenie-Assendelft 21:52+2 min+3 min
Fri 9 Oct— 21:44+1 min+1 min
Thu 8 Oct— 21:440 min+1 min
Wed 7 Oct— 21:440 min—
Tue 6 Oct— 21:430 min—
Mon 5 Oct— 21:130 min—