Train NS 4089 Uitgeest → Rotterdam Centraal

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

NS 4089 Uitgeest–Rotterdam Centraal: final delay under 3 min on 26 of its 28 runs with data in the last 30 days (93%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 13:05 (GMT+1).

It has not run yet today

Last recorded run: Saturday 21 November +1 min

Next service: today 22:48 from Uitgeest · Sun 22 Nov

Next departure 22:48 today · Uitgeest
On-time · 30 days
93%
26/28 runs under 3 min
RT coverage: 28 full · 0 partial · 0 no data
On-time · 90 days
91%
43/47 runs under 3 min
RT coverage: 47 full · 0 partial · 11 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: 0 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 16 Oct Max en route +18 min · last fix heading to — +15 min
  • Thu 19 Nov Max en route +3 min · last fix heading to — +3 min
  • Sat 14 Nov Max en route +5 min · last fix heading to Koog aan de Zaan +3 min
  • Fri 9 Oct Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 43
  • 3–10 min 6% · 3
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=7
  • 100% W n=7
  • 86% T n=7
  • 67% F n=6
  • 86% S n=7
  • 100% S n=6

Stops and timetable

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

Last 90 days, 47 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
22:48on time on time
22:52≈ on time ≈ on time
22:56≈ on time ≈ on time
22:59≈ on time ≈ on time
23:02≈ on time ≈ on time
23:05≈ on time ≈ +1 min
23:11≈ on time ≈ +1 min
23:17 / 23:19≈ on time ≈ +1 min
23:24≈ on time ≈ +1 min
23:28≈ on time ≈ +1 min
23:31≈ on time ≈ +1 min
23:34≈ on time ≈ +1 min
23:36≈ on time ≈ +1 min
23:40≈ on time ≈ +2 min
23:48≈ on time ≈ +2 min
23:56 / 23:58≈ on time ≈ +2 min
00:07≈ on time ≈ +2 min
00:10 / 00:11≈ on time ≈ +2 min
00:18≈ on time ≈ +2 min
00:21≈ on time ≈ +2 min
00:24≈ on time ≈ +2 min
00:28≈ on time ≈ +2 min
00: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
Sat 21 Nov— 00:38+1 min+1 min
Fri 20 Nov— 00:490 min+4 min
Thu 19 Nov— 00:37+3 min+3 min
Wed 18 Nov— 00:340 min+3 min
Tue 17 Nov— 00:340 min—
Mon 16 NovAmsterdam Centraal 00:340 min—
Sun 15 NovRotterdam Noord 00:430 min—
Sat 14 NovKoog aan de Zaan 00:39+3 min+5 min
Fri 13 Nov— 00:500 min—
Thu 12 Nov— 00:340 min—
Wed 11 Nov— 00:340 min—
Tue 10 Nov— 00:340 min—
Mon 9 Nov— 00:340 min—
Sun 8 NovGouda Goverwelle 00:220 min—
Sat 7 NovAmsterdam Sloterdijk 00:140 min—
Fri 6 Nov— 01:140 min+25 min
Thu 5 Nov— 00:520 min—
Wed 4 Nov— 00:340 min—
Tue 3 Nov— 00:340 min—
Mon 2 Nov— 00:340 min—
Sun 1 NovRotterdam Noord 00:430 min—
Sat 31 OctAmsterdam Centraal 01:100 min—
Thu 29 Oct— 00:350 min—
Wed 28 Oct— 00:350 min—
Tue 27 Oct— 00:350 min—
Mon 26 Oct— 00:350 min—
Sun 25 OctZoetermeer 00:430 min—
Sat 24 Oct— 00:440 min—
Fri 23 Oct— 00:440 min+5 min
Thu 22 Oct— 00:350 min—