Train NS 4373 Den Haag Centraal – Lelystad Centrum

Den Haag Centraal 19:10 → Lelystad Centrum 21:03 Daily 1 h 53 min · 22 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Almere Oostvaarders at 21:07 0 min

  1. Den Haag Centraal19:10
  2. De Vink19:24
  3. Nieuw Vennep19:44
  4. Amsterdam RAI20:04
  5. Weesp20:19
  6. Almere Oostvaarders20:53
  7. Lelystad Centrum21:03

Next service: tomorrow 19:10 from Den Haag Centraal · Sun 15 Nov

Next departure 19:10 tomorrow · Den Haag Centraal
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 20 full · 1 partial · 8 no data
On-time · 90 days
91%
32/35 runs under 3 min
RT coverage: 34 full · 1 partial · 26 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Lelystad Centrum, 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 19 Sept Max en route +14 min · last fix heading to Almere Oostvaarders +11 min
  • Sat 5 Sept Max en route +5 min · last fix heading to Diemen Zuid +4 min
  • Wed 11 Nov Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 3% · 1
  • On time 89% · 31
  • 3–10 min 6% · 2
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=4
  • 67% W n=3
  • 100% T n=4
  • 100% F n=7
  • 71% S n=7
  • 100% S n=7

Stops and timetable

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

Last 90 days, 35 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
19:10on time on time
19:13≈ on time ≈ on time
19:16≈ on time ≈ on time
19:21≈ on time ≈ on time
19:24≈ on time ≈ on time
19:28 / 19:32≈ on time ≈ on time
19:37≈ on time ≈ +1 min
19:44≈ on time ≈ +1 min
19:49≈ on time ≈ +1 min
19:53 / 19:55≈ on time ≈ +1 min
20:01 / 20:03≈ on time ≈ +1 min
20:04 / 20:06≈ on time ≈ +1 min
20:09≈ on time ≈ +1 min
20:12≈ on time ≈ +1 min
20:19 / 20:29≈ on time ≈ +1 min
20:35≈ on time ≈ +2 min
20:39≈ on time ≈ +2 min
20:42 / 20:43≈ on time ≈ +2 min
20:46≈ on time ≈ +2 min
20:50≈ on time ≈ +2 min
20:53≈ on time ≈ +2 min
21:03on 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
Sat 14 NovAlmere Oostvaarders 21:07Partial coverage0 min—
Fri 13 Nov— 21:09+3 min+4 min
Thu 12 Nov— 21:040 min—
Wed 11 Nov— 21:09+3 min+3 min
Tue 10 Nov— 21:04+1 min+2 min
Mon 9 Nov— 21:040 min—
Sun 8 NovAlmere Oostvaarders 21:07+1 min—
Sat 7 NovAlmere Oostvaarders 21:070 min—
Fri 6 Nov— 21:040 min—
Thu 5 Nov— 21:040 min—
Wed 4 Nov— 21:040 min—
Tue 3 Nov— 21:05No data—
Mon 2 Nov— 21:04No data—
Sun 1 NovAlmere Oostvaarders 21:070 min—
Sat 31 OctAlmere Oostvaarders 21:070 min—
Fri 30 Oct— 21:040 min—
Wed 28 Oct— 19:26No data—
Tue 27 Oct— 21:29No data—
Mon 26 OctHoofddorp 21:04No data—
Sun 25 OctAlmere Oostvaarders 21:07No data—
Sat 24 OctAlmere Oostvaarders 21:090 min—
Fri 23 OctDe Vink 21:040 min—
Thu 22 Oct— 21:090 min—
Wed 21 Oct— 21:07No data—
Tue 20 Oct— 21:050 min—
Mon 19 Oct— 21:210 min—
Sun 18 OctAlmere Oostvaarders 21:050 min—
Sat 17 OctAlmere Oostvaarders 21:10No data—
Fri 16 OctSchiphol Airport 21:050 min—
Thu 15 Oct— 21:29No data—