Train NS 7068 Enschede – Apeldoorn

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

It does not run today

Last recorded run: Friday 6 November +3 min

Next service: Monday 17:51 from Enschede · Mon 9 Nov

Next departure 17:51 Monday · Enschede
On-time · 30 days
78%
7/9 runs under 3 min
RT coverage: 2 full · 7 partial · 12 no data
On-time · 90 days
85%
11/13 runs under 3 min
RT coverage: 2 full · 11 partial · 51 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Fri 23 Oct Max en route +5 min · last fix heading to Enschede Kennispark +4 min
  • Fri 6 Nov Max en route +4 min · last fix heading to Holten +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 85% · 11
  • 3–10 min 15% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=1
  • 100% W n=3
  • 100% T n=2
  • 33% F n=3
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 13 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
17:51on time on time
17:55— —
18:00 / 18:02— —
18:07— —
18:12— —
18:15 / 18:23— —
18:28— —
18:33— —
18:39— —
18:49— —
18:54 / 18:55— —
19:00— —
19:05— —
19: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
Fri 6 NovHolten 19:17Partial coverage+3 min+4 min
Thu 5 NovAlmelo de Riet 19:09No data—
Wed 4 NovAlmelo de Riet 19:120 min—
Tue 3 NovAlmelo de Riet 19:09No data—
Mon 2 NovBorne 19:09Partial coverage0 min—
Fri 30 OctDeventer Colmschate 19:11No data—
Thu 29 OctHengelo 19:14Partial coverage0 min+2 min
Wed 28 OctAlmelo de Riet 19:11Partial coverage0 min—
Tue 27 OctHengelo 19:18No data—
Mon 26 OctBorne 19:14Partial coverage0 min—
Fri 23 OctEnschede Kennispark 19:17Partial coverage+4 min+5 min
Thu 22 OctHolten 19:12No data—
Wed 21 OctHolten 19:12No data—
Tue 20 OctHolten 19:11No data—
Mon 19 OctHolten 19:20No data—
Fri 16 OctDeventer Colmschate 19:03No data—
Thu 15 OctWierden 18:57No data—
Wed 14 OctDeventer Colmschate 19:03No data—
Tue 13 OctHolten 18:55No data—
Mon 12 OctHolten 18:560 min—
Fri 9 OctRijssen 19:11Partial coverage0 min—
Thu 8 OctHengelo 19:12Partial coverage0 min—
Wed 7 OctBorne 19:11Partial coverage0 min—
Tue 6 OctHengelo 19:11Partial coverage0 min—
Mon 5 OctAlmelo de Riet 19:12Partial coverage+1 min—
Fri 2 OctHolten 18:53No data—
Thu 1 OctHengelo 18:16No data—
Wed 30 SeptBorne 18:18No data—
Tue 29 SeptBorne 18:21No data—
Mon 28 SeptHengelo 18:16No data—