Train NS 7086 Almelo – Apeldoorn

Almelo 22:53 → Apeldoorn 23:40 Daily 0 h 47 min · 9 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 13 November 0 min

Next service: today 22:53 from Almelo · Sat 14 Nov

Next departure 22:53 today · Almelo
On-time · 30 days
86%
18/21 runs under 3 min
RT coverage: 20 full · 1 partial · 8 no data
On-time · 90 days
87%
26/30 runs under 3 min
RT coverage: 29 full · 1 partial · 23 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+6min
9 in 10 runs arrive with less than this
30 days: +5 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

  • Sun 1 Nov Max en route +16 min · last fix heading to Twello +15 min
  • Mon 19 Oct Max en route +12 min · last fix heading to — +11 min
  • Mon 12 Oct Max en route +10 min · last fix heading to — +10 min
  • Sun 18 Oct Max en route +5 min · last fix heading to Almelo +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 87% · 26
  • 3–10 min 3% · 1
  • 10–30 min 10% · 3
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 30 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
22:53on time on time
22:58≈ on time ≈ +1 min
23:04≈ on time ≈ +2 min
23:09≈ on time ≈ +3 min
23:19≈ on time ≈ +3 min
23:24 / 23:25≈ on time ≈ +4 min
23:30≈ on time ≈ +5 min
23:35≈ on time ≈ +5 min
23:40on time +6 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 Nov— 23:390 min—
Thu 12 Nov— 23:390 min—
Wed 11 Nov— 23:390 min—
Tue 10 Nov— 23:470 min+19 min
Mon 9 Nov— 23:42+1 min+1 min
Sun 8 NovApeldoorn Osseveld 23:490 min—
Sat 7 NovDeventer Colmschate 23:42Partial coverage+1 min—
Fri 6 Nov— 23:390 min—
Thu 5 Nov— 23:420 min—
Wed 4 Nov— 23:39+1 min+1 min
Tue 3 Nov— 23:39No data—
Mon 2 Nov— 23:47+3 min+4 min
Sun 1 NovTwello 00:08+15 min+16 min
Sat 31 OctDeventer Colmschate 23:33No data—
Fri 30 Oct— 00:08No data—
Thu 29 Oct— 23:410 min—
Wed 28 Oct— 23:390 min—
Tue 27 Oct— 23:420 min—
Mon 26 Oct— 23:410 min—
Sun 25 OctApeldoorn Osseveld 23:50No data—
Sat 24 Oct— 23:44No data—
Fri 23 Oct— 23:42+1 min—
Thu 22 Oct— 23:410 min—
Wed 21 Oct— 23:41No data—
Tue 20 Oct— 23:41No data—
Mon 19 Oct— 23:55+11 min+12 min
Sun 18 OctAlmelo 23:35+5 min+5 min
Sat 17 OctDeventer Colmschate 23:33No data—
Fri 16 Oct— 23:25+1 min+1 min
Thu 15 Oct— 23:33No data—