Train NS 7035 Apeldoorn – Almelo

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

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 11:20 from Apeldoorn · Fri 6 Nov

Next departure 11:20 today · Apeldoorn
On-time · 30 days
100%
10/10 runs under 3 min
RT coverage: 1 full · 9 partial · 11 no data
On-time · 90 days
100%
12/12 runs under 3 min
RT coverage: 1 full · 11 partial · 51 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 12
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 12 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
11:20on time on time
11:23— —
11:29— —
11:34 / 11:36— —
11:41— —
11:50— —
11:56— —
12:02— —
12:06— —

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 NovWierden 12:19No data—
Wed 4 NovWierden 12:18Partial coverage+3 min+3 min
Tue 3 NovWierden 12:23No data—
Mon 2 NovWierden 12:14No data—
Fri 30 OctWierden 12:20No data—
Thu 29 OctWierden 12:17No data—
Wed 28 OctWierden 12:16Partial coverage0 min—
Tue 27 OctWierden 12:16Partial coverage0 min—
Mon 26 OctWierden 12:16Partial coverage0 min—
Fri 23 OctWierden 12:20No data—
Thu 22 OctWierden 12:19No data—
Wed 21 OctWierden 12:19Partial coverage0 min—
Tue 20 OctWierden 12:16Partial coverage0 min—
Mon 19 OctWierden 12:16Partial coverage0 min—
Fri 16 OctWierden 12:160 min—
Thu 15 OctWierden 12:16No data—
Wed 14 OctWierden 12:16No data—
Tue 13 OctWierden 12:16No data—
Mon 12 OctWierden 12:33No data—
Fri 9 OctWierden 12:16Partial coverage0 min—
Thu 8 OctWierden 12:17Partial coverage+2 min+2 min
Wed 7 OctWierden 12:16Partial coverage0 min—
Tue 6 OctWierden 12:16Partial coverage0 min—
Mon 5 OctWierden 12:16No data—
Fri 2 OctWierden 12:16No data—
Thu 1 OctWierden 12:16No data—
Wed 30 SeptWierden 12:16No data—
Tue 29 SeptWierden 12:17No data—
Mon 28 SeptWierden 12:16No data—
Fri 25 SeptWierden 12:16No data—