Train NS 7076 Almelo – Apeldoorn

Almelo 20:23 → Apeldoorn 21: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 0 min

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

Next departure 20:23 today · Almelo
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 13 full · 0 partial · 8 no data
On-time · 90 days
100%
15/15 runs under 3 min
RT coverage: 15 full · 0 partial · 11 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: 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

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

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

On-time by weekday

  • 100% M n=4
  • 100% T n=3
  • 100% W n=3
  • 100% T n=2
  • 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, 15 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
20:23on time on time
20:28≈ on time ≈ on time
20:34≈ on time ≈ on time
20:39≈ on time ≈ +1 min
20:49≈ on time ≈ +1 min
20:54 / 20:55≈ on time ≈ +1 min
21:00≈ on time ≈ +1 min
21:06≈ on time ≈ +1 min
21:10on time +1 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
Wed 4 Nov— 21:120 min—
Tue 3 Nov— 21:10No data—
Mon 2 Nov— 21:090 min—
Fri 30 Oct— 21:11No data—
Thu 29 Oct— 21:110 min—
Wed 28 Oct— 21:110 min—
Tue 27 Oct— 21:120 min—
Mon 26 Oct— 21:14No data—
Fri 23 Oct— 21:12+1 min—
Thu 22 Oct— 21:18No data—
Wed 21 Oct— 21:12No data—
Tue 20 Oct— 21:11No data—
Mon 19 Oct— 21:120 min—
Fri 16 Oct— 20:550 min—
Thu 15 Oct— 20:58No data—
Wed 14 Oct— 20:55No data—
Tue 13 Oct— 21:040 min—
Mon 12 Oct— 20:550 min—
Fri 9 Oct— 21:110 min—
Thu 8 Oct— 21:11+1 min—
Wed 7 Oct— 21:110 min—
Tue 6 Oct— 21:16+2 min+3 min
Mon 5 Oct— 21:110 min—
Fri 21 AugRijssen 20:48No data—
Fri 14 AugHolten 20:53No data—
Wed 12 AugHolten 20:53No data—