Train NS 7034 Almelo – Apeldoorn

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

✓ Today’s run finished

Today, last fix heading to Apeldoorn Osseveld at 10:49 No data

  1. Almelo09:53
  2. Wierden09:58
  3. Holten10:09
  4. Deventer Colmschate10:19
  5. Deventer10:24
  6. Apeldoorn Osseveld10:35
  7. Apeldoorn10:40

Next service: tomorrow 09:53 from Almelo · Sat 7 Nov

Next departure 09:53 tomorrow · Almelo
On-time · 30 days
94%
16/17 runs under 3 min
RT coverage: 2 full · 15 partial · 13 no data
On-time · 90 days
95%
18/19 runs under 3 min
RT coverage: 3 full · 16 partial · 70 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: +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

  • Sun 18 Oct Max en route +3 min · last fix heading to Deventer Colmschate +3 min

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 95% · 18
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=4
  • 100% W n=4
  • 100% T n=2
  • 100% F n=2
  • 100% S n=3
  • 67% 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
09:53on time on time
09:58— —
10:04— —
10:09— —
10:19— —
10:24 / 10:25— —
10:30— —
10:35— —
10: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
Fri 6 NovApeldoorn Osseveld 10:49No data—
Thu 5 NovApeldoorn Osseveld 10:49No data—
Wed 4 NovApeldoorn Osseveld 10:49Partial coverage0 min—
Tue 3 NovApeldoorn Osseveld 10:53No data—
Mon 2 NovApeldoorn Osseveld 10:49No data—
Sun 1 NovApeldoorn Osseveld 10:52Partial coverage0 min+1 min
Sat 31 OctApeldoorn Osseveld 10:50Partial coverage0 min—
Fri 30 OctApeldoorn Osseveld 10:50Partial coverage0 min—
Thu 29 OctApeldoorn Osseveld 10:50No data—
Wed 28 OctApeldoorn Osseveld 10:50Partial coverage0 min—
Tue 27 OctApeldoorn Osseveld 10:50Partial coverage0 min—
Mon 26 OctApeldoorn Osseveld 10:50No data—
Sun 25 OctApeldoorn Osseveld 10:52No data—
Sat 24 OctApeldoorn Osseveld 10:53Partial coverage+2 min+3 min
Fri 23 OctApeldoorn Osseveld 10:51No data—
Thu 22 OctApeldoorn Osseveld 10:50Partial coverage0 min—
Wed 21 OctApeldoorn Osseveld 10:50Partial coverage0 min—
Tue 20 OctApeldoorn Osseveld 10:50Partial coverage0 min—
Mon 19 OctApeldoorn Osseveld 10:49Partial coverage0 min—
Sun 18 OctDeventer Colmschate 10:33+3 min+3 min
Sat 17 OctDeventer Colmschate 10:33No data—
Fri 16 OctDeventer Colmschate 10:33No data—
Thu 15 OctDeventer Colmschate 10:33No data—
Wed 14 OctDeventer Colmschate 10:33No data—
Tue 13 OctDeventer Colmschate 10:330 min—
Mon 12 OctDeventer Colmschate 10:36No data—
Sun 11 OctApeldoorn Osseveld 10:50Partial coverage+1 min—
Sat 10 OctApeldoorn Osseveld 10:50Partial coverage0 min—
Fri 9 OctApeldoorn Osseveld 10:49Partial coverage0 min—
Thu 8 OctApeldoorn Osseveld 10:54Partial coverage+3 min+4 min