Train RRReis A 30415 Apeldoorn – Zutphen

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

✓ Today’s run finished

Today, last fix heading to Apeldoorn at 07:28 0 min

  1. Apeldoorn07:12
  2. Zutphen07:25

Next service: Saturday 07:12 from Apeldoorn · Sat 14 Nov

Next departure 07:12 Saturday · Apeldoorn
On-time · 30 days
100%
5/5 runs under 3 min
RT coverage: 0 full · 5 partial · 0 no data
On-time · 90 days
100%
5/5 runs under 3 min
RT coverage: 0 full · 5 partial · 7 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 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

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

  • Early 0% · 0
  • On time 100% · 5
  • 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=5
  • — S n=0

Stops and timetable

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

Last 90 days, 5 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
07:12on time +1 min
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.

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
Sat 7 NovApeldoorn 07:28Partial coverage0 min—
Sat 31 OctApeldoorn 07:27Partial coverage0 min—
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—