Train NS 7075 Apeldoorn – Almelo

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

It has not run yet today

Last recorded run: Wednesday 11 November 0 min

Next service: today 21:20 from Apeldoorn · Thu 12 Nov

Next departure 21:20 today · Apeldoorn
On-time · 30 days
82%
9/11 runs under 3 min
RT coverage: 11 full · 0 partial · 10 no data
On-time · 90 days
88%
15/17 runs under 3 min
RT coverage: 17 full · 0 partial · 11 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Wed 4 Nov Max en route +5 min · last fix heading to — +5 min
  • Mon 9 Nov Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 15
  • 3–10 min 12% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 17 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
21:20on time on time
21:23≈ on time ≈ +1 min
21:29≈ on time ≈ +1 min
21:34 / 21:36≈ on time ≈ +2 min
21:41≈ on time ≈ +2 min
21:50≈ on time ≈ +2 min
21:56≈ on time ≈ +3 min
22:02≈ on time ≈ +3 min
22:06on time +3 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
Wed 11 Nov— 22:070 min—
Tue 10 Nov— 22:070 min—
Mon 9 Nov— 22:14+4 min+4 min
Fri 6 Nov— 22:070 min—
Thu 5 Nov— 22:08No data—
Wed 4 Nov— 22:18+5 min+5 min
Tue 3 Nov— 22:08No data—
Mon 2 Nov— 22:09+1 min+3 min
Fri 30 Oct— 22:07No data—
Thu 29 Oct— 22:070 min—
Wed 28 Oct— 22:070 min—
Tue 27 Oct— 22:140 min—
Mon 26 Oct— 22:10No data—
Fri 23 Oct— 22:12+2 min+2 min
Thu 22 Oct— 22:08No data—
Wed 21 Oct— 22:08No data—
Tue 20 Oct— 22:20No data—
Mon 19 Oct— 21:36No data—
Fri 16 Oct— 22:10+2 min+2 min
Thu 15 Oct— 22:07No data—
Wed 14 Oct— 22:07No data—
Tue 13 Oct— 22:07No data—
Mon 12 Oct— 22:070 min—
Fri 9 Oct— 22:07+1 min—
Thu 8 Oct— 22:070 min—
Wed 7 Oct— 22:070 min—
Tue 6 Oct— 22:09+1 min+1 min
Mon 5 Oct— 22:070 min—