Train NS 1522 Deventer – Amsterdam Centraal

Deventer 07:19 → Amsterdam Centraal 08:29 Mon, Tue, Wed, Thu, Fri, Sat 1 h 10 min · 5 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

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

  1. Deventer07:19
  2. Apeldoorn07:29
  3. Amersfoort Centraal07:54
  4. Hilversum08:07
  5. Amsterdam Centraal08:29

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

Next departure 07:19 tomorrow · Deventer
On-time · 30 days
89%
16/18 runs under 3 min
RT coverage: 7 full · 11 partial · 3 no data
On-time · 90 days
88%
22/25 runs under 3 min
RT coverage: 10 full · 15 partial · 43 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: +3 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

  • Tue 10 Nov Max en route +15 min · last fix heading to Amersfoort Centraal +15 min
  • Fri 9 Oct Max en route +8 min · last fix heading to Hilversum +8 min
  • Tue 17 Nov Max en route +4 min · last fix heading to Hilversum +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 22
  • 3–10 min 8% · 2
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 50% T n=4
  • 100% W n=4
  • 100% T n=3
  • 67% F n=3
  • 100% S n=5
  • — S n=0

Stops and timetable

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

Last 90 days, 25 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
07:19on time on time
07:29 / 07:30≈ on time ≈ on time
07:54 / 07:56≈ on time ≈ on time
08:07 / 08:09≈ on time ≈ +1 min
08: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 08:34Partial coverage+4 min+4 min
Mon 16 NovHilversum 08:34Partial coverage+2 min+3 min
Sat 14 NovHilversum 08:290 min—
Fri 13 NovHilversum 08:33Partial coverage+1 min+2 min
Thu 12 NovHilversum 08:29Partial coverage0 min—
Wed 11 NovHilversum 08:29Partial coverage0 min—
Tue 10 NovAmersfoort Centraal 08:29Partial coverage+15 min+15 min
Mon 9 NovHilversum 08:29Partial coverage0 min+2 min
Sat 7 NovHilversum 08:290 min+2 min
Fri 6 NovHilversum 08:29No data—
Thu 5 NovHilversum 08:29No data—
Wed 4 NovHilversum 08:34Partial coverage+2 min+5 min
Tue 3 NovHilversum 08:34No data—
Mon 2 NovAmersfoort Centraal 08:33Partial coverage0 min—
Sat 31 OctHilversum 08:230 min—
Fri 30 OctHilversum 08:25Partial coverage+3 min+3 min
Thu 29 OctHilversum 08:510 min—
Wed 28 OctHilversum 08:310 min—
Tue 27 OctHilversum 08:310 min—
Mon 26 OctHilversum 08:31+1 min—
Mon 19 OctHilversum 08:35Partial coverage0 min—
Sat 17 OctAmersfoort Centraal 08:06+1 min+1 min
Fri 16 OctHilversum 08:31No data—
Thu 15 OctHilversum 08:30No data—
Wed 14 OctHilversum 08:23No data—
Tue 13 OctHilversum 08:30No data—
Mon 12 OctHilversum 08:310 min—
Sat 10 OctHilversum 08:33+1 min+2 min
Fri 9 OctHilversum 08:43Partial coverage+8 min+8 min
Thu 8 OctHilversum 08:31Partial coverage+2 min+2 min