Train NS 4149 Hoorn Kersenboogerd – Hoofddorp

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

✓ Today’s run finished

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

  1. Hoorn Kersenboogerd12:54
  2. Purmerend Overwhere13:09
  3. Purmerend13:12
  4. Zaandam Kogerveld13:21
  5. Amsterdam Sloterdijk13:31
  6. Schiphol Airport13:46
  7. Hoofddorp13:52

Next service: tomorrow 12:54 from Hoorn Kersenboogerd · Wed 18 Nov

Next departure 12:54 tomorrow · Hoorn Kersenboogerd
On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 8 full · 10 partial · 12 no data
On-time · 90 days
96%
25/26 runs under 3 min
RT coverage: 13 full · 13 partial · 63 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 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

  • Sat 14 Nov Max en route +22 min · last fix heading to Amsterdam Lelylaan +21 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 25
  • 3–10 min 0% · 0
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 26 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
12:54on time on time
12:57 / 12:58≈ on time ≈ on time
13:09≈ on time ≈ +1 min
13:12≈ on time ≈ +1 min
13:15≈ on time ≈ +1 min
13:21≈ on time ≈ +1 min
13:25≈ on time ≈ +1 min
13:31 / 13:36≈ on time ≈ +2 min
13:40≈ on time ≈ +2 min
13:46 / 13:47≈ on time ≈ +2 min
13:52on time +2 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
Tue 17 NovSchiphol Airport 13:59Partial coverage0 min—
Mon 16 NovSchiphol Airport 13:59Partial coverage0 min—
Sun 15 NovSchiphol Airport 14:000 min—
Sat 14 NovAmsterdam Lelylaan 14:32+21 min+22 min
Fri 13 NovSchiphol Airport 13:590 min—
Thu 12 NovSchiphol Airport 13:59Partial coverage0 min—
Wed 11 NovSchiphol Airport 13:59Partial coverage0 min—
Tue 10 NovSchiphol Airport 13:59Partial coverage0 min—
Mon 9 NovSchiphol Airport 13:59Partial coverage0 min—
Sun 8 NovSchiphol Airport 13:590 min—
Sat 7 NovZaandam 13:340 min—
Fri 6 NovSchiphol Airport 13:59No data—
Thu 5 NovSchiphol Airport 14:04No data—
Wed 4 NovSchiphol Airport 13:59Partial coverage0 min—
Tue 3 NovSchiphol Airport 14:13No data—
Mon 2 NovSchiphol Airport 14:03Partial coverage0 min—
Sun 1 NovSchiphol Airport 14:06+3 min+4 min
Sat 31 OctSchiphol Airport 14:010 min—
Fri 30 OctSchiphol Airport 14:01No data—
Thu 29 OctSchiphol Airport 14:05No data—
Wed 28 OctSchiphol Airport 14:01No data—
Tue 27 OctSchiphol Airport 14:01Partial coverage0 min—
Mon 26 OctSchiphol Airport 14:01No data—
Sun 25 OctSchiphol Airport 14:01No data—
Sat 24 OctSchiphol Airport 14:010 min—
Fri 23 OctSchiphol Airport 14:02No data—
Thu 22 OctSchiphol Airport 14:01No data—
Wed 21 OctSchiphol Airport 14:03No data—
Tue 20 OctSchiphol Airport 14:01No data—
Mon 19 OctSchiphol Airport 14:01Partial coverage0 min—