Train NS 4085 Uitgeest – Rotterdam Centraal

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

It has not run yet today

Last recorded run: Tuesday 10 November 0 min

Next service: today 21:48 from Uitgeest · Wed 11 Nov

Next departure 21:48 today · Uitgeest
On-time · 30 days
96%
23/24 runs under 3 min
RT coverage: 24 full · 0 partial · 5 no data
On-time · 90 days
94%
30/32 runs under 3 min
RT coverage: 32 full · 0 partial · 21 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 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

  • Sun 18 Oct Max en route +18 min · last fix heading to Breukelen +18 min
  • Mon 5 Oct Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 30
  • 3–10 min 3% · 1
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 100% T n=5
  • 100% W n=4
  • 100% T n=3
  • 100% F n=5
  • 100% S n=5
  • 75% S n=4

Stops and timetable

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

Last 90 days, 32 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
21:48on time on time
21:52≈ on time ≈ on time
21:56≈ on time ≈ on time
21:59≈ on time ≈ on time
22:02≈ on time ≈ on time
22:05≈ on time ≈ on time
22:11≈ on time ≈ on time
22:17 / 22:19≈ on time ≈ +1 min
22:24≈ on time ≈ +1 min
22:28≈ on time ≈ +1 min
22:31≈ on time ≈ +1 min
22:34≈ on time ≈ +1 min
22:36≈ on time ≈ +1 min
22:40≈ on time ≈ +1 min
22:48≈ on time ≈ +1 min
22:56 / 22:58≈ on time ≈ +1 min
23:07≈ on time ≈ +1 min
23:10 / 23:11≈ on time ≈ +1 min
23:18≈ on time ≈ +2 min
23:21≈ on time ≈ +2 min
23:24≈ on time ≈ +2 min
23:28≈ on time ≈ +2 min
23: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
Tue 10 Nov— 23:340 min—
Mon 9 Nov— 23:340 min—
Sun 8 NovGouda Goverwelle 23:23+1 min—
Sat 7 NovGouda Goverwelle 23:220 min—
Fri 6 Nov— 23:340 min—
Thu 5 Nov— 23:340 min—
Wed 4 Nov— 23:34+1 min—
Tue 3 Nov— 23:340 min—
Mon 2 Nov— 23:34+2 min+2 min
Sun 1 NovRotterdam Noord 23:420 min—
Sat 31 OctCapelle Schollevaar 23:350 min—
Fri 30 Oct— 23:350 min—
Thu 29 Oct— 23:35+2 min+2 min
Wed 28 Oct— 23:400 min—
Tue 27 Oct— 23:360 min—
Mon 26 Oct— 23:350 min—
Sun 25 OctZoetermeer 23:39No data—
Sat 24 OctAmsterdam Holendrecht 23:370 min—
Fri 23 Oct— 23:33+1 min+1 min
Thu 22 Oct— 23:32No data—
Wed 21 Oct— 23:33No data—
Tue 20 Oct— 23:34No data—
Mon 19 Oct— 22:580 min—
Sun 18 OctBreukelen 23:16+18 min+18 min
Sat 17 OctGouda Goverwelle 23:260 min—
Fri 16 Oct— 23:350 min—
Thu 15 Oct— 23:37No data—
Wed 14 Oct— 23:350 min—
Tue 13 Oct— 23:520 min—
Mon 12 Oct— 23:350 min—