Train NS 7081 Apeldoorn – Almelo

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

It has not run yet today

Last recorded run: Thursday 12 November +2 min

Next service: today 22:50 from Apeldoorn · Fri 13 Nov

Next departure 22:50 today · Apeldoorn
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 21 full · 0 partial · 7 no data
On-time · 90 days
90%
28/31 runs under 3 min
RT coverage: 31 full · 0 partial · 21 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: +2 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 18 Oct Max en route +7 min · last fix heading to Wierden +7 min
  • Mon 12 Oct Max en route +6 min · last fix heading to — +6 min
  • Fri 9 Oct Max en route +5 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 28
  • 3–10 min 10% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 31 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:50on time on time
22:53≈ on time ≈ on time
22:59≈ on time ≈ +1 min
23:04 / 23:06≈ on time ≈ +1 min
23:11≈ on time ≈ +2 min
23:20≈ on time ≈ +2 min
23:27≈ on time ≈ +2 min
23:32≈ on time ≈ +2 min
23:37on time +2 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
Thu 12 Nov— 23:39+2 min+2 min
Wed 11 Nov— 23:380 min—
Tue 10 Nov— 23:520 min+28 min
Mon 9 Nov— 23:39+1 min—
Sun 8 NovWierden 23:440 min—
Sat 7 NovHolten 23:380 min—
Fri 6 Nov— 23:39+1 min+1 min
Thu 5 Nov— 23:390 min—
Wed 4 Nov— 23:380 min—
Tue 3 Nov— 23:390 min—
Sun 1 NovWierden 23:49+2 min+3 min
Sat 31 OctHolten 23:34No data—
Fri 30 Oct— 23:51No data—
Thu 29 Oct— 23:40+1 min+1 min
Wed 28 Oct— 23:380 min—
Tue 27 Oct— 23:390 min—
Mon 26 Oct— 23:41No data—
Sun 25 OctWierden 23:46No data—
Sat 24 Oct— 23:39No data—
Fri 23 Oct— 23:390 min—
Thu 22 Oct— 23:390 min—
Wed 21 Oct— 23:39No data—
Tue 20 Oct— 23:120 min—
Mon 19 Oct— 23:390 min—
Sun 18 OctWierden 23:50+7 min+7 min
Sat 17 OctWierden 23:47No data—
Fri 16 Oct— 23:38+1 min+1 min
Thu 15 Oct— 23:380 min—
Wed 14 Oct— 23:380 min—
Tue 13 Oct— 23:380 min—