Train NS 7087 Apeldoorn – Deventer

Apeldoorn 00:20 → Deventer 00:34 Mon, Tue, Wed, Thu 0 h 14 min · 4 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 00:49 +6 min

  1. Apeldoorn00:20
  2. Apeldoorn Osseveld00:23
  3. Twello00:29
  4. Deventer00:34

Next service: tomorrow 00:20 from Apeldoorn · Wed 18 Nov

Next departure 00:20 tomorrow · Apeldoorn
On-time · 30 days
71%
10/14 runs under 3 min
RT coverage: 14 full · 0 partial · 3 no data
On-time · 90 days
76%
13/17 runs under 3 min
RT coverage: 17 full · 0 partial · 3 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+6min
9 in 10 runs arrive with less than this
30 days: +6 min

Last 30 days

Arrival delay at Deventer, 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 +12 min · last fix heading to — +12 min
  • Tue 17 Nov Max en route +8 min · last fix heading to — +6 min
  • Fri 13 Nov Max en route +5 min · last fix heading to — +5 min
  • Fri 30 Oct Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 76% · 13
  • 3–10 min 18% · 3
  • 10–30 min 6% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 17 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
00:20on time +4 min
00:23≈ on time ≈ +4 min
00:29≈ on time ≈ +6 min
00:34on time +6 min

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 Nov— 00:49+6 min+8 min
Fri 13 Nov— 00:44+5 min+5 min
Thu 12 Nov— 00:340 min—
Wed 11 Nov— 00:59+12 min+12 min
Tue 10 Nov— 00:340 min—
Fri 6 Nov— 00:38No data—
Thu 5 Nov— 05:530 min—
Wed 4 Nov— 00:340 min—
Tue 3 Nov— 00:340 min—
Fri 30 Oct— 00:41+3 min+3 min
Thu 29 Oct— 00:450 min—
Wed 28 Oct— 00:350 min—
Tue 27 Oct— 00:490 min—
Fri 23 Oct— 00:42No data—
Thu 22 Oct— 00:35No data—
Wed 21 Oct— 00:360 min—
Tue 20 Oct— 00:360 min—
Thu 8 Oct— 00:42+3 min+3 min
Wed 7 Oct— 00:35+1 min—
Tue 6 Oct— 00:350 min—