Train Blauwnet A 31219 Zutphen – Oldenzaal

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

It has not run yet today

Last recorded run: Monday 9 November No data

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

Next departure 08:36 today · Zutphen
On-time · 30 days
100%
10/10 runs under 3 min
RT coverage: 3 full · 7 partial · 19 no data
On-time · 90 days
100%
15/15 runs under 3 min
RT coverage: 4 full · 11 partial · 73 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 15
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 15 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:36on time on time
08:51— —
08:59 / 09:00— —
09:07— —
09:10— —
09:14 / 09:17— —
09:20— —
09: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 Oost 09:34Partial coverageNo data—
Sun 8 NovHengelo Oost 09:38+1 min—
Sat 7 NovHengelo Oost 09:34No data—
Fri 6 NovHengelo Oost 09:34No data—
Thu 5 NovHengelo Oost 09:37No data—
Wed 4 NovHengelo Oost 09:37Partial coverage0 min+1 min
Tue 3 NovHengelo Oost 09:37No data—
Mon 2 NovHengelo Oost 09:38No data—
Sun 1 NovHengelo Oost 09:37No data—
Sat 31 OctHengelo Oost 09:36Partial coverage0 min—
Fri 30 OctHengelo Oost 09:36No data—
Thu 29 OctHengelo Oost 09:37Partial coverage0 min—
Wed 28 OctHengelo Oost 09:37Partial coverage0 min—
Tue 27 OctHengelo Oost 09:36No data—
Mon 26 OctHengelo Oost 09:36No data—
Sun 25 OctHengelo Gezondheidspark 09:26No data—
Sat 24 OctHengelo Gezondheidspark 09:26+1 min+2 min
Fri 23 OctHengelo Oost 09:36No data—
Thu 22 OctHengelo Oost 09:36No data—
Wed 21 OctHengelo Oost 09:36No data—
Tue 20 OctHengelo Oost 09:38Partial coverage0 min—
Mon 19 OctHengelo Oost 09:36Partial coverage0 min—
Sun 18 OctHengelo Oost 09:38+1 min+3 min
Sat 17 OctHengelo Oost 09:37Partial coverage0 min—
Fri 16 OctHengelo Oost 09:37No data—
Thu 15 OctHengelo Oost 09:36No data—
Wed 14 OctHengelo Oost 09:37No data—
Tue 13 OctHengelo Oost 09:36No data—
Mon 12 OctHengelo Oost 09:38No data—
Sun 11 OctHengelo Oost 09:360 min—