Train Blauwnet A 31221 Zutphen – Oldenzaal

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

✓ Today’s run finished

Today, last fix heading to Hengelo Oost at 10:09 +2 min

  1. Zutphen09:06
  2. Lochem09:21
  3. Goor09:29
  4. Hengelo Gezondheidspark09:40
  5. Hengelo09:44
  6. Hengelo Oost09:50
  7. Oldenzaal09:57

Next service: tomorrow 09:06 from Zutphen · Wed 11 Nov

Next departure 09:06 tomorrow · Zutphen
On-time · 30 days
90%
9/10 runs under 3 min
RT coverage: 1 full · 9 partial · 16 no data
On-time · 90 days
86%
12/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
+4min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Fri 9 Oct Max en route +10 min · last fix heading to Hengelo Oost +10 min
  • Mon 9 Nov Max en route +6 min · last fix heading to Hengelo Oost +5 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 86% · 12
  • 3–10 min 7% · 1
  • 10–30 min 7% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 50% M n=2
  • 100% T n=4
  • 100% W n=2
  • 100% T n=2
  • 0% F n=1
  • 100% S n=3
  • — 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
09:06on time on time
09:21— —
09:29 / 09:30— —
09:37— —
09:40— —
09:44 / 09:47— —
09:50— —
09: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
Tue 10 NovHengelo Oost 10:09Partial coverage+2 min+2 min
Mon 9 NovHengelo Oost 10:12Partial coverage+5 min+6 min
Sat 7 NovHengelo Oost 10:04Partial coverage0 min—
Fri 6 NovHengelo Oost 10:04No data—
Thu 5 NovHengelo Oost 10:04No data—
Wed 4 NovHengelo Oost 10:04No data—
Tue 3 NovHengelo Oost 10:09No data—
Mon 2 NovHengelo Oost 10:04No data—
Sat 31 OctHengelo Oost 10:06No data—
Fri 30 OctHengelo Oost 10:06No data—
Thu 29 OctHengelo Oost 10:04Partial coverage0 min—
Wed 28 OctHengelo Oost 10:06Partial coverage0 min—
Tue 27 OctHengelo Oost 10:06Partial coverage0 min—
Mon 26 OctHengelo Oost 10:07No data—
Sat 24 OctHengelo Gezondheidspark 09:55+1 min—
Fri 23 OctHengelo Oost 10:06No data—
Thu 22 OctHengelo Oost 10:07No data—
Wed 21 OctHengelo Oost 10:06No data—
Tue 20 OctHengelo Oost 10:07Partial coverage0 min—
Mon 19 OctHengelo Oost 10:07Partial coverage0 min—
Sat 17 OctHengelo Oost 10:06Partial coverage0 min—
Fri 16 OctHengelo Oost 10:07No data—
Thu 15 OctHengelo Oost 10:06No data—
Wed 14 OctHengelo Oost 10:07No data—
Tue 13 OctHengelo Oost 10:06No data—
Mon 12 OctHengelo Oost 10:07No data—
Sat 10 OctHengelo Oost 10:06No data—
Fri 9 OctHengelo Oost 10:17Partial coverage+10 min+10 min
Thu 8 OctHengelo Oost 10:06Partial coverage0 min—
Wed 7 OctHengelo Oost 10:06Partial coverage0 min—