Train NS 7083 Apeldoorn – Almelo

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

It has not run yet today

Last recorded run: Thursday 12 November 0 min

Next service: today 23:20 from Apeldoorn · Fri 13 Nov

Full trip card
Next departure 23:20 today · Apeldoorn
On-time · 30 days
88%
15/17 runs under 3 min
RT coverage: 17 full · 0 partial · 2 no data
On-time · 90 days
83%
20/24 runs under 3 min
RT coverage: 24 full · 0 partial · 3 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: +2 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 12 Oct Max en route +14 min · last fix heading to — +14 min
  • Mon 9 Nov Max en route +6 min · last fix heading to — +6 min
  • Wed 7 Oct Max en route +4 min · last fix heading to — +4 min
  • Mon 19 Oct Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 83% · 20
  • 3–10 min 13% · 3
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 24 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
Apeldoorn
23:20on time on time
Apeldoorn Osseveld
23:23≈ on time ≈ on time
Twello
23:29≈ on time ≈ +1 min
Deventer
23:34 / 23:36≈ on time ≈ +2 min
Deventer Colmschate
23:41≈ on time ≈ +2 min
Holten
23:50≈ on time ≈ +3 min
Rijssen
23:56≈ on time ≈ +3 min
Wierden
00:02≈ on time ≈ +3 min
Almelo
00:06on time +4 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
Thu 12 Nov— 00:090 min+2 min
Wed 11 Nov— 00:09+1 min+1 min
Tue 10 Nov— 00:040 min+6 min
Mon 9 Nov— 00:17+6 min+6 min
Fri 6 Nov— 00:09+1 min+1 min
Thu 5 Nov— 00:07No data—
Wed 4 Nov— 00:080 min—
Tue 3 Nov— 00:080 min—
Fri 30 Oct— 00:07No data—
Wed 28 Oct— 00:070 min—
Tue 27 Oct— 00:070 min—
Mon 26 Oct— 00:130 min—
Fri 23 Oct— 00:080 min—
Thu 22 Oct— 00:070 min—
Wed 21 Oct— 00:070 min—
Tue 20 Oct— 00:130 min—
Mon 19 Oct— 00:12+3 min+3 min
Fri 16 Oct— 00:070 min—
Thu 15 Oct— 00:070 min—
Wed 14 Oct— 00:070 min—
Tue 13 Oct— 00:08No data—
Mon 12 Oct— 00:35+14 min+14 min
Fri 9 Oct— 00:070 min—
Thu 8 Oct— 00:080 min—
Wed 7 Oct— 00:12+4 min+4 min
Tue 6 Oct— 00:070 min—
Mon 5 Oct— 00:070 min—