Train NS 7031 Apeldoorn – Almelo

Apeldoorn 10:20 → Almelo 11:06 Mon, Tue, Wed, Thu, Fri 0 h 46 min · 9 stops NS (Nederlandse Spoorwegen)

Running now · updated 10:52

Heading to Almelo 0 min

Estimated arrival at Almelo 11:06 · 93 km/h

  1. Apeldoorn10:20
  2. Apeldoorn Osseveld10:23
  3. Deventer10:34
  4. Deventer Colmschate10:41
  5. Holten10:50
  6. Wierden11:02
  7. Almelo11:06

Today it is running no worse than usual: typical arrival delay is 0 min; 80% of the last 15 runs arrived on time.

On-time · 30 days
80%
12/15 runs under 3 min
RT coverage: 0 full · 15 partial · 7 no data
On-time · 90 days
85%
17/20 runs under 3 min
RT coverage: 1 full · 19 partial · 43 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +5 min

Last 30 days

Arrival delay at Almelo, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Wed 11 Nov Max en route +16 min · last fix heading to Wierden +15 min
  • Mon 16 Nov Max en route +6 min · last fix heading to Wierden +6 min
  • Tue 10 Nov Max en route +4 min · last fix heading to Wierden +4 min

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

On-time by weekday

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

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 10Today
10:20on time on time
10:23— —
10:29— —
10:34 / 10:36— —
10:41— —
10:50— —
10:56— —
11:02— —
11:06— —

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
Tue 17 NovHolten 10:49Partial coverage0 min—
Mon 16 NovWierden 11:19Partial coverage+6 min+6 min
Fri 13 NovWierden 11:14Partial coverage0 min—
Thu 12 NovWierden 11:14Partial coverage0 min—
Wed 11 NovWierden 11:29Partial coverage+15 min+16 min
Tue 10 NovWierden 11:19Partial coverage+4 min+4 min
Mon 9 NovWierden 11:14Partial coverage0 min—
Fri 6 NovWierden 11:18No data—
Thu 5 NovWierden 11:14No data—
Wed 4 NovWierden 11:17Partial coverage+1 min+2 min
Tue 3 NovWierden 11:17No data—
Mon 2 NovWierden 11:14No data—
Fri 30 OctWierden 11:16No data—
Thu 29 OctWierden 11:20No data—
Wed 28 OctWierden 11:16Partial coverage0 min—
Tue 27 OctWierden 11:16Partial coverage0 min—
Mon 26 OctWierden 11:16No data—
Fri 23 OctWierden 11:16Partial coverage0 min—
Thu 22 OctWierden 11:21Partial coverage0 min—
Wed 21 OctWierden 11:16Partial coverage0 min—
Tue 20 OctWierden 11:16Partial coverage0 min—
Mon 19 OctWierden 11:16Partial coverage0 min—
Fri 16 OctWierden 11:16No data—
Thu 15 OctWierden 11:16No data—
Wed 14 OctWierden 11:16No data—
Tue 13 OctWierden 11:160 min—
Mon 12 OctWierden 11:16No data—
Fri 9 OctWierden 11:16Partial coverage0 min—
Thu 8 OctWierden 11:17Partial coverage+1 min+4 min
Wed 7 OctDeventer 12:01Partial coverage0 min—