Train NS 7030 Almelo – Apeldoorn

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

✓ Today’s run finished

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

  1. Almelo08:53
  2. Wierden08:58
  3. Holten09:09
  4. Deventer Colmschate09:19
  5. Deventer09:24
  6. Apeldoorn Osseveld09:35
  7. Apeldoorn09:40

Next service: tomorrow 08:53 from Almelo · Sun 8 Nov

Next departure 08:53 tomorrow · Almelo
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 15 full · 6 partial · 9 no data
On-time · 90 days
100%
24/24 runs under 3 min
RT coverage: 18 full · 6 partial · 65 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

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

  • Early 0% · 0
  • On time 100% · 24
  • 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=5
  • 100% W n=3
  • 100% T n=3
  • 100% F n=3
  • 100% S n=5
  • 100% S n=3

Stops and timetable

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

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

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