Train NS 7049 Apeldoorn – Almelo

Apeldoorn 14:50 → Almelo 15:37 Daily 0 h 47 min · 9 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Wierden at 15:47 +1 min

  1. Apeldoorn14:50
  2. Apeldoorn Osseveld14:53
  3. Deventer15:04
  4. Deventer Colmschate15:11
  5. Holten15:20
  6. Wierden15:32
  7. Almelo15:37

Next service: tomorrow 14:50 from Apeldoorn · Sun 15 Nov

Next departure 14:50 tomorrow · Apeldoorn
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 12 full · 6 partial · 12 no data
On-time · 90 days
96%
26/27 runs under 3 min
RT coverage: 19 full · 8 partial · 62 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 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

  • Mon 5 Oct Max en route +3 min · last fix heading to Enschede Kennispark +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 26
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 100% T n=3
  • 100% W n=4
  • 100% T n=4
  • 100% F n=3
  • 100% S n=5
  • 100% S n=4

Stops and timetable

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

Last 90 days, 27 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
14:50on time on time
14:53≈ on time ≈ on time
14:59≈ on time ≈ on time
15:04 / 15:06≈ on time ≈ on time
15:11≈ on time ≈ on time
15:20≈ on time ≈ on time
15:27≈ on time ≈ on time
15:32≈ on time ≈ on time
15:37on 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 14 NovWierden 15:47Partial coverage+1 min—
Fri 13 NovEnschede Kennispark 16:180 min—
Thu 12 NovEnschede Kennispark 16:180 min—
Wed 11 NovEnschede Kennispark 16:180 min—
Tue 10 NovEnschede Kennispark 16:180 min—
Mon 9 NovEnschede Kennispark 16:180 min—
Sun 8 NovWierden 15:44Partial coverage0 min—
Sat 7 NovWierden 15:48Partial coverage+1 min+2 min
Fri 6 NovEnschede Kennispark 16:18No data—
Thu 5 NovEnschede Kennispark 16:18No data—
Wed 4 NovEnschede Kennispark 16:180 min—
Tue 3 NovEnschede Kennispark 16:19No data—
Mon 2 NovEnschede Kennispark 16:19No data—
Sun 1 NovWierden 15:47Partial coverage0 min—
Sat 31 OctWierden 15:48Partial coverage+1 min+2 min
Fri 30 OctEnschede Kennispark 16:180 min—
Thu 29 OctEnschede Kennispark 16:180 min—
Wed 28 OctEnschede Kennispark 16:180 min—
Tue 27 OctEnschede Kennispark 16:18No data—
Mon 26 OctEnschede Kennispark 16:18No data—
Sun 25 OctWierden 15:50No data—
Sat 24 OctWierden 15:46Partial coverage0 min—
Fri 23 OctEnschede Kennispark 16:19No data—
Thu 22 OctEnschede Kennispark 16:180 min—
Wed 21 OctEnschede Kennispark 16:23No data—
Tue 20 OctEnschede Kennispark 16:18No data—
Mon 19 OctEnschede Kennispark 16:190 min—
Sun 18 OctWierden 15:47+1 min—
Sat 17 OctWierden 15:47No data—
Fri 16 OctEnschede Kennispark 16:18No data—