Train Blauwnet A 31217 Zutphen – Oldenzaal

Zutphen 08:06 → Oldenzaal 08:57 Mon, Tue, Wed, Thu, Fri, Sat 0 h 51 min · 8 stops Blauwnet A

It does not run today

Last recorded run: Saturday 7 November 0 min

Next service: tomorrow 08:06 from Zutphen · Mon 9 Nov

Next departure 08:06 tomorrow · Zutphen
On-time · 30 days
90%
9/10 runs under 3 min
RT coverage: 1 full · 9 partial · 15 no data
On-time · 90 days
93%
13/14 runs under 3 min
RT coverage: 1 full · 13 partial · 62 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 Oldenzaal, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sat 24 Oct Max en route +4 min · last fix heading to Hengelo Gezondheidspark +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 13
  • 3–10 min 7% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 14 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
08:06on time on time
08:21— —
08:29 / 08:30— —
08:37— —
08:40— —
08:44 / 08:47— —
08:50— —
08:57— —

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 NovHengelo Oost 09:04Partial coverage0 min—
Fri 6 NovHengelo Oost 09:07No data—
Thu 5 NovHengelo Oost 09:08No data—
Wed 4 NovHengelo Oost 09:08Partial coverage+1 min+2 min
Tue 3 NovHengelo Oost 09:09No data—
Mon 2 NovHengelo Oost 09:08No data—
Sat 31 OctHengelo Oost 09:06Partial coverage0 min—
Fri 30 OctHengelo Oost 09:07No data—
Thu 29 OctHengelo Oost 09:08No data—
Wed 28 OctHengelo Oost 09:07Partial coverage0 min—
Tue 27 OctHengelo Oost 09:11Partial coverage0 min—
Mon 26 OctHengelo Oost 09:07No data—
Sat 24 OctHengelo Gezondheidspark 08:58+4 min+4 min
Fri 23 OctHengelo Oost 09:06No data—
Thu 22 OctHengelo Oost 09:06No data—
Wed 21 OctHengelo Oost 09:08No data—
Tue 20 OctHengelo Oost 09:11Partial coverage0 min—
Mon 19 OctHengelo Oost 09:09Partial coverage0 min—
Sat 17 OctHengelo Oost 09:06Partial coverage0 min—
Fri 16 OctHengelo Oost 09:06No data—
Thu 15 OctHengelo Oost 09:06No data—
Wed 14 OctHengelo Oost 09:06No data—
Tue 13 OctHengelo Oost 09:06No data—
Mon 12 OctHengelo Oost 09:07No data—
Sat 10 OctHengelo Oost 09:06Partial coverage0 min—
Fri 9 OctHengelo Oost 09:08Partial coverage+1 min+3 min
Thu 8 OctHengelo Oost 09:08Partial coverage+1 min+1 min
Wed 7 OctHengelo Oost 09:07Partial coverage0 min—
Tue 6 OctHengelo Oost 09:07Partial coverage0 min+2 min
Mon 5 OctHengelo Oost 09:04No data—