Train NS 1530 Deventer – Amsterdam Centraal

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

✓ Today’s run finished

Today, last fix heading to Hilversum at 10:34 +4 min

  1. Deventer09:19
  2. Apeldoorn09:29
  3. Amersfoort Centraal09:54
  4. Hilversum10:07
  5. Amsterdam Centraal10:29

Next service: tomorrow 09:19 from Deventer · Wed 18 Nov

Next departure 09:19 tomorrow · Deventer
On-time · 30 days
85%
17/20 runs under 3 min
RT coverage: 10 full · 10 partial · 4 no data
On-time · 90 days
87%
26/30 runs under 3 min
RT coverage: 16 full · 14 partial · 45 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: +4 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

  • Thu 12 Nov Max en route +15 min · last fix heading to Hilversum +15 min
  • Mon 16 Nov Max en route +4 min · last fix heading to Hilversum +4 min
  • Tue 17 Nov Max en route +5 min · last fix heading to Hilversum +4 min
  • Sat 17 Oct Max en route +3 min · last fix heading to Amersfoort Centraal +3 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 10% · 3
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 75% T n=4
  • 100% W n=4
  • 67% T n=3
  • 100% F n=4
  • 80% S n=5
  • 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 10
09:19on time on time
09:29 / 09:30≈ on time ≈ on time
09:54 / 09:56≈ on time ≈ +1 min
10:07 / 10:09≈ on time ≈ +1 min
10: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
Tue 17 NovHilversum 10:34Partial coverage+4 min+5 min
Mon 16 NovHilversum 10:27Partial coverage+4 min+4 min
Sun 15 NovHilversum 10:33+2 min+2 min
Sat 14 NovHilversum 10:290 min—
Fri 13 NovHilversum 10:34Partial coverage+2 min+4 min
Thu 12 NovHilversum 10:49Partial coverage+15 min+15 min
Wed 11 NovHilversum 10:29Partial coverage0 min—
Tue 10 NovAmersfoort Centraal 10:09Partial coverage0 min—
Mon 9 NovHilversum 10:29Partial coverage0 min—
Sun 8 NovHilversum 10:29+1 min—
Sat 7 NovHilversum 10:290 min—
Fri 6 NovHilversum 10:23No data—
Thu 5 NovHilversum 10:34No data—
Wed 4 NovHilversum 10:34Partial coverage+3 min+4 min
Tue 3 NovHilversum 10:23No data—
Mon 2 NovHilversum 10:48No data—
Sun 1 NovHilversum 10:300 min—
Sat 31 OctHilversum 10:230 min—
Fri 30 OctHilversum 10:53Partial coverage0 min—
Thu 29 OctHilversum 10:330 min—
Wed 28 OctHilversum 10:360 min—
Tue 27 OctHilversum 10:320 min—
Mon 26 OctHilversum 10:300 min—
Mon 19 OctHilversum 10:23Partial coverage0 min—
Sun 18 OctAmersfoort Centraal 10:060 min—
Sat 17 OctAmersfoort Centraal 10:08+3 min+3 min
Fri 16 OctHilversum 10:300 min—
Thu 15 OctHilversum 10:30No data—
Wed 14 OctHilversum 10:30No data—
Tue 13 OctHilversum 10:30No data—