Train Blauwnet A 31255 Zutphen – Oldenzaal

Zutphen 17:36 → Oldenzaal 18:27 Daily 0 h 51 min · 8 stops Blauwnet A

It has not run yet today

Last recorded run: Monday 9 November 0 min

Next service: today 17:36 from Zutphen · Tue 10 Nov

Next departure 17:36 today · Zutphen
On-time · 30 days
92%
11/12 runs under 3 min
RT coverage: 1 full · 11 partial · 16 no data
On-time · 90 days
94%
17/18 runs under 3 min
RT coverage: 2 full · 16 partial · 68 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: +2 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

  • Sun 8 Nov Max en route +7 min · last fix heading to Hengelo Oost +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 17
  • 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
  • 100% W n=3
  • 100% T n=1
  • 100% F n=2
  • 100% S n=3
  • 75% S n=4

Stops and timetable

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

Last 90 days, 18 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
17:36on time on time
17:51— —
17:59 / 18:00— —
18:07— —
18:10— —
18:14 / 18:17— —
18:20— —
18:27— —

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
Mon 9 NovHengelo Gezondheidspark 18:24Partial coverage0 min—
Sun 8 NovHengelo Oost 18:43Partial coverage+7 min+7 min
Sat 7 NovHengelo Oost 18:34No data—
Fri 6 NovHengelo Oost 18:34Partial coverage+2 min+2 min
Thu 5 NovHengelo Gezondheidspark 18:24No data—
Wed 4 NovHengelo Gezondheidspark 18:24Partial coverage0 min—
Tue 3 NovHengelo Gezondheidspark 18:24No data—
Mon 2 NovHengelo Gezondheidspark 18:24No data—
Sun 1 NovHengelo Oost 18:37Partial coverage+1 min+1 min
Sat 31 OctHengelo Oost 18:37Partial coverage+1 min+1 min
Fri 30 OctHengelo Oost 18:34No data—
Thu 29 OctGoor 18:14No data—
Wed 28 OctHengelo Gezondheidspark 18:24Partial coverage0 min—
Tue 27 OctGoor 18:14No data—
Mon 26 OctDelden 18:21Partial coverage0 min—
Sun 25 OctHengelo Gezondheidspark 18:27No data—
Sat 24 OctHengelo Gezondheidspark 18:270 min—
Thu 22 OctHengelo Oost 18:34No data—
Wed 21 OctHengelo Oost 18:34No data—
Tue 20 OctHengelo Oost 18:34Partial coverage0 min—
Mon 19 OctHengelo Oost 18:34No data—
Sun 18 OctHengelo Oost 18:36Partial coverage0 min—
Sat 17 OctHengelo Oost 18:36No data—
Fri 16 OctHengelo Oost 18:37No data—
Thu 15 OctHengelo Oost 18:34No data—
Wed 14 OctHengelo Oost 18:34No data—
Tue 13 OctHengelo Oost 18:34No data—
Mon 12 OctHengelo Oost 18:32Partial coverage0 min—
Sun 11 OctHengelo Oost 18:37Partial coverage0 min—
Sat 10 OctHengelo Oost 18:36Partial coverage0 min—