Train NS 7062 Enschede – Apeldoorn

Enschede 16:21 → Apeldoorn 17:40 Daily 1 h 19 min · 14 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 18 November 0 min

Next service: today 16:21 from Enschede · Thu 19 Nov

Next departure 16:21 today · Enschede
On-time · 30 days
95%
21/22 runs under 3 min
RT coverage: 7 full · 15 partial · 7 no data
On-time · 90 days
97%
30/31 runs under 3 min
RT coverage: 12 full · 19 partial · 57 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 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

  • Tue 17 Nov Max en route +6 min · last fix heading to Apeldoorn Osseveld +5 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=5
  • 83% T n=6
  • 100% W n=5
  • 100% T n=3
  • 100% F n=3
  • 100% S n=5
  • 100% S n=4

Stops and timetable

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

Last 90 days, 31 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
16:21on time on time
16:26≈ on time ≈ on time
16:31 / 16:32≈ on time ≈ on time
16:37≈ on time ≈ on time
16:42≈ on time ≈ on time
16:45 / 16:53≈ on time ≈ on time
16:58≈ on time ≈ +1 min
17:03≈ on time ≈ +1 min
17:09≈ on time ≈ +1 min
17:19≈ on time ≈ +1 min
17:24 / 17:25≈ on time ≈ +1 min
17:30≈ on time ≈ +1 min
17:35≈ on time ≈ +1 min
17: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
Wed 18 NovApeldoorn Osseveld 17:49Partial coverage0 min—
Tue 17 NovApeldoorn Osseveld 17:49Partial coverage+5 min+6 min
Mon 16 NovApeldoorn Osseveld 17:49Partial coverage0 min—
Sun 15 NovApeldoorn Osseveld 17:52+1 min+3 min
Sat 14 NovApeldoorn Osseveld 17:49+1 min—
Fri 13 NovApeldoorn Osseveld 17:52Partial coverage+2 min+3 min
Thu 12 NovApeldoorn Osseveld 17:49Partial coverage0 min—
Wed 11 NovApeldoorn Osseveld 17:49Partial coverage+1 min+2 min
Tue 10 NovApeldoorn Osseveld 17:49Partial coverage+2 min+3 min
Mon 9 NovApeldoorn Osseveld 17:49Partial coverage0 min—
Sun 8 NovApeldoorn Osseveld 17:53+2 min+3 min
Sat 7 NovApeldoorn Osseveld 17:490 min—
Fri 6 NovApeldoorn Osseveld 17:49Partial coverage0 min—
Thu 5 NovApeldoorn Osseveld 17:49No data—
Wed 4 NovApeldoorn Osseveld 17:49Partial coverage0 min—
Tue 3 NovApeldoorn Osseveld 17:49Partial coverage0 min—
Mon 2 NovApeldoorn Osseveld 17:49Partial coverage0 min—
Sun 1 NovApeldoorn Osseveld 17:500 min—
Sat 31 OctApeldoorn Osseveld 17:500 min+1 min
Fri 30 OctApeldoorn Osseveld 17:49No data—
Thu 29 OctApeldoorn Osseveld 17:49No data—
Wed 28 OctApeldoorn Osseveld 17:49Partial coverage0 min—
Tue 27 OctApeldoorn Osseveld 17:49Partial coverage0 min—
Mon 26 OctApeldoorn Osseveld 17:49No data—
Sun 25 OctApeldoorn Osseveld 17:51No data—
Sat 24 OctApeldoorn Osseveld 17:52+1 min+3 min
Fri 23 OctApeldoorn Osseveld 17:53No data—
Thu 22 OctApeldoorn Osseveld 17:44Partial coverage0 min—
Wed 21 OctApeldoorn Osseveld 17:49No data—
Tue 20 OctApeldoorn Osseveld 17:56No data—