Train NS 7076 Almelo – Deventer

Almelo 20:23 → Deventer 20:54 Mon, Tue, Wed, Thu, Fri 0 h 31 min · 6 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Friday 16 October 0 min

Next service: Monday 20:23 from Almelo · Mon 19 Oct

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 8
  • 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=2
  • 100% W n=1
  • 100% T n=1
  • 100% F n=2
  • — S n=0
  • — S n=0

Stops and timetable

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

StopSched.
20:23
20:28
20:34
20:39
20:49
20:54

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.

Recent runs

DateLast stopFinalMax
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—
Fri 7 AugApeldoorn Osseveld 21:20No data—
Fri 31 JulRijssen 20:48No data—
Wed 29 JulRijssen 20:48No data—