Train NS 4180 Hoofddorp – Enkhuizen

Hoofddorp 23:13 → Enkhuizen 00:29 Daily 1 h 16 min · 15 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 18 November 0 min

Next service: today 23:13 from Hoofddorp · Thu 19 Nov

Next departure 23:13 today · Hoofddorp
On-time · 30 days
100%
25/25 runs under 3 min
RT coverage: 25 full · 0 partial · 4 no data
On-time · 90 days
98%
39/40 runs under 3 min
RT coverage: 40 full · 0 partial · 16 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Enkhuizen, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Mon 19 Oct Max en route +24 min · last fix heading to — +24 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 40 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
23:13on time on time
23:17 / 23:18≈ on time ≈ on time
23:25≈ on time ≈ on time
23:29 / 23:33≈ on time ≈ on time
23:39≈ on time ≈ on time
23:44≈ on time ≈ on time
23:50≈ on time ≈ on time
23:53≈ on time ≈ on time
23:55≈ on time ≈ on time
00:07 / 00:08≈ on time ≈ on time
00:12 / 00:13≈ on time ≈ +1 min
00:19≈ on time ≈ +1 min
00:24≈ on time ≈ +1 min
00:26≈ on time ≈ +1 min
00:29on time +1 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
Wed 18 Nov— 00:290 min—
Tue 17 Nov— 00:180 min+3 min
Mon 16 NovAmsterdam Lelylaan 00:14+1 min+3 min
Sun 15 NovHoorn 00:220 min—
Sat 14 NovHoofddorp 00:140 min—
Fri 13 Nov— 00:130 min—
Thu 12 Nov— 00:340 min+4 min
Wed 11 Nov— 00:290 min—
Tue 10 Nov— 00:140 min+1 min
Mon 9 Nov— 00:14+1 min+1 min
Sun 8 NovHoorn 00:220 min—
Sat 7 NovAmsterdam Lelylaan 00:190 min+3 min
Fri 6 Nov— 00:130 min—
Thu 5 Nov— 00:340 min—
Wed 4 Nov— 00:290 min—
Tue 3 Nov— 00:140 min—
Mon 2 Nov— 00:140 min—
Sun 1 NovHoorn 00:220 min—
Sat 31 OctSchiphol Airport 00:13No data—
Fri 30 Oct— 00:14No data—
Thu 29 Oct— 00:30+1 min—
Wed 28 Oct— 00:300 min—
Tue 27 Oct— 00:160 min—
Mon 26 Oct— 00:230 min—
Sun 25 OctHoorn 00:23No data—
Sat 24 Oct— 00:14No data—
Fri 23 Oct— 00:140 min—
Thu 22 Oct— 00:330 min—
Wed 21 Oct— 00:350 min—
Tue 20 Oct— 00:220 min—