Train RRReis A 17812 Zutphen – Apeldoorn

Zutphen 07:37 → Apeldoorn 07:55 Daily 0 h 18 min · 5 stops RRReis A

✓ Today’s run finished

Today, last fix heading to Apeldoorn De Maten at 08:05 0 min

  1. Zutphen07:37
  2. Voorst-Empe07:41
  3. Klarenbeek07:46
  4. Apeldoorn De Maten07:52
  5. Apeldoorn07:55

Next service: tomorrow 07:37 from Zutphen · Sun 8 Nov

Full trip card
Next departure 07:37 tomorrow · Zutphen
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 15 full · 5 partial · 10 no data
On-time · 90 days
95%
21/22 runs under 3 min
RT coverage: 17 full · 5 partial · 65 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 4 Nov Max en route +4 min · last fix heading to Apeldoorn De Maten +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 21
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 22 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
Zutphen
07:37on time on time
Voorst-Empe
07:41≈ on time ≈ on time
Klarenbeek
07:46≈ on time ≈ on time
Apeldoorn De Maten
07:52≈ on time ≈ on time
Apeldoorn
07:55on time on time

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 De Maten 08:05Partial coverage0 min—
Fri 6 NovApeldoorn De Maten 08:04No data—
Thu 5 NovApeldoorn De Maten 08:09No data—
Wed 4 NovApeldoorn De Maten 08:08+4 min+4 min
Tue 3 NovApeldoorn De Maten 08:040 min—
Mon 2 NovApeldoorn De Maten 08:040 min—
Sun 1 NovApeldoorn De Maten 08:060 min—
Sat 31 OctApeldoorn De Maten 08:06Partial coverage0 min—
Fri 30 OctApeldoorn De Maten 08:060 min—
Thu 29 OctApeldoorn De Maten 08:060 min—
Wed 28 OctApeldoorn De Maten 08:060 min—
Tue 27 OctApeldoorn De Maten 08:060 min—
Mon 26 OctApeldoorn De Maten 08:060 min—
Sun 25 OctApeldoorn De Maten 08:06No data—
Sat 24 OctApeldoorn De Maten 08:06Partial coverage0 min—
Fri 23 OctApeldoorn De Maten 08:060 min—
Thu 22 OctApeldoorn De Maten 08:07No data—
Wed 21 OctApeldoorn De Maten 08:07No data—
Tue 20 OctApeldoorn De Maten 08:060 min—
Mon 19 OctApeldoorn De Maten 08:060 min—
Sun 18 OctApeldoorn De Maten 08:07+1 min—
Sat 17 OctApeldoorn De Maten 08:06Partial coverage0 min—
Fri 16 OctApeldoorn De Maten 08:06No data—
Thu 15 OctApeldoorn De Maten 08:06No data—
Wed 14 OctApeldoorn De Maten 08:06No data—
Tue 13 OctApeldoorn De Maten 08:07No data—
Mon 12 OctApeldoorn De Maten 08:06No data—
Sun 11 OctApeldoorn De Maten 08:060 min—
Sat 10 OctApeldoorn De Maten 08:06Partial coverage0 min—
Fri 9 OctApeldoorn De Maten 08:060 min—