Train NS 1546 Deventer – Amsterdam Centraal

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

It has not run yet today

Last recorded run: Wednesday 4 November +1 min

Next service: today 13:19 from Deventer · Thu 5 Nov

Next departure 13:19 today · Deventer
On-time · 30 days
94%
15/16 runs under 3 min
RT coverage: 10 full · 6 partial · 7 no data
On-time · 90 days
94%
17/18 runs under 3 min
RT coverage: 11 full · 7 partial · 47 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: +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 +8 min · last fix heading to Hilversum +8 min

Distribution · 90 days

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

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

On-time by weekday

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