Train NS 1540 Deventer – Amsterdam Centraal

Deventer 11:48 → Amsterdam Centraal 12:59 Daily 1 h 11 min · 5 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November 0 min

Next service: today 11:48 from Deventer · Fri 6 Nov

Next departure 11:48 today · Deventer
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 14 full · 4 partial · 5 no data
On-time · 90 days
100%
21/21 runs under 3 min
RT coverage: 16 full · 5 partial · 45 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: +1 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 21
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=3
  • 100% W n=3
  • 100% T n=3
  • 100% F n=2
  • 100% 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, 21 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
11:48on time on time
11:58 / 12:00≈ on time ≈ on time
12:24 / 12:26≈ on time ≈ on time
12:37 / 12:39≈ on time ≈ +1 min
12:59on 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
Thu 5 NovHilversum 13:03Partial coverage0 min—
Wed 4 NovHilversum 12:59Partial coverage0 min+2 min
Tue 3 NovHilversum 13:040 min—
Mon 2 NovHilversum 12:580 min—
Sun 1 NovHilversum 13:010 min—
Sat 31 OctHilversum 13:18+2 min+4 min
Fri 30 OctHilversum 13:03Partial coverage0 min—
Thu 29 OctHilversum 13:000 min—
Wed 28 OctHilversum 13:010 min—
Tue 27 OctHilversum 13:01No data—
Mon 26 OctHilversum 12:55No data—
Mon 19 OctHilversum 13:000 min—
Sun 18 OctAmersfoort Centraal 12:350 min—
Sat 17 OctAmersfoort Centraal 12:380 min—
Fri 16 OctHilversum 13:00No data—
Thu 15 OctHilversum 13:01No data—
Wed 14 OctHilversum 13:00No data—
Tue 13 OctHilversum 13:010 min—
Mon 12 OctHilversum 13:010 min—
Sun 11 OctHilversum 13:000 min—
Sat 10 OctHilversum 13:02+2 min+2 min
Fri 9 OctHilversum 13:010 min—
Thu 8 OctHilversum 13:00Partial coverage0 min—
Wed 7 OctHilversum 13:05Partial coverage0 min—
Tue 6 OctHilversum 13:000 min—
Mon 5 OctHilversum 13:000 min—
Fri 2 OctHilversum 12:53No data—
Thu 1 OctHilversum 12:53No data—
Wed 30 SeptHilversum 12:53No data—
Tue 29 SeptHilversum 13:06No data—