Train NS 7023 Apeldoorn – Almelo

Apeldoorn 08:20 → Almelo 09:06 Mon, Tue, Wed, Thu, Fri 0 h 46 min · 9 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Friday 6 November No data

Next service: Monday 08:20 from Apeldoorn · Mon 9 Nov

Next departure 08:20 Monday · Apeldoorn
On-time · 30 days
100%
8/8 runs under 3 min
RT coverage: 0 full · 8 partial · 13 no data
On-time · 90 days
100%
9/9 runs under 3 min
RT coverage: 0 full · 9 partial · 55 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Almelo, 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 9 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:20on time on time
08:23— —
08:29— —
08:34 / 08:36— —
08:41— —
08:50— —
08:56— —
09:02— —
09:06— —

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 NovWierden 09:14No data—
Thu 5 NovWierden 09:18No data—
Wed 4 NovWierden 09:14Partial coverage0 min+2 min
Tue 3 NovWierden 09:24No data—
Mon 2 NovWierden 09:18No data—
Fri 30 OctWierden 09:16No data—
Thu 29 OctWierden 09:16Partial coverage0 min—
Wed 28 OctWierden 09:19Partial coverage0 min—
Tue 27 OctWierden 09:16Partial coverage0 min—
Mon 26 OctWierden 09:16No data—
Fri 23 OctWierden 09:18No data—
Thu 22 OctWierden 09:20No data—
Wed 21 OctWierden 09:23Partial coverage0 min—
Tue 20 OctWierden 09:16Partial coverage0 min—
Mon 19 OctWierden 09:16Partial coverage0 min—
Fri 16 OctWierden 09:18No data—
Thu 15 OctWierden 09:16No data—
Wed 14 OctWierden 09:16No data—
Tue 13 OctWierden 09:16No data—
Mon 12 OctWierden 09:18No data—
Fri 9 OctWierden 09:18Partial coverage+2 min+2 min
Thu 8 OctWierden 09:16Partial coverage0 min—
Wed 7 OctWierden 09:16No data—
Tue 6 OctWierden 09:16No data—
Mon 5 OctWierden 09:16No data—
Fri 2 OctWierden 09:16No data—
Thu 1 OctWierden 09:17No data—
Wed 30 SeptWierden 09:16No data—
Tue 29 SeptWierden 09:18No data—
Mon 28 SeptWierden 09:16No data—