Train NS 1540 Deventer → Amsterdam Centraal

Deventer 11:48 → Amsterdam Centraal 12:59 Mon, Tue, Wed, Thu, Fri 1 h 11 min · 5 stops NS (Nederlandse Spoorwegen)

NS 1540 Deventer–Amsterdam Centraal: final delay under 3 min on 21 of its 23 runs with data in the last 30 days (91%). Median final delay: 0 min. TrainsRadar data as of 23 Nov 2026, 00:04 (GMT+1).

It has not run yet today

Last recorded run: Friday 20 November 0 min

Next service: today 11:48 from Deventer · Mon 23 Nov

Next departure 11:48 today · Deventer
On-time · 30 days
91%
21/23 runs under 3 min
RT coverage: 15 full · 8 partial · 3 no data
On-time · 90 days
94%
33/35 runs under 3 min
RT coverage: 25 full · 10 partial · 37 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Mon 16 Nov Max en route +12 min · last fix heading to Hilversum +12 min
  • Sat 14 Nov Max en route +5 min · last fix heading to Hilversum +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 33
  • 3–10 min 3% · 1
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 100% T n=5
  • 100% W n=5
  • 100% T n=5
  • 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, 35 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 ≈ +1 min
12:37 / 12:39≈ on time ≈ +2 min
12:59on time +2 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 12:59Partial coverage0 min—
Thu 19 NovHilversum 12:59Partial coverage0 min—
Wed 18 NovHilversum 12:59Partial coverage0 min—
Tue 17 NovHilversum 12:590 min—
Mon 16 NovHilversum 13:14+12 min+12 min
Sun 15 NovHilversum 12:59+1 min+1 min
Sat 14 NovHilversum 13:04+5 min+5 min
Fri 13 NovHilversum 13:04+2 min+3 min
Thu 12 NovHilversum 13:03Partial coverage+1 min+1 min
Wed 11 NovHilversum 13:03Partial coverage+2 min+3 min
Tue 10 NovAmersfoort Centraal 12:390 min—
Mon 9 NovHilversum 12:530 min—
Sun 8 NovHilversum 12:530 min—
Sat 7 NovHilversum 12:590 min—
Fri 6 NovHilversum 12:59No data—
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—