Train NS 1534 Deventer – Amsterdam Centraal

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

✓ Today’s run finished

Today, last fix heading to Hilversum at 11:33 +2 min

  1. Deventer10:18
  2. Apeldoorn10:28
  3. Amersfoort Centraal10:54
  4. Hilversum11:07
  5. Amsterdam Centraal11:29

Next service: tomorrow 10:18 from Deventer · Wed 18 Nov

Next departure 10:18 tomorrow · Deventer
On-time · 30 days
79%
15/19 runs under 3 min
RT coverage: 11 full · 8 partial · 5 no data
On-time · 90 days
80%
24/30 runs under 3 min
RT coverage: 18 full · 12 partial · 45 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+6min
9 in 10 runs arrive with less than this
30 days: +5 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 11 Nov Max en route +18 min · last fix heading to Hilversum +17 min
  • Thu 8 Oct Max en route +12 min · last fix heading to Hilversum +11 min
  • Wed 4 Nov Max en route +7 min · last fix heading to Hilversum +7 min
  • Sun 11 Oct Max en route +5 min · last fix heading to Hilversum +5 min
  • Thu 12 Nov Max en route +5 min · last fix heading to Hilversum +5 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 80% · 24
  • 3–10 min 13% · 4
  • 10–30 min 7% · 2
  • 30+ min 0% · 0

On-time by weekday

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