Train NS 7050 Almelo – Apeldoorn

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

✓ Today’s run finished

Today, last fix heading to Apeldoorn Osseveld at 14:49 0 min

  1. Almelo13:53
  2. Wierden13:58
  3. Holten14:09
  4. Deventer Colmschate14:19
  5. Deventer14:24
  6. Apeldoorn Osseveld14:35
  7. Apeldoorn14:40

Next service: tomorrow 13:53 from Almelo · Mon 9 Nov

Next departure 13:53 tomorrow · Almelo
On-time · 30 days
100%
15/15 runs under 3 min
RT coverage: 3 full · 12 partial · 15 no data
On-time · 90 days
100%
20/20 runs under 3 min
RT coverage: 3 full · 17 partial · 69 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

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

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

Stops and timetable

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

Last 90 days, 20 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
13:53on time on time
13:58— —
14:04— —
14:09— —
14:19— —
14:24 / 14:25— —
14:30— —
14:35— —
14:40— —

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
Sun 8 NovApeldoorn Osseveld 14:49Partial coverage0 min—
Sat 7 NovApeldoorn Osseveld 14:50Partial coverage0 min—
Fri 6 NovApeldoorn Osseveld 14:49No data—
Thu 5 NovApeldoorn Osseveld 14:49No data—
Wed 4 NovApeldoorn Osseveld 14:49Partial coverage0 min+1 min
Tue 3 NovApeldoorn Osseveld 14:49No data—
Mon 2 NovApeldoorn Osseveld 14:49No data—
Sun 1 NovApeldoorn Osseveld 14:51Partial coverage0 min—
Sat 31 OctApeldoorn Osseveld 14:49No data—
Fri 30 OctApeldoorn Osseveld 14:49Partial coverage0 min—
Thu 29 OctApeldoorn Osseveld 14:50No data—
Wed 28 OctApeldoorn Osseveld 14:50Partial coverage0 min—
Tue 27 OctApeldoorn Osseveld 14:49Partial coverage0 min—
Mon 26 OctApeldoorn Osseveld 14:50No data—
Sun 25 OctApeldoorn Osseveld 14:53No data—
Sat 24 OctApeldoorn Osseveld 14:50Partial coverage0 min—
Fri 23 OctApeldoorn Osseveld 14:50No data—
Thu 22 OctApeldoorn Osseveld 14:50Partial coverage0 min—
Wed 21 OctApeldoorn Osseveld 14:58No data—
Tue 20 OctApeldoorn Osseveld 15:240 min—
Mon 19 OctApeldoorn Osseveld 14:50Partial coverage0 min—
Sun 18 OctDeventer Colmschate 14:330 min—
Sat 17 OctDeventer Colmschate 14:33No data—
Fri 16 OctDeventer Colmschate 14:330 min—
Thu 15 OctDeventer Colmschate 14:33No data—
Wed 14 OctDeventer Colmschate 14:33No data—
Tue 13 OctDeventer Colmschate 14:33No data—
Mon 12 OctDeventer Colmschate 14:33No data—
Sun 11 OctApeldoorn Osseveld 14:50Partial coverage0 min—
Sat 10 OctApeldoorn Osseveld 14:50Partial coverage0 min—