Train NS 4077 Uitgeest – Rotterdam Centraal

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

✓ Today’s run finished

Today, last fix heading to — at 21:34 0 min

  1. Uitgeest19:48
  2. Koog aan de Zaan20:02
  3. Amsterdam Centraal20:17
  4. Amsterdam Bijlmer ArenA20:34
  5. Woerden20:56
  6. Nieuwerkerk a/d IJssel21:18
  7. Rotterdam Centraal21:34

Next service: tomorrow 19:48 from Uitgeest · Tue 10 Nov

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

  • Wed 7 Oct Max en route +18 min · last fix heading to — +18 min
  • Sat 10 Oct Max en route +15 min · last fix heading to Rotterdam Noord +15 min
  • Wed 4 Nov Max en route +11 min · last fix heading to — +11 min
  • Mon 5 Oct Max en route +5 min · last fix heading to — +5 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 4% · 1
  • 10–30 min 11% · 3
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 100% T n=3
  • 50% W n=4
  • 100% T n=2
  • 100% F n=4
  • 80% 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
19:48on time on time
19:52≈ on time ≈ on time
19:56≈ on time ≈ +1 min
19:59≈ on time ≈ +1 min
20:02≈ on time ≈ +1 min
20:05≈ on time ≈ +1 min
20:11≈ on time ≈ +2 min
20:17 / 20:19≈ on time ≈ +2 min
20:24≈ on time ≈ +2 min
20:28≈ on time ≈ +3 min
20:31≈ on time ≈ +3 min
20:34≈ on time ≈ +3 min
20:36≈ on time ≈ +3 min
20:40≈ on time ≈ +4 min
20:48≈ on time ≈ +4 min
20:56 / 20:58≈ on time ≈ +5 min
21:07≈ on time ≈ +5 min
21:10 / 21:11≈ on time ≈ +6 min
21:18≈ on time ≈ +6 min
21:21≈ on time ≈ +6 min
21:24≈ on time ≈ +7 min
21:28≈ on time ≈ +7 min
21:34on time +7 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— 21:340 min—
Sun 8 NovGouda Goverwelle 21:220 min—
Sat 7 NovGouda Goverwelle 21:23+1 min+3 min
Fri 6 Nov— 21:34+1 min—
Thu 5 Nov— 21:34No data—
Wed 4 Nov— 21:49+11 min+11 min
Tue 3 Nov— 21:340 min—
Mon 2 Nov— 21:38+3 min+3 min
Sun 1 NovRotterdam Noord 21:430 min—
Sat 31 OctRotterdam Noord 21:440 min—
Fri 30 Oct— 21:35No data—
Thu 29 Oct— 21:350 min—
Wed 28 Oct— 21:350 min—
Tue 27 Oct— 21:36No data—
Mon 26 Oct— 21:35No data—
Sun 25 OctZoetermeer 21:42No data—
Sat 24 OctZoetermeer 21:400 min—
Fri 23 Oct— 21:360 min+1 min
Thu 22 Oct— 21:33No data—
Wed 21 Oct— 21:410 min—
Tue 20 Oct— 21:330 min—
Mon 19 Oct— 20:580 min—
Sun 18 OctBreukelen 21:04+2 min+2 min
Sat 17 OctGouda Goverwelle 21:240 min—
Fri 16 OctWormerveer 21:36+2 min+2 min
Thu 15 Oct— 21:38No data—
Wed 14 Oct— 21:35No data—
Tue 13 Oct— 21:48No data—
Mon 12 Oct— 21:500 min—
Sun 11 OctRotterdam Noord 21:430 min—