Train NS 4079 Uitgeest – Rotterdam Centraal

Uitgeest 20:18 → Rotterdam Centraal 22:04 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 20:18 from Uitgeest · Wed 11 Nov

Next departure 20:18 today · Uitgeest
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 19 full · 0 partial · 10 no data
On-time · 90 days
96%
26/27 runs under 3 min
RT coverage: 27 full · 0 partial · 28 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

  • Tue 6 Oct Max en route +4 min · last fix heading to — +4 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 96% · 26
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 75% T n=4
  • 100% W n=2
  • 100% T n=2
  • 100% 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
20:18on time on time
20:22≈ on time ≈ on time
20:26≈ on time ≈ on time
20:29≈ on time ≈ on time
20:32≈ on time ≈ on time
20:35≈ on time ≈ on time
20:41≈ on time ≈ on time
20:47 / 20:49≈ on time ≈ on time
20:54≈ on time ≈ +1 min
20:58≈ on time ≈ +1 min
21:01≈ on time ≈ +1 min
21:04≈ on time ≈ +1 min
21:06≈ on time ≈ +1 min
21:10≈ on time ≈ +1 min
21:18≈ on time ≈ +1 min
21:26 / 21:28≈ on time ≈ +1 min
21:37≈ on time ≈ +1 min
21:40 / 21:41≈ on time ≈ +1 min
21:48≈ on time ≈ +1 min
21:51≈ on time ≈ +1 min
21:54≈ on time ≈ +1 min
21:58≈ on time ≈ +1 min
22:04on 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— 22:040 min—
Mon 9 Nov— 22:04+1 min—
Sun 8 NovGouda Goverwelle 21:520 min+1 min
Sat 7 NovGouda Goverwelle 21:520 min—
Fri 6 Nov— 22:04+1 min—
Thu 5 Nov— 22:04No data—
Wed 4 Nov— 22:08+2 min+5 min
Tue 3 Nov— 22:050 min—
Mon 2 Nov— 22:04+1 min—
Sun 1 NovRotterdam Noord 22:130 min—
Sat 31 OctRotterdam Noord 22:140 min—
Fri 30 Oct— 22:05No data—
Thu 29 Oct— 22:05+1 min—
Wed 28 Oct— 22:10No data—
Tue 27 Oct— 22:060 min—
Mon 26 Oct— 22:050 min—
Sun 25 OctZoetermeer 22:08No data—
Sat 24 OctZoetermeer 22:070 min—
Fri 23 Oct— 22:040 min—
Thu 22 Oct— 21:29No data—
Wed 21 Oct— 22:03No data—
Tue 20 Oct— 22:08No data—
Mon 19 Oct— 21:300 min—
Sun 18 OctBreukelen 21:320 min—
Sat 17 OctGouda Goverwelle 21:530 min—
Fri 16 Oct— 22:06+1 min+1 min
Thu 15 Oct— 22:14No data—
Wed 14 Oct— 22:10No data—
Tue 13 Oct— 22:06No data—
Mon 12 Oct— 22:060 min—