Train NS 7021 Apeldoorn – Enschede

Apeldoorn 07:50 → Enschede 09:08 Daily 1 h 18 min · 14 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 07:50 from Apeldoorn · Fri 6 Nov

Next departure 07:50 today · Apeldoorn
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 7 full · 11 partial · 11 no data
On-time · 90 days
100%
20/20 runs under 3 min
RT coverage: 7 full · 13 partial · 68 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 Enschede, in minutes. One bar per run.

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 20
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=2
  • 100% W n=4
  • 100% T n=3
  • 100% F n=3
  • 100% S n=4
  • 100% S n=2

Stops and timetable

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

Last 90 days, 20 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
07:50on time on time
07:53≈ on time ≈ on time
07:59≈ on time ≈ on time
08:04 / 08:06≈ on time ≈ on time
08:11≈ on time ≈ on time
08:20≈ on time ≈ on time
08:26≈ on time ≈ on time
08:32≈ on time ≈ on time
08:37 / 08:44≈ on time ≈ on time
08:47≈ on time ≈ +1 min
08:53≈ on time ≈ +1 min
08:58 / 08:59≈ on time ≈ +1 min
09:04≈ +1 min ≈ +1 min
09:08+1 min +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
Thu 5 NovEnschede Kennispark 09:18No data—
Wed 4 NovEnschede Kennispark 09:18Partial coverage0 min—
Tue 3 NovEnschede Kennispark 09:18No data—
Mon 2 NovEnschede Kennispark 09:18No data—
Sun 1 NovWierden 08:46No data—
Sat 31 OctWierden 08:47+1 min—
Fri 30 OctEnschede Kennispark 09:18Partial coverage0 min—
Thu 29 OctEnschede Kennispark 09:18Partial coverage0 min—
Wed 28 OctEnschede Kennispark 09:18Partial coverage0 min—
Tue 27 OctEnschede Kennispark 09:18No data—
Mon 26 OctEnschede Kennispark 09:18Partial coverage0 min—
Sun 25 OctWierden 08:46No data—
Sat 24 OctWierden 08:460 min—
Fri 23 OctEnschede Kennispark 09:19Partial coverage0 min—
Thu 22 OctEnschede Kennispark 09:18No data—
Wed 21 OctEnschede Kennispark 09:18Partial coverage0 min—
Tue 20 OctEnschede Kennispark 09:18Partial coverage0 min—
Mon 19 OctEnschede Kennispark 09:19Partial coverage0 min—
Sun 18 OctWierden 08:47+1 min—
Sat 17 OctWierden 08:47+1 min+1 min
Fri 16 OctEnschede Kennispark 09:18No data—
Thu 15 OctEnschede Kennispark 09:190 min—
Wed 14 OctEnschede Kennispark 09:18No data—
Tue 13 OctEnschede Kennispark 09:19No data—
Mon 12 OctEnschede Kennispark 09:19No data—
Sun 11 OctWierden 08:47+1 min—
Sat 10 OctWierden 08:47+1 min—
Fri 9 OctEnschede Kennispark 09:19Partial coverage+1 min+1 min
Thu 8 OctEnschede Kennispark 09:20Partial coverage+2 min+3 min
Wed 7 OctEnschede Kennispark 09:18Partial coverage0 min—