Train NS 1550 Deventer – Amsterdam Centraal

Deventer 14:18 → Amsterdam Centraal 15:29 Daily 1 h 11 min · 5 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 14:18 from Deventer · Thu 5 Nov

Next departure 14:18 today · Deventer
On-time · 30 days
92%
11/12 runs under 3 min
RT coverage: 8 full · 4 partial · 11 no data
On-time · 90 days
93%
13/14 runs under 3 min
RT coverage: 9 full · 5 partial · 51 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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 +4 min · last fix heading to Hilversum +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 13
  • 3–10 min 7% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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