Train NS 7070 Almelo – Apeldoorn

Almelo 18:53 → Apeldoorn 19:40 Daily 0 h 47 min · 9 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 6 November +1 min

Next service: today 18:53 from Almelo · Sat 7 Nov

Next departure 18:53 today · Almelo
On-time · 30 days
100%
15/15 runs under 3 min
RT coverage: 10 full · 5 partial · 13 no data
On-time · 90 days
100%
19/19 runs under 3 min
RT coverage: 14 full · 5 partial · 41 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 Apeldoorn, 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

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

  • Early 0% · 0
  • On time 100% · 19
  • 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=3
  • 100% T n=2
  • 100% F n=4
  • 100% S n=2
  • 100% S n=3

Stops and timetable

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

Last 90 days, 19 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
18:53on time on time
18:58≈ on time ≈ on time
19:04≈ on time ≈ on time
19:09≈ on time ≈ on time
19:19≈ on time ≈ +1 min
19:24 / 19:25≈ on time ≈ +1 min
19:30≈ on time ≈ +1 min
19:35≈ on time ≈ +1 min
19:40on time +1 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 6 Nov— 19:44+1 min+3 min
Thu 5 Nov— 19:39No data—
Wed 4 Nov— 19:390 min—
Tue 3 Nov— 19:42No data—
Sun 1 NovApeldoorn Osseveld 19:49Partial coverage+1 min—
Sat 31 OctApeldoorn Osseveld 19:50Partial coverage+1 min—
Fri 30 OctAlmelo 19:41No data—
Thu 29 Oct— 19:420 min+2 min
Wed 28 Oct— 19:410 min—
Tue 27 Oct— 19:420 min—
Mon 26 OctApeldoorn Osseveld 19:48No data—
Sun 25 OctApeldoorn Osseveld 19:51No data—
Sat 24 OctApeldoorn Osseveld 19:51No data—
Fri 23 OctDeventer 19:45Partial coverage+1 min+2 min
Thu 22 Oct— 19:42No data—
Wed 21 Oct— 20:08No data—
Tue 20 Oct— 19:41No data—
Mon 19 Oct— 19:42No data—
Sun 18 OctDeventer Colmschate 19:35+2 min+2 min
Sat 17 OctDeventer Colmschate 19:33No data—
Fri 16 OctDeventer Colmschate 19:330 min—
Thu 15 Oct— 19:25No data—
Wed 14 OctDeventer Colmschate 19:33No data—
Tue 13 Oct— 19:260 min—
Mon 12 Oct— 19:260 min—
Sun 11 OctApeldoorn Osseveld 19:50Partial coverage0 min—
Sat 10 OctApeldoorn Osseveld 19:50Partial coverage0 min—
Fri 9 Oct— 19:410 min—
Thu 8 Oct— 19:42+1 min—
Wed 7 Oct— 19:410 min—