Train NS 4185 Hoorn Kersenboogerd – Hoofddorp

Hoorn Kersenboogerd 21:48 → Hoofddorp 22:47 Daily 0 h 59 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 18 November 0 min

Next service: today 21:48 from Hoorn Kersenboogerd · Thu 19 Nov

Next departure 21:48 today · Hoorn Kersenboogerd
On-time · 30 days
94%
16/17 runs under 3 min
RT coverage: 15 full · 2 partial · 11 no data
On-time · 90 days
97%
28/29 runs under 3 min
RT coverage: 25 full · 4 partial · 27 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: 0 min

Last 30 days

Arrival delay at Hoofddorp, 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 23 Oct Max en route +9 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 28
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=4
  • 100% W n=5
  • 100% T n=3
  • 80% F n=5
  • 100% S n=2
  • 100% S n=4

Stops and timetable

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

Last 90 days, 29 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:48on time on time
21:52 / 21:53≈ on time ≈ on time
22:05≈ on time ≈ on time
22:07≈ on time ≈ on time
22:10≈ on time ≈ on time
22:17≈ on time ≈ on time
22:20≈ on time ≈ on time
22:26 / 22:31≈ on time ≈ on time
22:35≈ on time ≈ on time
22:41 / 22:43≈ on time ≈ +1 min
22:47on 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— 22:480 min—
Tue 17 Nov— 22:480 min—
Mon 16 Nov— 22:490 min—
Sun 15 NovSchiphol Airport 22:57Partial coverage0 min—
Sat 14 NovSchiphol Airport 22:57Partial coverage+1 min+1 min
Fri 13 Nov— 22:480 min—
Thu 12 Nov— 22:480 min—
Wed 11 Nov— 22:480 min—
Tue 10 Nov— 22:480 min—
Mon 9 Nov— 22:490 min—
Sun 8 NovAmsterdam Lelylaan 22:490 min—
Sat 7 Nov— 21:49No data—
Fri 6 Nov— 22:480 min—
Thu 5 Nov— 22:49No data—
Wed 4 Nov— 22:490 min—
Tue 3 Nov— 22:48No data—
Mon 2 Nov— 22:480 min—
Sun 1 NovSchiphol Airport 22:57No data—
Sat 31 OctSchiphol Airport 22:57No data—
Thu 29 Oct— 22:400 min—
Wed 28 Oct— 22:480 min—
Tue 27 Oct— 22:49No data—
Mon 26 Oct— 22:48No data—
Sun 25 OctSchiphol Airport 22:57No data—
Sat 24 OctAmsterdam Lelylaan 22:48No data—
Fri 23 Oct— 22:59+5 min+9 min
Thu 22 Oct— 22:41No data—
Wed 21 Oct— 22:48No data—
Tue 20 Oct— 22:480 min—
Mon 19 Oct— 23:030 min—