Train RRReis A 30415 Apeldoorn – Zutphen

Apeldoorn 07:12 → Zutphen 07:25 Sat 0 h 13 min · 2 stops RRReis A

It does not run today

Last recorded run: Saturday 24 October 0 min

Next service: tomorrow 07:12 from Apeldoorn · Sat 31 Oct

Next departure 07:12 tomorrow · Apeldoorn
On-time · 30 days
100%
3/3 runs under 3 min
RT coverage: 0 full · 3 partial · 1 no data
On-time · 90 days
100%
3/3 runs under 3 min
RT coverage: 0 full · 3 partial · 8 no data
Typical delay
—
Needs at least 5 runs with data (3 so far)
P90
—
Needs at least 5 runs with data (3 so far)

Last 30 days

Arrival delay at Zutphen, 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

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

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

On-time by weekday

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

Stops and timetable

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

StopSched.
07:12
07:25

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
Sat 24 OctApeldoorn 07:28Partial coverage0 min—
Sat 17 OctApeldoorn 07:29Partial coverage+1 min+2 min
Sat 10 OctApeldoorn 07:28Partial coverage0 min+1 min
Sat 3 OctApeldoorn 07:26No data—
Sat 26 SeptApeldoorn 07:26No data—
Sat 19 SeptApeldoorn 07:26No data—
Sat 5 SeptApeldoorn 07:26No data—
Sat 29 AugApeldoorn 07:26No data—
Sat 22 AugApeldoorn 07:26No data—
Sat 15 AugApeldoorn 07:26No data—
Sat 8 AugApeldoorn 07:27No data—