Train NS 1554 Deventer – Amsterdam Centraal

Deventer 15:19 → Amsterdam Centraal 16:29 Daily 1 h 10 min · 5 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 15:19 from Deventer · Fri 6 Nov

Next departure 15:19 today · Deventer
On-time · 30 days
93%
13/14 runs under 3 min
RT coverage: 9 full · 5 partial · 9 no data
On-time · 90 days
94%
16/17 runs under 3 min
RT coverage: 10 full · 7 partial · 49 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: +2 min

Last 30 days

Arrival delay at Amsterdam Centraal, 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 10 Oct Max en route +29 min · last fix heading to Hilversum +29 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 16
  • 3–10 min 0% · 0
  • 10–30 min 6% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=1
  • 100% W n=3
  • 100% T n=2
  • 100% F n=3
  • 50% S n=2
  • 100% S n=3

Stops and timetable

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

Last 90 days, 17 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
15:19on time on time
15:29 / 15:30≈ on time ≈ +1 min
15:54 / 15:56≈ on time ≈ +2 min
16:07 / 16:09≈ on time ≈ +3 min
16:29on time +5 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
Thu 5 NovHilversum 16:30No data—
Wed 4 NovHilversum 16:29Partial coverage0 min+1 min
Tue 3 NovHilversum 16:29No data—
Mon 2 NovHilversum 16:29No data—
Sun 1 NovHilversum 16:310 min—
Sat 31 OctHilversum 16:300 min—
Fri 30 OctHilversum 16:30Partial coverage0 min—
Thu 29 OctHilversum 16:310 min—
Wed 28 OctHilversum 16:300 min—
Tue 27 OctHilversum 16:31No data—
Mon 26 OctHilversum 16:31No data—
Mon 19 OctHilversum 16:24Partial coverage0 min—
Sun 18 OctAmersfoort Centraal 16:050 min—
Sat 17 OctAmersfoort Centraal 16:06No data—
Fri 16 OctHilversum 16:300 min—
Thu 15 OctAmersfoort Centraal 16:30No data—
Wed 14 OctHilversum 16:31No data—
Tue 13 OctHilversum 16:31No data—
Mon 12 OctHilversum 16:31+1 min+2 min
Sun 11 OctHilversum 16:35+2 min+3 min
Sat 10 OctHilversum 16:57+29 min+29 min
Fri 9 OctHilversum 16:30Partial coverage0 min—
Thu 8 OctHilversum 16:31Partial coverage0 min—
Wed 7 OctHilversum 16:31Partial coverage0 min—
Tue 6 OctHilversum 16:31Partial coverage+1 min—
Mon 5 OctHilversum 16:32+1 min+3 min
Fri 2 OctHilversum 16:23No data—
Thu 1 OctHilversum 16:24No data—
Wed 30 SeptHilversum 16:28No data—
Tue 29 SeptHilversum 16:23No data—