Train NS 7084 Almelo – Apeldoorn

Almelo 22:23 → Apeldoorn 23:10 Mon, Tue, Wed, Thu, Fri 0 h 47 min · 9 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Friday 13 November +3 min

Next service: Monday 22:23 from Almelo · Mon 16 Nov

Full trip card
Next departure 22:23 Monday · Almelo
On-time · 30 days
87%
13/15 runs under 3 min
RT coverage: 15 full · 0 partial · 6 no data
On-time · 90 days
91%
21/23 runs under 3 min
RT coverage: 23 full · 0 partial · 7 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: +3 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

  • Mon 2 Nov Max en route +8 min · last fix heading to — +7 min
  • Fri 13 Nov Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 21
  • 3–10 min 9% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 100% T n=5
  • 100% W n=3
  • 100% T n=5
  • 80% F n=5
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 23 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
Almelo
22:23on time on time
Wierden
22:28≈ on time ≈ on time
Rijssen
22:34≈ on time ≈ +1 min
Holten
22:39≈ on time ≈ +1 min
Deventer Colmschate
22:49≈ on time ≈ +1 min
Deventer
22:54 / 22:55≈ on time ≈ +2 min
Twello
23:00≈ on time ≈ +2 min
Apeldoorn Osseveld
23:05≈ on time ≈ +2 min
Apeldoorn
23:10on 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
Fri 13 Nov— 23:17+3 min+3 min
Thu 12 Nov— 23:090 min—
Wed 11 Nov— 23:090 min—
Tue 10 Nov— 23:090 min—
Mon 9 Nov— 23:090 min—
Fri 6 Nov— 23:090 min—
Thu 5 Nov— 23:090 min—
Wed 4 Nov— 23:090 min—
Tue 3 Nov— 23:090 min—
Mon 2 Nov— 23:24+7 min+8 min
Fri 30 Oct— 23:11No data—
Thu 29 Oct— 23:110 min—
Wed 28 Oct— 23:11No data—
Tue 27 Oct— 23:110 min—
Mon 26 Oct— 23:11No data—
Fri 23 Oct— 23:14+1 min+1 min
Thu 22 Oct— 23:12No data—
Wed 21 Oct— 23:11No data—
Tue 20 Oct— 23:11No data—
Mon 19 Oct— 23:120 min—
Fri 16 Oct— 22:550 min—
Thu 15 Oct— 22:550 min—
Wed 14 Oct— 22:55No data—
Tue 13 Oct— 22:550 min—
Mon 12 Oct— 23:00+2 min+2 min
Fri 9 Oct— 23:12+1 min—
Thu 8 Oct— 23:14+3 min+3 min
Wed 7 Oct— 23:110 min—
Tue 6 Oct— 23:110 min—
Mon 5 Oct— 23:110 min—