Train NS 1555 Amsterdam Centraal – Deventer

Amsterdam Centraal 15:31 → Deventer 16:44 Daily 1 h 13 min · 5 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Apeldoorn at 16:49 0 min

  1. Amsterdam Centraal15:31
  2. Hilversum15:50
  3. Amersfoort Centraal16:03
  4. Apeldoorn16:32
  5. Deventer16:44

Next service: tomorrow 15:31 from Amsterdam Centraal · Fri 6 Nov

Next departure 15:31 tomorrow · Amsterdam Centraal
On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 12 full · 6 partial · 6 no data
On-time · 90 days
95%
19/20 runs under 3 min
RT coverage: 13 full · 7 partial · 46 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: +1 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 10 Oct Max en route +20 min · last fix heading to Hilversum +20 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 19
  • 3–10 min 0% · 0
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 20 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:31on time on time
15:50 / 15:52≈ on time ≈ on time
16:03 / 16:06≈ on time ≈ on time
16:32 / 16:34≈ on time ≈ +1 min
16:44on 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
Thu 5 NovApeldoorn 16:49Partial coverage0 min—
Wed 4 NovApeldoorn 16:48Partial coverage+1 min—
Tue 3 NovApeldoorn 16:48Partial coverage0 min—
Mon 2 NovApeldoorn 16:48No data—
Sun 1 NovHilversum 16:070 min—
Sat 31 OctHilversum 16:060 min—
Fri 30 OctApeldoorn 16:480 min—
Thu 29 OctDieren 17:250 min—
Wed 28 OctDieren 17:230 min—
Tue 27 OctDieren 17:25No data—
Mon 26 OctDieren 17:31No data—
Mon 19 OctApeldoorn 16:48Partial coverage0 min—
Sun 18 OctHilversum 16:050 min—
Sat 17 OctHilversum 16:050 min—
Fri 16 OctHilversum 16:090 min—
Thu 15 OctHilversum 16:10No data—
Wed 14 OctHilversum 16:22No data—
Tue 13 OctHilversum 16:10No data—
Mon 12 OctHilversum 16:090 min—
Sun 11 OctHilversum 16:21+1 min+1 min
Sat 10 OctHilversum 16:29+20 min+20 min
Fri 9 OctApeldoorn 16:480 min—
Thu 8 OctApeldoorn 16:48Partial coverage0 min—
Wed 7 OctApeldoorn 16:48Partial coverage0 min—
Tue 6 OctApeldoorn 16:48Partial coverage0 min+4 min
Mon 5 OctApeldoorn 16:480 min—
Fri 2 OctApeldoorn 16:48No data—
Thu 1 OctApeldoorn 16:48No data—
Wed 30 SeptApeldoorn 16:48No data—
Tue 29 SeptApeldoorn 16:48No data—