Train NS 7057 Apeldoorn – Enschede

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

It has not run yet today

Last recorded run: Friday 13 November +7 min

Next service: today 16:50 from Apeldoorn · Sat 14 Nov

Next departure 16:50 today · Apeldoorn
On-time · 30 days
87%
13/15 runs under 3 min
RT coverage: 7 full · 8 partial · 14 no data
On-time · 90 days
91%
21/23 runs under 3 min
RT coverage: 11 full · 12 partial · 65 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: +5 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

Worst days

  • Sat 31 Oct Max en route +13 min · last fix heading to Wierden +12 min
  • Fri 13 Nov Max en route +7 min · last fix heading to Enschede Kennispark +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 21
  • 3–10 min 4% · 1
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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