Train NS 4061 Uitgeest – Rotterdam Centraal

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

It has not run yet today

Last recorded run: Friday 6 November +1 min

Next service: today 15:48 from Uitgeest · Sat 7 Nov

Next departure 15:48 today · Uitgeest
On-time · 30 days
89%
17/19 runs under 3 min
RT coverage: 15 full · 4 partial · 10 no data
On-time · 90 days
91%
21/23 runs under 3 min
RT coverage: 17 full · 6 partial · 65 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: +3 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 +15 min · last fix heading to Rotterdam Noord +15 min
  • Mon 26 Oct Max en route +13 min · last fix heading to Rotterdam Noord +13 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 21
  • 3–10 min 0% · 0
  • 10–30 min 9% · 2
  • 30+ min 0% · 0

On-time by weekday

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