Train NS 1538 Deventer – Amsterdam Centraal

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

✓ Today’s run finished

Today, last fix heading to Hilversum at 12:34 +5 min

  1. Deventer11:19
  2. Apeldoorn11:29
  3. Amersfoort Centraal11:54
  4. Hilversum12:07
  5. Amsterdam Centraal12:29

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

Next departure 11:19 tomorrow · Deventer
On-time · 30 days
90%
19/21 runs under 3 min
RT coverage: 11 full · 10 partial · 3 no data
On-time · 90 days
90%
27/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: +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

  • Tue 17 Nov Max en route +5 min · last fix heading to Hilversum +5 min
  • Sat 10 Oct Max en route +4 min · last fix heading to Hilversum +4 min
  • Mon 16 Nov Max en route +6 min · last fix heading to Hilversum +4 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 90% · 27
  • 3–10 min 10% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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