Train NS 4168 Hoofddorp – Hoorn Kersenboogerd

Hoofddorp 20:08 → Hoorn Kersenboogerd 21:12 Daily 1 h 04 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 18 November 0 min

Next service: today 20:08 from Hoofddorp · Thu 19 Nov

Next departure 20:08 today · Hoofddorp
On-time · 30 days
90%
18/20 runs under 3 min
RT coverage: 15 full · 5 partial · 9 no data
On-time · 90 days
93%
28/30 runs under 3 min
RT coverage: 22 full · 8 partial · 29 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Hoorn Kersenboogerd, 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 9 Nov Max en route +6 min · last fix heading to — +6 min
  • Wed 4 Nov Max en route +7 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 28
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 100% T n=3
  • 75% W n=4
  • 100% T n=3
  • 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 (11 stops).

Last 90 days, 30 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:08on time on time
20:12 / 20:13≈ on time ≈ on time
20:20≈ on time ≈ +1 min
20:24 / 20:33≈ on time ≈ +1 min
20:39≈ on time ≈ +1 min
20:44≈ on time ≈ +2 min
20:50≈ on time ≈ +2 min
20:53≈ on time ≈ +2 min
20:55≈ on time ≈ +2 min
21:07 / 21:08≈ on time ≈ +3 min
21:12on time +3 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— 21:140 min—
Tue 17 Nov— 21:130 min—
Mon 16 Nov— 21:140 min—
Sun 15 NovHoorn 21:22Partial coverage0 min—
Sat 14 NovHoorn 21:23Partial coverage0 min—
Fri 13 Nov— 21:130 min—
Thu 12 Nov— 21:14+3 min+3 min
Wed 11 Nov— 21:130 min—
Tue 10 Nov— 21:140 min—
Mon 9 Nov— 21:18+6 min+6 min
Sun 8 NovHoorn 21:220 min—
Sat 7 NovHoorn 21:22Partial coverage0 min—
Fri 6 Nov— 21:14+2 min+3 min
Thu 5 Nov— 21:14No data—
Wed 4 Nov— 21:22+5 min+7 min
Tue 3 Nov— 21:14No data—
Mon 2 Nov— 21:130 min—
Sun 1 NovHoorn 21:22Partial coverage0 min—
Sat 31 OctHoorn 21:22Partial coverage0 min—
Fri 30 Oct— 21:13No data—
Thu 29 Oct— 21:130 min—
Wed 28 Oct— 21:13No data—
Tue 27 Oct— 21:14No data—
Mon 26 Oct— 21:140 min—
Sun 25 OctHoorn 21:23No data—
Sat 24 OctHoorn 21:23No data—
Fri 23 Oct— 21:130 min—
Thu 22 Oct— 21:14No data—
Wed 21 Oct— 21:15No data—
Tue 20 Oct— 21:16No data—