Train NS 7061 Apeldoorn – Almelo

Apeldoorn 17:50 → Almelo 18:37 Daily 0 h 47 min · 9 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November No data

Next service: today 17:50 from Apeldoorn · Thu 5 Nov

Next departure 17:50 today · Apeldoorn
On-time · 30 days
94%
16/17 runs under 3 min
RT coverage: 4 full · 13 partial · 12 no data
On-time · 90 days
95%
18/19 runs under 3 min
RT coverage: 4 full · 15 partial · 69 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: +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

Worst days

  • Fri 9 Oct Max en route +5 min · last fix heading to Wierden +5 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 19 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:50on time on time
17:53— —
17:59— —
18:04 / 18:06— —
18:11— —
18:20— —
18:27— —
18:32— —
18:37— —

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
Wed 4 NovDeventer Colmschate 18:39No data—
Tue 3 NovDeventer Colmschate 18:24Partial coverage0 min—
Mon 2 NovDeventer 18:38Partial coverage0 min—
Sun 1 NovWierden 18:44Partial coverage0 min+2 min
Sat 31 OctWierden 18:47Partial coverage+1 min—
Fri 30 OctWierden 18:59No data—
Thu 29 OctTwello 18:39No data—
Wed 28 OctDeventer Colmschate 18:41Partial coverage+2 min+2 min
Tue 27 OctTwello 18:51No data—
Mon 26 OctDeventer 18:50Partial coverage0 min—
Sun 25 OctWierden 18:46No data—
Sat 24 OctWierden 18:46No data—
Fri 23 OctWierden 18:46Partial coverage+1 min+1 min
Thu 22 OctWierden 18:46Partial coverage0 min—
Wed 21 OctWierden 19:16No data—
Tue 20 OctWierden 18:46No data—
Mon 19 OctWierden 18:46No data—
Sun 18 OctWierden 18:460 min—
Sat 17 OctWierden 18:46No data—
Fri 16 OctWierden 18:470 min—
Thu 15 OctRijssen 18:50No data—
Wed 14 OctWierden 18:42No data—
Tue 13 OctWierden 18:460 min—
Mon 12 OctWierden 18:460 min—
Sun 11 OctWierden 18:47Partial coverage+1 min—
Sat 10 OctWierden 18:47Partial coverage+1 min—
Fri 9 OctWierden 18:46Partial coverage+5 min+5 min
Thu 8 OctTwello 18:41Partial coverage+1 min+3 min
Wed 7 OctDeventer 18:38Partial coverage0 min—
Tue 6 OctTwello 18:39Partial coverage+2 min+2 min