Train NS 7048 Almelo – Apeldoorn

Almelo 13:23 → Apeldoorn 14:10 Mon, Tue, Wed, Thu, Fri 0 h 47 min · 9 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November +1 min

Next service: today 13:23 from Almelo · Thu 5 Nov

Next departure 13:23 today · Almelo
On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 2 full · 10 partial · 9 no data
On-time · 90 days
100%
14/14 runs under 3 min
RT coverage: 2 full · 12 partial · 48 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: +1 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

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

  • Early 0% · 0
  • On time 100% · 14
  • 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=4
  • 100% W n=4
  • 100% T n=1
  • 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, 14 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:23on time on time
13:28— —
13:34— —
13:39— —
13:49— —
13:54 / 13:55— —
14:00— —
14:06— —
14:10— —

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
Wed 4 NovApeldoorn Osseveld 14:19Partial coverage+1 min+3 min
Tue 3 NovApeldoorn Osseveld 14:19No data—
Mon 2 NovApeldoorn Osseveld 14:19No data—
Fri 30 OctApeldoorn Osseveld 14:20No data—
Thu 29 OctApeldoorn Osseveld 14:20No data—
Wed 28 OctApeldoorn Osseveld 14:23Partial coverage0 min—
Tue 27 OctApeldoorn Osseveld 14:20Partial coverage0 min—
Mon 26 OctApeldoorn Osseveld 14:20No data—
Fri 23 OctApeldoorn Osseveld 14:20Partial coverage0 min—
Thu 22 OctApeldoorn Osseveld 14:20No data—
Wed 21 OctApeldoorn Osseveld 14:20Partial coverage0 min—
Tue 20 OctApeldoorn Osseveld 14:20Partial coverage0 min—
Mon 19 OctApeldoorn Osseveld 14:20Partial coverage0 min—
Fri 16 OctDeventer Colmschate 14:030 min—
Thu 15 OctDeventer Colmschate 14:03No data—
Wed 14 OctDeventer Colmschate 14:03No data—
Tue 13 OctDeventer Colmschate 14:080 min—
Mon 12 OctDeventer Colmschate 14:03No data—
Fri 9 OctApeldoorn Osseveld 14:21Partial coverage+1 min—
Thu 8 OctApeldoorn Osseveld 14:20Partial coverage0 min—
Wed 7 OctApeldoorn Osseveld 14:20Partial coverage0 min—
Tue 6 OctApeldoorn Osseveld 14:20Partial coverage0 min—
Mon 5 OctApeldoorn Osseveld 14:20Partial coverage0 min—
Fri 2 OctApeldoorn Osseveld 14:20No data—
Thu 1 OctApeldoorn Osseveld 14:22No data—
Wed 30 SeptApeldoorn Osseveld 14:20No data—
Tue 29 SeptApeldoorn Osseveld 14:29No data—
Mon 28 SeptApeldoorn Osseveld 14:20No data—
Fri 25 SeptApeldoorn Osseveld 14:21No data—
Thu 24 SeptApeldoorn Osseveld 14:20No data—