Train NS 4388 Lelystad Centrum – Hoofddorp

Lelystad Centrum 00:25 → Hoofddorp 01:39 Fri, Sat 1 h 14 min · 14 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 01:39 0 min

Lelystad Centrum00:25
Almere Buiten00:39
Almere Centrum00:45
Weesp01:02
Duivendrecht01:17
Amsterdam Zuid01:25
Hoofddorp01:39

Next service: Friday 00:25 from Lelystad Centrum · Fri 13 Nov

Full trip card

Next departure 00:25 Friday · Lelystad Centrum

On-time · 30 days

100%

8/8 runs under 3 min

RT coverage: 8 full · 0 partial · 1 no data

On-time · 90 days

100%

8/8 runs under 3 min

RT coverage: 8 full · 0 partial · 2 no data

Typical delay

0min

Median at arrival, 90 days

30 days: 0 min

P90

0min

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

Distribution · 90 days

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

Early 0% · 0
On time 100% · 8
3–10 min 0% · 0
10–30 min 0% · 0
30+ min 0% · 0

On-time by weekday

— M n=0
— T n=0
— W n=0
— T n=0
— F n=0
100% S n=5
100% S n=3

Stops and timetable

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

Last 90 days, 8 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.

Stop	Sched.	Usually	9 days in 10
Lelystad Centrum	00:25	on time	on time
Almere Oostvaarders	00:36	≈ on time	≈ on time
Almere Buiten	00:39	≈ on time	≈ on time
Almere Parkwijk	00:43	≈ on time	≈ on time
Almere Centrum	00:45 / 00:48	≈ on time	≈ on time
Almere Muziekwijk	00:51	≈ on time	≈ on time
Almere Poort	00:55	≈ on time	≈ on time
Weesp	01:02 / 01:08	≈ on time	≈ on time
Diemen Zuid	01:15	≈ on time	≈ on time
Duivendrecht	01:17	≈ on time	≈ on time
Amsterdam RAI	01:21	≈ on time	≈ on time
Amsterdam Zuid	01:25 / 01:28	≈ on time	≈ on time
Schiphol Airport	01:34 / 01:35	≈ on time	≈ on time
Hoofddorp	01:39	on time	on time

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

Date	Last stop	Final	Max
Sat 7 Nov	— 01:39	0 min	—
Sun 1 Nov	— 01:40	No data	—
Sat 31 Oct	— 01:43	0 min	—
Sun 25 Oct	— 01:40	0 min	—
Sat 24 Oct	— 01:41	0 min	—
Sun 18 Oct	Amsterdam Zuid 01:42	0 min	—
Sat 17 Oct	— 01:40	0 min	—
Sun 11 Oct	— 01:41	0 min	—
Sat 10 Oct	— 01:40	0 min	—
Sun 4 Oct	Almere Oostvaarders 00:50	No data	—