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: Monday 16 November +12 min

Next service: today 15:19 from Deventer · Tue 17 Nov

Next departure 15:19 today · Deventer
On-time · 30 days
82%
14/17 runs under 3 min
RT coverage: 8 full · 9 partial · 6 no data
On-time · 90 days
85%
23/27 runs under 3 min
RT coverage: 14 full · 13 partial · 47 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+8min
9 in 10 runs arrive with less than this
30 days: +8 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
  • Mon 16 Nov Max en route +12 min · last fix heading to Amersfoort Centraal +12 min
  • Mon 9 Nov Max en route +11 min · last fix heading to Hilversum +10 min
  • Thu 12 Nov Max en route +7 min · last fix heading to Hilversum +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 85% · 23
  • 3–10 min 7% · 2
  • 10–30 min 7% · 2
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 27 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 ≈ on time
15:54 / 15:56≈ on time ≈ +1 min
16:07 / 16:09≈ on time ≈ +2 min
16:29on 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
Mon 16 NovAmersfoort Centraal 16:39Partial coverage+12 min+12 min
Sun 15 NovHilversum 16:29+1 min+1 min
Sat 14 NovHilversum 16:34+3 min+3 min
Fri 13 NovHilversum 16:32Partial coverage+1 min+1 min
Thu 12 NovHilversum 16:34Partial coverage+7 min+7 min
Wed 11 NovHilversum 16:29Partial coverage0 min—
Tue 10 NovAmersfoort Centraal 16:09Partial coverage0 min—
Mon 9 NovHilversum 16:49Partial coverage+10 min+11 min
Sun 8 NovHilversum 16:300 min—
Sat 7 NovHilversum 16:29+1 min—
Fri 6 NovHilversum 16:34No data—
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