Train NS 7064 Enschede – Apeldoorn

Enschede 16:51 → Apeldoorn 18: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 18:19 +4 min

  1. Enschede16:51
  2. Hengelo17:00
  3. Almelo de Riet17:12
  4. Rijssen17:33
  5. Deventer Colmschate17:49
  6. Apeldoorn Osseveld18:05
  7. Apeldoorn18:10

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

Next departure 16:51 tomorrow · Enschede
On-time · 30 days
93%
13/14 runs under 3 min
RT coverage: 0 full · 14 partial · 8 no data
On-time · 90 days
95%
21/22 runs under 3 min
RT coverage: 4 full · 18 partial · 41 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

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 21
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 80% T n=5
  • 100% W n=5
  • 100% T n=2
  • 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, 22 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:51on time on time
16:55— —
17:00 / 17:02— —
17:07— —
17:12— —
17:15 / 17:23— —
17:28— —
17:33— —
17:39— —
17:49— —
17:54 / 17:55— —
18:00— —
18:05— —
18: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 18:19Partial coverage+4 min+4 min
Mon 16 NovApeldoorn Osseveld 18:19Partial coverage0 min—
Fri 13 NovApeldoorn Osseveld 18:19Partial coverage+2 min+3 min
Thu 12 NovApeldoorn Osseveld 18:19Partial coverage+1 min+1 min
Wed 11 NovApeldoorn Osseveld 18:19Partial coverage0 min—
Tue 10 NovApeldoorn Osseveld 18:19Partial coverage0 min—
Mon 9 NovApeldoorn Osseveld 18:19Partial coverage0 min+1 min
Fri 6 NovApeldoorn Osseveld 18:19Partial coverage+1 min—
Thu 5 NovApeldoorn Osseveld 18:19No data—
Wed 4 NovApeldoorn Osseveld 18:19Partial coverage0 min—
Tue 3 NovApeldoorn Osseveld 18:19No data—
Mon 2 NovApeldoorn Osseveld 18:19No data—
Fri 30 OctApeldoorn Osseveld 18:19No data—
Thu 29 OctTwello 18:14No data—
Wed 28 OctApeldoorn Osseveld 18:19Partial coverage0 min—
Tue 27 OctApeldoorn Osseveld 18:19Partial coverage0 min—
Mon 26 OctApeldoorn Osseveld 18:19Partial coverage+1 min—
Fri 23 OctApeldoorn Osseveld 18:21No data—
Thu 22 OctApeldoorn Osseveld 18:19No data—
Wed 21 OctApeldoorn Osseveld 18:19Partial coverage0 min—
Tue 20 OctApeldoorn Osseveld 18:19No data—
Mon 19 OctApeldoorn Osseveld 18:19Partial coverage0 min—
Fri 16 OctDeventer Colmschate 18:030 min—
Thu 15 OctDeventer Colmschate 18:03No data—
Wed 14 OctDeventer Colmschate 18:03No data—
Tue 13 OctDeventer Colmschate 18:030 min—
Mon 12 OctDeventer Colmschate 18:030 min—
Fri 9 OctApeldoorn Osseveld 18:19Partial coverage0 min—
Thu 8 OctTwello 18:140 min—
Wed 7 OctApeldoorn Osseveld 18:19Partial coverage0 min—