Train NS 1591 Amsterdam Centraal – Deventer

Amsterdam Centraal 00:30 → Deventer 01:44 Fri, Sat 1 h 14 min · 5 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Sunday 15 November 0 min

Next service: tomorrow 00:30 from Amsterdam Centraal · Fri 20 Nov

Next departure 00:30 tomorrow · Amsterdam Centraal
On-time · 30 days
100%
5/5 runs under 3 min
RT coverage: 5 full · 0 partial · 1 no data
On-time · 90 days
88%
7/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
+3min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Deventer, 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 17 Oct Max en route +10 min · last fix heading to — +10 min

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 88% · 7
  • 3–10 min 13% · 1
  • 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
  • 80% S n=5
  • 100% S n=3

Stops and timetable

Timetable of the latest run from the operator’s GTFS (5 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.

StopSched.Usually 9 days in 10
00:30on time +1 min
00:50 / 00:52≈ on time ≈ +2 min
01:03 / 01:06≈ on time ≈ +2 min
01:32 / 01:34≈ on time ≈ +3 min
01:44on time +3 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
Sun 15 Nov— 01:440 min—
Sat 14 Nov— 01:480 min+2 min
Sun 8 Nov— 01:440 min—
Sat 7 Nov— 01:440 min—
Sun 1 Nov— 01:46No data—
Sat 31 Oct— 01:450 min—
Sun 18 OctHilversum 01:09No data—
Sat 17 Oct— 01:27+10 min+10 min
Sun 11 Oct— 01:460 min—
Sat 10 Oct— 01:450 min—