Train NS 1548 Deventer – Amsterdam Centraal

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

It has not run yet today

Last recorded run: Monday 16 November +1 min

Next service: today 13:48 from Deventer · Tue 17 Nov

Next departure 13:48 today · Deventer
On-time · 30 days
94%
15/16 runs under 3 min
RT coverage: 10 full · 6 partial · 7 no data
On-time · 90 days
92%
24/26 runs under 3 min
RT coverage: 17 full · 9 partial · 48 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

  • Sat 10 Oct Max en route +11 min · last fix heading to Hilversum +11 min
  • Thu 12 Nov Max en route +6 min · last fix heading to Hilversum +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 24
  • 3–10 min 4% · 1
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

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