Train NS 7017 Apeldoorn – Almelo

Apeldoorn 06:50 → Almelo 07:37 Mon, Tue, Wed, Thu, Fri, Sat 0 h 47 min · 9 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Saturday 7 November +1 min

Next service: tomorrow 06:50 from Apeldoorn · Mon 9 Nov

Full trip card
Next departure 06:50 tomorrow · Apeldoorn
On-time · 30 days
91%
21/23 runs under 3 min
RT coverage: 19 full · 4 partial · 2 no data
On-time · 90 days
93%
25/27 runs under 3 min
RT coverage: 23 full · 4 partial · 49 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: +1 min

Last 30 days

Arrival delay at Almelo, 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 24 Oct Max en route +3 min · last fix heading to Wierden +3 min
  • Sat 31 Oct Max en route +3 min · last fix heading to Wierden +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 25
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 27 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
Apeldoorn
06:50on time on time
Apeldoorn Osseveld
06:53≈ on time ≈ on time
Twello
06:59≈ on time ≈ on time
Deventer
07:04 / 07:06≈ on time ≈ on time
Deventer Colmschate
07:11≈ on time ≈ on time
Holten
07:20≈ on time ≈ on time
Rijssen
07:27≈ on time ≈ on time
Wierden
07:32≈ on time ≈ +1 min
Almelo
07:37on 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 7 NovWierden 07:47Partial coverage+1 min+1 min
Fri 6 NovEnschede Kennispark 08:18No data—
Thu 5 NovEnschede Kennispark 08:27No data—
Wed 4 NovEnschede Kennispark 08:190 min—
Tue 3 NovEnschede Kennispark 08:180 min—
Mon 2 NovEnschede Kennispark 08:180 min—
Sat 31 OctWierden 07:49Partial coverage+3 min+3 min
Fri 30 OctEnschede Kennispark 08:190 min—
Thu 29 OctEnschede Kennispark 08:190 min—
Wed 28 OctEnschede Kennispark 08:180 min—
Tue 27 OctEnschede Kennispark 08:180 min—
Mon 26 OctEnschede Kennispark 08:180 min—
Sat 24 OctWierden 07:49Partial coverage+3 min+3 min
Fri 23 OctEnschede Kennispark 08:180 min—
Thu 22 OctEnschede Kennispark 08:210 min—
Wed 21 OctEnschede Kennispark 08:180 min—
Tue 20 OctEnschede Kennispark 08:180 min—
Mon 19 OctEnschede Kennispark 08:180 min—
Sat 17 OctWierden 07:47+1 min+1 min
Fri 16 OctEnschede Kennispark 08:180 min—
Thu 15 OctEnschede Kennispark 08:190 min—
Wed 14 OctEnschede Kennispark 08:180 min—
Tue 13 OctEnschede Kennispark 08:180 min—
Mon 12 OctEnschede Kennispark 08:180 min—
Sat 10 OctWierden 07:47Partial coverage+1 min—
Fri 9 OctEnschede Kennispark 08:180 min—
Thu 8 OctEnschede Kennispark 08:19+1 min—
Wed 7 OctEnschede Kennispark 08:180 min—
Tue 6 OctEnschede Kennispark 08:19+1 min+1 min
Mon 5 OctEnschede Kennispark 08:19No data—