Train NS 4386 Lelystad Centrum – Weesp

Lelystad Centrum 23:55 → Weesp 00:30 Daily 0 h 35 min · 8 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 23:55 from Lelystad Centrum · Thu 5 Nov

Full trip card
Next departure 23:55 today · Lelystad Centrum
On-time · 30 days
96%
23/24 runs under 3 min
RT coverage: 20 full · 4 partial · 4 no data
On-time · 90 days
96%
25/26 runs under 3 min
RT coverage: 22 full · 4 partial · 11 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 Weesp, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Wed 7 Oct Max en route +3 min · last fix heading to — +3 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 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (8 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
Lelystad Centrum
23:55on time on time
Almere Oostvaarders
00:06≈ on time ≈ on time
Almere Buiten
00:09≈ on time ≈ on time
Almere Parkwijk
00:13≈ on time ≈ on time
Almere Centrum
00:15 / 00:16≈ on time ≈ on time
Almere Muziekwijk
00:19≈ on time ≈ on time
Almere Poort
00:23≈ on time ≈ on time
Weesp
00:30on 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
Wed 4 Nov— 00:290 min—
Tue 3 Nov— 00:340 min—
Mon 2 Nov— 00:290 min—
Sun 1 NovAlmere Poort 00:37Partial coverage0 min—
Sat 31 Oct— 01:100 min—
Fri 30 Oct— 00:030 min—
Wed 28 Oct— 00:350 min—
Tue 27 Oct— 00:310 min—
Mon 26 Oct— 00:310 min—
Sun 25 OctAlmere Poort 00:37Partial coverage0 min—
Sat 24 Oct— 01:11No data—
Fri 23 Oct— 01:110 min+3 min
Thu 22 Oct— 00:310 min—
Wed 21 Oct— 00:31No data—
Tue 20 Oct— 00:31No data—
Mon 19 Oct— 00:310 min—
Sun 18 OctAlmere Poort 00:42Partial coverage0 min—
Sat 17 OctLelystad Centrum 01:27No data—
Fri 16 Oct— 01:100 min—
Thu 15 Oct— 00:310 min—
Wed 14 Oct— 00:410 min—
Tue 13 Oct— 00:310 min—
Mon 12 Oct— 00:310 min—
Sun 11 OctAlmere Poort 00:37Partial coverage0 min—
Sat 10 Oct— 01:110 min—
Fri 9 Oct— 01:11+1 min—
Thu 8 Oct— 00:340 min—
Wed 7 Oct— 00:36+3 min+3 min
Tue 6 Oct— 00:340 min—
Mon 5 Oct— 00:32+1 min—