Train NS 4083 Uitgeest – Rotterdam Centraal

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

It has not run yet today

Last recorded run: Monday 9 November +1 min

Next service: today 21:18 from Uitgeest · Tue 10 Nov

Next departure 21:18 today · Uitgeest
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 20 full · 0 partial · 7 no data
On-time · 90 days
85%
23/27 runs under 3 min
RT coverage: 27 full · 0 partial · 23 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
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

  • Fri 9 Oct Max en route +8 min · last fix heading to — +8 min
  • Wed 7 Oct Max en route +8 min · last fix heading to — +8 min
  • Tue 6 Oct Max en route +3 min · last fix heading to — +3 min
  • Mon 5 Oct Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 85% · 23
  • 3–10 min 15% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 27 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:18on time on time
21:22≈ on time ≈ on time
21:26≈ on time ≈ on time
21:29≈ on time ≈ on time
21:32≈ on time ≈ on time
21:35≈ on time ≈ +1 min
21:41≈ on time ≈ +1 min
21:47 / 21:49≈ on time ≈ +1 min
21:54≈ on time ≈ +1 min
21:58≈ on time ≈ +1 min
22:01≈ on time ≈ +1 min
22:04≈ on time ≈ +1 min
22:06≈ on time ≈ +1 min
22:10≈ on time ≈ +2 min
22:18≈ on time ≈ +2 min
22:26 / 22:28≈ on time ≈ +2 min
22:37≈ on time ≈ +2 min
22:40 / 22:41≈ on time ≈ +2 min
22:48≈ on time ≈ +3 min
22:51≈ on time ≈ +3 min
22:54≈ on time ≈ +3 min
22:58≈ on time ≈ +3 min
23:04on time +3 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
Mon 9 Nov— 23:04+1 min—
Sun 8 NovGouda Goverwelle 22:520 min—
Sat 7 NovGouda Goverwelle 22:52+1 min+2 min
Fri 6 Nov— 23:040 min—
Thu 5 Nov— 23:090 min—
Wed 4 Nov— 23:040 min—
Mon 2 Nov— 21:190 min—
Sun 1 NovRotterdam Noord 23:130 min—
Sat 31 OctRotterdam Noord 23:120 min—
Fri 30 Oct— 23:05No data—
Thu 29 Oct— 23:05+1 min—
Wed 28 Oct— 23:050 min—
Tue 27 Oct— 23:120 min—
Mon 26 Oct— 23:050 min—
Sun 25 OctZoetermeer 23:16No data—
Sat 24 OctZaandam 23:100 min—
Fri 23 Oct— 23:03+1 min+1 min
Thu 22 Oct— 23:060 min—
Wed 21 Oct— 23:25No data—
Tue 20 Oct— 23:04No data—
Sun 18 OctBreukelen 22:33+1 min+1 min
Sat 17 OctGouda Goverwelle 22:530 min—
Fri 16 Oct— 23:06+1 min+1 min
Thu 15 Oct— 23:05No data—
Wed 14 Oct— 23:05No data—
Tue 13 Oct— 23:05No data—
Mon 12 Oct— 23:050 min—
Sun 11 OctRotterdam Noord 23:13+1 min—
Sat 10 OctAmsterdam Bijlmer ArenA 22:180 min—
Fri 9 Oct— 23:19+8 min+8 min