Train NS 7080 Almelo – Apeldoorn

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

✓ Today’s run finished

Today, last fix heading to — at 22:09 0 min

  1. Almelo21:23
  2. Wierden21:28
  3. Holten21:39
  4. Deventer Colmschate21:49
  5. Deventer21:54
  6. Apeldoorn Osseveld22:06
  7. Apeldoorn22:10

Next service: Monday 21:23 from Almelo · Mon 16 Nov

Full trip card
Next departure 21:23 Monday · Almelo
On-time · 30 days
100%
15/15 runs under 3 min
RT coverage: 15 full · 0 partial · 7 no data
On-time · 90 days
100%
21/21 runs under 3 min
RT coverage: 21 full · 0 partial · 9 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: 0 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

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

  • Early 0% · 0
  • On time 100% · 21
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=3
  • 100% W n=5
  • 100% T n=3
  • 100% F n=5
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 21 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
Almelo
21:23on time on time
Wierden
21:28≈ on time ≈ on time
Rijssen
21:34≈ on time ≈ on time
Holten
21:39≈ on time ≈ on time
Deventer Colmschate
21:49≈ on time ≈ on time
Deventer
21:54 / 21:55≈ on time ≈ on time
Twello
22:00≈ on time ≈ on time
Apeldoorn Osseveld
22:06≈ on time ≈ on time
Apeldoorn
22:10on 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
Fri 13 Nov— 22:090 min—
Thu 12 Nov— 22:090 min—
Wed 11 Nov— 22:100 min—
Tue 10 Nov— 22:14+2 min+3 min
Mon 9 Nov— 22:090 min—
Fri 6 Nov— 22:090 min—
Thu 5 Nov— 22:09No data—
Wed 4 Nov— 22:120 min+1 min
Tue 3 Nov— 22:10No data—
Mon 2 Nov— 22:090 min—
Fri 30 Oct— 22:11No data—
Thu 29 Oct— 22:110 min—
Wed 28 Oct— 22:110 min—
Tue 27 Oct— 22:140 min—
Mon 26 Oct— 22:11No data—
Fri 23 Oct— 22:120 min—
Thu 22 Oct— 22:12No data—
Wed 21 Oct— 22:110 min—
Tue 20 Oct— 22:17No data—
Mon 19 Oct— 21:290 min—
Fri 16 Oct— 21:550 min—
Thu 15 Oct— 21:57No data—
Wed 14 Oct— 21:55No data—
Tue 13 Oct— 21:56No data—
Mon 12 Oct— 21:550 min—
Fri 9 Oct— 22:120 min+1 min
Thu 8 Oct— 22:120 min—
Wed 7 Oct— 22:110 min—
Tue 6 Oct— 22:110 min—
Mon 5 Oct— 22:110 min—