Train NS 7032 Enschede – Apeldoorn

Enschede 08:51 → Apeldoorn 10:10 Mon, Tue, Wed, Thu, Fri 1 h 19 min · 14 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Apeldoorn Osseveld at 10:19 0 min

  1. Enschede08:51
  2. Hengelo09:00
  3. Almelo de Riet09:12
  4. Rijssen09:33
  5. Deventer Colmschate09:49
  6. Apeldoorn Osseveld10:05
  7. Apeldoorn10:10

Next service: tomorrow 08:51 from Enschede · Wed 18 Nov

Next departure 08:51 tomorrow · Enschede
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 0 full · 15 partial · 7 no data
On-time · 90 days
95%
19/20 runs under 3 min
RT coverage: 1 full · 19 partial · 43 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

  • Wed 4 Nov Max en route +12 min · last fix heading to Apeldoorn Osseveld +11 min

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 95% · 19
  • 3–10 min 0% · 0
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

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

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
08:51on time on time
08:55— —
09:00 / 09:02— —
09:07— —
09:12— —
09:15 / 09:23— —
09:28— —
09:33— —
09:39— —
09:49— —
09:54 / 09:55— —
10:00— —
10:05— —
10:10— —

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
Tue 17 NovApeldoorn Osseveld 10:19Partial coverage0 min—
Mon 16 NovApeldoorn Osseveld 10:23Partial coverage+3 min+3 min
Fri 13 NovApeldoorn Osseveld 10:19Partial coverage0 min—
Thu 12 NovApeldoorn Osseveld 10:19Partial coverage+2 min+2 min
Wed 11 NovApeldoorn Osseveld 10:19Partial coverage0 min—
Tue 10 NovApeldoorn Osseveld 10:19Partial coverage0 min+1 min
Mon 9 NovApeldoorn Osseveld 10:19Partial coverage0 min—
Fri 6 NovApeldoorn Osseveld 10:19No data—
Thu 5 NovApeldoorn Osseveld 10:19No data—
Wed 4 NovApeldoorn Osseveld 10:29Partial coverage+11 min+12 min
Tue 3 NovApeldoorn Osseveld 10:19No data—
Mon 2 NovApeldoorn Osseveld 10:19No data—
Fri 30 OctApeldoorn Osseveld 10:21No data—
Thu 29 OctApeldoorn Osseveld 10:20No data—
Wed 28 OctApeldoorn Osseveld 10:20Partial coverage0 min—
Tue 27 OctApeldoorn Osseveld 10:20Partial coverage0 min—
Mon 26 OctApeldoorn Osseveld 10:20No data—
Fri 23 OctApeldoorn Osseveld 10:20Partial coverage0 min—
Thu 22 OctApeldoorn Osseveld 10:21Partial coverage0 min—
Wed 21 OctApeldoorn Osseveld 10:20Partial coverage0 min—
Tue 20 OctApeldoorn Osseveld 10:20Partial coverage0 min—
Mon 19 OctApeldoorn Osseveld 10:20Partial coverage0 min—
Fri 16 OctDeventer Colmschate 10:040 min—
Thu 15 OctWierden 10:58No data—
Wed 14 OctDeventer Colmschate 10:03No data—
Tue 13 OctDeventer Colmschate 10:03No data—
Mon 12 OctDeventer Colmschate 10:04No data—
Fri 9 OctApeldoorn Osseveld 10:20Partial coverage0 min—
Thu 8 OctApeldoorn Osseveld 10:20Partial coverage+1 min—
Wed 7 OctApeldoorn Osseveld 10:20Partial coverage0 min—