Train RRReis A 17856 Zutphen – Apeldoorn

Zutphen 18:36 → Apeldoorn 18:55 Daily 0 h 19 min · 5 stops RRReis A

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 18:36 from Zutphen · Sat 7 Nov

Next departure 18:36 today · Zutphen
On-time · 30 days
100%
15/15 runs under 3 min
RT coverage: 10 full · 5 partial · 13 no data
On-time · 90 days
94%
16/17 runs under 3 min
RT coverage: 12 full · 5 partial · 45 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

Worst days

  • Wed 7 Oct Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 16
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=1
  • 67% W n=3
  • 100% T n=2
  • 100% F n=2
  • 100% S n=2
  • 100% S n=3

Stops and timetable

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

Last 90 days, 17 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
18:36on time on time
18:40≈ on time ≈ on time
18:45 / 18:46≈ on time ≈ on time
18:52≈ on time ≈ +1 min
18:55on 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
Fri 6 NovKlarenbeek 18:59No data—
Thu 5 Nov— 18:58No data—
Wed 4 Nov— 18:590 min—
Mon 2 Nov— 18:580 min—
Sun 1 NovApeldoorn De Maten 19:07+1 min—
Sat 31 OctApeldoorn De Maten 19:060 min—
Fri 30 OctApeldoorn De Maten 19:06No data—
Thu 29 Oct— 18:570 min—
Wed 28 Oct— 18:590 min—
Tue 27 Oct— 19:00No data—
Mon 26 Oct— 18:580 min—
Sun 25 OctApeldoorn De Maten 19:06No data—
Sat 24 OctApeldoorn De Maten 19:08No data—
Fri 23 OctApeldoorn De Maten 19:06Partial coverage0 min—
Thu 22 OctVoorst-Empe 18:58No data—
Wed 21 OctVoorst-Empe 18:57No data—
Tue 20 OctKlarenbeek 18:59Partial coverage0 min—
Mon 19 OctVoorst-Empe 18:59Partial coverage0 min—
Sun 18 OctApeldoorn De Maten 19:070 min—
Sat 17 OctApeldoorn De Maten 19:06No data—
Fri 16 OctApeldoorn De Maten 19:06No data—
Thu 15 Oct— 18:58No data—
Wed 14 OctApeldoorn De Maten 19:06No data—
Tue 13 OctVoorst-Empe 18:50No data—
Mon 12 OctVoorst-Empe 18:57Partial coverage0 min—
Sun 11 OctApeldoorn De Maten 19:060 min—
Sat 10 OctApeldoorn De Maten 19:060 min—
Fri 9 OctZutphen 18:57Partial coverage0 min—
Thu 8 Oct— 18:480 min—
Wed 7 Oct— 19:01+4 min+4 min