Train NS 7085 Apeldoorn – Almelo

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

It has not run yet today

Last recorded run: Thursday 5 November 0 min

Next service: today 23:50 from Apeldoorn · Fri 6 Nov

Next departure 23:50 today · Apeldoorn
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 19 full · 2 partial · 2 no data
On-time · 90 days
96%
23/24 runs under 3 min
RT coverage: 22 full · 2 partial · 13 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
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

  • Sun 1 Nov Max en route +7 min · last fix heading to Wierden +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 23
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 24 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
23:50on time on time
23:53≈ on time ≈ on time
23:59≈ on time ≈ on time
00:04 / 00:06≈ on time ≈ on time
00:11≈ on time ≈ on time
00:20≈ on time ≈ on time
00:27≈ on time ≈ +1 min
00:32≈ on time ≈ +1 min
00:37on time on time

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
Thu 5 Nov— 00:390 min—
Wed 4 Nov— 00:390 min—
Tue 3 Nov— 00:390 min—
Mon 2 Nov— 00:380 min—
Sun 1 NovWierden 00:49Partial coverage+3 min+7 min
Sat 31 Oct— 01:000 min—
Wed 28 Oct— 00:380 min—
Tue 27 Oct— 00:390 min—
Mon 26 Oct— 00:380 min—
Sun 25 OctWierden 00:46No data—
Sat 24 Oct— 00:39No data—
Fri 23 Oct— 00:39+1 min—
Thu 22 Oct— 00:380 min—
Wed 21 Oct— 00:380 min—
Tue 20 Oct— 00:380 min—
Mon 19 Oct— 00:430 min+5 min
Thu 15 Oct— 00:380 min—
Wed 14 Oct— 00:430 min—
Tue 13 Oct— 01:070 min—
Sun 11 OctWierden 00:47Partial coverage0 min—
Sat 10 Oct— 00:390 min—
Fri 9 Oct— 00:39+1 min—
Thu 8 Oct— 00:410 min+1 min
Wed 7 Oct— 00:380 min—
Tue 6 Oct— 00:380 min—
Mon 5 OctDeventer 01:010 min+23 min
Sun 4 OctWierden 00:46No data—
Sat 3 OctWierden 00:46No data—
Sun 27 SeptWierden 00:46No data—
Sun 20 SeptWierden 00:46No data—