Train NS 1542 Deventer – Amsterdam Centraal

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

Running now · updated 13:16

Heading to Amsterdam Centraal 0 min

Estimated arrival at Amsterdam Centraal 13:29 · 123 km/h

  1. Deventer12:18
  2. Apeldoorn12:28
  3. Amersfoort Centraal12:54
  4. Hilversum13:07
  5. Amsterdam Centraal13:29

Today it is running no worse than usual: typical arrival delay is 0 min; 79% of the last 19 runs arrived on time.

On-time · 30 days
79%
15/19 runs under 3 min
RT coverage: 8 full · 11 partial · 7 no data
On-time · 90 days
87%
26/30 runs under 3 min
RT coverage: 19 full · 11 partial · 45 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +6 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

  • Wed 18 Nov Max en route +13 min · last fix heading to Hilversum +12 min
  • Mon 16 Nov Max en route +12 min · last fix heading to Hilversum +12 min
  • Tue 17 Nov Max en route +5 min · last fix heading to Deventer +5 min
  • Thu 19 Nov Max en route +4 min · last fix heading to Hilversum +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 87% · 26
  • 3–10 min 7% · 2
  • 10–30 min 7% · 2
  • 30+ min 0% · 0

On-time by weekday

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