Train NS 4145 Hoorn Kersenboogerd – Hoofddorp

Hoorn Kersenboogerd 11:54 → Hoofddorp 12:52 Daily 0 h 58 min · 11 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Schiphol Airport at 12:59 0 min

  1. Hoorn Kersenboogerd11:54
  2. Purmerend Overwhere12:09
  3. Purmerend12:12
  4. Zaandam Kogerveld12:21
  5. Amsterdam Sloterdijk12:31
  6. Schiphol Airport12:46
  7. Hoofddorp12:52

Next service: tomorrow 11:54 from Hoorn Kersenboogerd · Fri 20 Nov

Next departure 11:54 tomorrow · Hoorn Kersenboogerd
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 9 full · 10 partial · 11 no data
On-time · 90 days
97%
28/29 runs under 3 min
RT coverage: 16 full · 13 partial · 60 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

  • Sun 18 Oct Max en route +3 min · last fix heading to Schiphol Airport +3 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=4
  • 100% T n=5
  • 100% W n=5
  • 100% T n=3
  • 100% F n=2
  • 100% S n=5
  • 80% S n=5

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
11:54on time on time
11:57 / 11:58≈ on time ≈ on time
12:09≈ on time ≈ on time
12:12≈ on time ≈ on time
12:15≈ on time ≈ on time
12:21≈ on time ≈ on time
12:25≈ on time ≈ on time
12:31 / 12:36≈ on time ≈ +1 min
12:40≈ on time ≈ +1 min
12:46 / 12:47≈ on time ≈ +1 min
12:52on 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
Thu 19 NovSchiphol Airport 12:59Partial coverage0 min—
Wed 18 NovSchiphol Airport 12:59Partial coverage0 min—
Tue 17 NovSchiphol Airport 13:02Partial coverage+1 min+1 min
Mon 16 NovSchiphol Airport 13:00Partial coverage0 min—
Sun 15 NovSchiphol Airport 12:590 min—
Sat 14 NovSchiphol Airport 12:590 min—
Fri 13 NovSchiphol Airport 12:590 min—
Thu 12 NovSchiphol Airport 12:59Partial coverage0 min—
Wed 11 NovSchiphol Airport 12:59Partial coverage0 min—
Tue 10 NovSchiphol Airport 13:02Partial coverage+1 min—
Mon 9 NovSchiphol Airport 12:59Partial coverage0 min—
Sun 8 NovSchiphol Airport 12:590 min—
Sat 7 NovSchiphol Airport 12:590 min—
Fri 6 NovSchiphol Airport 12:59No data—
Thu 5 NovSchiphol Airport 12:59No data—
Wed 4 NovSchiphol Airport 12:59Partial coverage0 min—
Tue 3 NovSchiphol Airport 12:59No data—
Mon 2 NovSchiphol Airport 13:02No data—
Sun 1 NovSchiphol Airport 13:020 min—
Sat 31 OctSchiphol Airport 13:010 min—
Fri 30 OctSchiphol Airport 13:01No data—
Thu 29 OctSchiphol Airport 13:01No data—
Wed 28 OctSchiphol Airport 13:01Partial coverage0 min—
Tue 27 OctSchiphol Airport 13:010 min—
Mon 26 OctSchiphol Airport 13:01No data—
Sun 25 OctSchiphol Airport 13:02No data—
Sat 24 OctSchiphol Airport 13:010 min—
Fri 23 OctSchiphol Airport 13:01No data—
Thu 22 OctSchiphol Airport 13:01No data—
Wed 21 OctSchiphol Airport 13:02No data—