Train NS 7018 Deventer – Apeldoorn

Deventer 06:25 → Apeldoorn 06:40 Mon, Tue, Wed, Thu, Fri, Sat 0 h 15 min · 4 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Saturday 14 November 0 min

Next service: tomorrow 06:25 from Deventer · Mon 16 Nov

Next departure 06:25 tomorrow · Deventer
On-time · 30 days
91%
20/22 runs under 3 min
RT coverage: 18 full · 4 partial · 2 no data
On-time · 90 days
94%
30/32 runs under 3 min
RT coverage: 27 full · 5 partial · 43 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Apeldoorn, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Fri 13 Nov Max en route +4 min · last fix heading to Apeldoorn Osseveld +4 min
  • Sat 7 Nov Max en route +4 min · last fix heading to Apeldoorn Osseveld +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 30
  • 3–10 min 6% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=6
  • 100% W n=6
  • 100% T n=6
  • 80% F n=5
  • 80% S n=5
  • — S n=0

Stops and timetable

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

Last 90 days, 32 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
06:25on time on time
06:30≈ on time ≈ on time
06:35≈ on time ≈ on time
06:40on 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
Sat 14 NovApeldoorn Osseveld 06:49Partial coverage0 min—
Fri 13 NovApeldoorn Osseveld 06:54+4 min+4 min
Thu 12 NovApeldoorn Osseveld 06:490 min+2 min
Wed 11 NovApeldoorn Osseveld 06:490 min—
Tue 10 NovApeldoorn Osseveld 06:49+1 min—
Mon 9 NovApeldoorn Osseveld 06:49+1 min—
Sat 7 NovApeldoorn Osseveld 06:49Partial coverage+4 min+4 min
Fri 6 NovApeldoorn Osseveld 06:53No data—
Thu 5 NovApeldoorn Osseveld 06:520 min—
Wed 4 NovApeldoorn Osseveld 06:49+1 min—
Tue 3 NovApeldoorn Osseveld 06:490 min—
Mon 2 NovApeldoorn Osseveld 06:49No data—
Sat 31 OctApeldoorn Osseveld 06:51Partial coverage+2 min+3 min
Fri 30 OctApeldoorn Osseveld 06:500 min—
Thu 29 OctApeldoorn Osseveld 06:500 min—
Wed 28 OctApeldoorn Osseveld 06:500 min—
Tue 27 OctApeldoorn Osseveld 06:500 min+1 min
Mon 26 OctApeldoorn Osseveld 06:500 min—
Sat 24 OctApeldoorn Osseveld 06:50Partial coverage0 min—
Fri 23 OctApeldoorn Osseveld 06:510 min+2 min
Thu 22 OctApeldoorn Osseveld 06:510 min+2 min
Wed 21 OctApeldoorn Osseveld 06:500 min—
Tue 20 OctApeldoorn Osseveld 06:500 min—
Mon 19 OctApeldoorn Osseveld 06:500 min—
Fri 16 OctDeventer Colmschate 06:330 min—
Thu 15 OctDeventer Colmschate 06:34+1 min+1 min
Wed 14 OctDeventer Colmschate 06:330 min—
Tue 13 OctDeventer Colmschate 06:330 min—
Mon 12 OctDeventer Colmschate 06:330 min—
Sat 10 OctApeldoorn Osseveld 06:50Partial coverage0 min—