Train NS 4059 Uitgeest – Rotterdam Centraal

Uitgeest 15:18 → Rotterdam Centraal 17:04 Daily 1 h 46 min · 23 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 15:18 from Uitgeest · Fri 6 Nov

Next departure 15:18 today · Uitgeest
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 12 full · 5 partial · 12 no data
On-time · 90 days
100%
20/20 runs under 3 min
RT coverage: 13 full · 7 partial · 68 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Rotterdam Centraal, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 20
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 20 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
15:18on time on time
15:22≈ on time ≈ on time
15:26≈ on time ≈ on time
15:29≈ on time ≈ on time
15:32≈ on time ≈ on time
15:35≈ on time ≈ on time
15:41≈ on time ≈ on time
15:47 / 15:49≈ on time ≈ on time
15:54≈ on time ≈ on time
15:58≈ on time ≈ on time
16:01≈ on time ≈ on time
16:04≈ on time ≈ on time
16:06≈ on time ≈ on time
16:10≈ on time ≈ on time
16:18≈ on time ≈ on time
16:26 / 16:28≈ on time ≈ +1 min
16:37≈ on time ≈ +1 min
16:40 / 16:41≈ on time ≈ +1 min
16:48≈ on time ≈ +1 min
16:51≈ on time ≈ +1 min
16:54≈ on time ≈ +1 min
16:58≈ on time ≈ +1 min
17:04on time +1 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
Thu 5 NovRotterdam Noord 17:12No data—
Wed 4 NovRotterdam Noord 17:12Partial coverage0 min—
Tue 3 NovRotterdam Noord 17:12No data—
Mon 2 NovRotterdam Noord 17:12No data—
Sun 1 NovRotterdam Noord 17:130 min—
Sat 31 OctRotterdam Noord 17:120 min—
Fri 30 OctRotterdam Noord 17:15No data—
Thu 29 OctRotterdam Noord 17:12No data—
Wed 28 OctRotterdam Noord 17:14Partial coverage0 min—
Tue 27 OctRotterdam Noord 17:12No data—
Mon 26 OctRotterdam Noord 17:13No data—
Sun 25 OctZoetermeer 17:08No data—
Sat 24 OctZoetermeer 17:09+1 min—
Fri 23 OctZoetermeer 17:110 min—
Thu 22 OctZoetermeer 17:080 min—
Wed 21 OctZoetermeer 17:140 min—
Tue 20 OctZoetermeer 17:080 min—
Mon 19 OctUtrecht Zuilen 16:430 min—
Sun 18 OctBreukelen 16:33+1 min+1 min
Sat 17 OctGouda Goverwelle 16:520 min—
Fri 16 OctRotterdam Noord 17:13No data—
Thu 15 OctRotterdam Noord 17:14No data—
Wed 14 OctRotterdam Noord 17:15No data—
Tue 13 OctRotterdam Noord 17:17No data—
Mon 12 OctRotterdam Noord 17:15+1 min—
Sun 11 OctRotterdam Noord 17:130 min—
Sat 10 OctRotterdam Noord 17:15Partial coverage0 min—
Fri 9 OctRotterdam Noord 17:13Partial coverage0 min—
Thu 8 OctRotterdam Noord 17:12Partial coverage0 min—
Wed 7 OctRotterdam Noord 17:12Partial coverage+1 min+1 min