Train NS 4053 Uitgeest – Rotterdam Centraal

Uitgeest 13:48 → Rotterdam Centraal 15:34 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 13:48 from Uitgeest · Fri 6 Nov

Next departure 13:48 today · Uitgeest
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 13 full · 6 partial · 10 no data
On-time · 90 days
95%
21/22 runs under 3 min
RT coverage: 14 full · 8 partial · 66 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: +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

Worst days

  • Sat 10 Oct Max en route +17 min · last fix heading to Rotterdam Noord +17 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 21
  • 3–10 min 0% · 0
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=3
  • 100% W n=4
  • 100% T n=1
  • 100% F n=4
  • 75% 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, 22 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
13:48on time on time
13:52≈ on time ≈ on time
13:56≈ on time ≈ on time
13:59≈ on time ≈ on time
14:02≈ on time ≈ on time
14:05≈ on time ≈ on time
14:11≈ on time ≈ on time
14:17 / 14:19≈ on time ≈ +1 min
14:24≈ on time ≈ +1 min
14:28≈ on time ≈ +1 min
14:31≈ on time ≈ +1 min
14:34≈ on time ≈ +1 min
14:36≈ on time ≈ +1 min
14:40≈ on time ≈ +1 min
14:48≈ on time ≈ +1 min
14:56 / 14:58≈ on time ≈ +1 min
15:07≈ on time ≈ +1 min
15:10 / 15:11≈ on time ≈ +1 min
15:18≈ on time ≈ +2 min
15:21≈ on time ≈ +2 min
15:24≈ on time ≈ +2 min
15:28≈ on time ≈ +2 min
15:34on 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
Thu 5 NovRotterdam Noord 15:43No data—
Wed 4 NovRotterdam Noord 15:43Partial coverage+1 min+1 min
Tue 3 NovRotterdam Noord 15:54Partial coverage0 min—
Mon 2 NovRotterdam Noord 15:43No data—
Sun 1 NovRotterdam Noord 15:440 min—
Sat 31 OctRotterdam Noord 15:43Partial coverage+1 min—
Fri 30 OctRotterdam Noord 15:43Partial coverage0 min—
Thu 29 OctRotterdam Noord 15:42No data—
Wed 28 OctRotterdam Noord 15:430 min—
Tue 27 OctRotterdam Noord 15:440 min—
Mon 26 OctRotterdam Noord 22:26No data—
Sun 25 OctAmsterdam Sloterdijk 16:43No data—
Sat 24 OctZoetermeer 15:38+1 min—
Fri 23 OctZoetermeer 15:430 min—
Thu 22 OctZoetermeer 15:38No data—
Wed 21 OctZoetermeer 15:490 min—
Tue 20 OctZoetermeer 15:39No data—
Mon 19 OctUtrecht Zuilen 15:120 min—
Sun 18 OctBreukelen 15:02+2 min+2 min
Sat 17 OctGouda Goverwelle 15:220 min—
Fri 16 OctRotterdam Noord 15:450 min—
Thu 15 OctRotterdam Noord 15:43No data—
Wed 14 OctRotterdam Noord 15:43No data—
Tue 13 OctRotterdam Noord 15:44No data—
Mon 12 OctRotterdam Noord 15:430 min—
Sun 11 OctRotterdam Noord 15:43+1 min+2 min
Sat 10 OctRotterdam Noord 16:08Partial coverage+17 min+17 min
Fri 9 OctRotterdam Noord 15:430 min—
Thu 8 OctRotterdam Noord 15:43Partial coverage0 min—
Wed 7 OctRotterdam Noord 15:44Partial coverage+2 min+2 min