Train Blauwnet A 31218 Oldenzaal – Zutphen

Oldenzaal 08:03 → Zutphen 08:53 Mon, Tue, Wed, Thu, Fri, Sat 0 h 50 min · 8 stops Blauwnet A

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 08:03 from Oldenzaal · Fri 6 Nov

Next departure 08:03 today · Oldenzaal
On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 4 full · 8 partial · 13 no data
On-time · 90 days
100%
13/13 runs under 3 min
RT coverage: 4 full · 9 partial · 61 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Zutphen, 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

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

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

Stops and timetable

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

Last 90 days, 13 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:03on time on time
08:09— —
08:13 / 08:16— —
08:18— —
08:23— —
08:30 / 08:32— —
08:40— —
08:53— —

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
Thu 5 NovLochem 08:54No data—
Wed 4 NovLochem 08:57Partial coverage+2 min+2 min
Tue 3 NovLochem 08:54No data—
Mon 2 NovLochem 08:58No data—
Sat 31 OctLochem 08:55+3 min+3 min
Fri 30 OctHengelo 08:30Partial coverageNo data—
Thu 29 OctLochem 08:58Partial coverage0 min—
Wed 28 OctLochem 08:56Partial coverage0 min—
Tue 27 OctLochem 08:55Partial coverage0 min—
Mon 26 OctLochem 08:56No data—
Sat 24 OctLochem 08:57+2 min+2 min
Fri 23 OctLochem 08:55No data—
Thu 22 OctLochem 08:55No data—
Wed 21 OctLochem 08:57No data—
Tue 20 OctLochem 08:59Partial coverage0 min—
Mon 19 OctLochem 08:55Partial coverage0 min—
Sat 17 OctLochem 08:540 min—
Fri 16 OctLochem 08:55No data—
Thu 15 OctLochem 08:55No data—
Wed 14 OctLochem 08:55No data—
Tue 13 OctLochem 08:55No data—
Mon 12 OctLochem 08:56No data—
Sat 10 OctLochem 08:540 min—
Fri 9 OctLochem 08:57Partial coverage+1 min+3 min
Thu 8 OctLochem 08:55Partial coverage+1 min—
Tue 6 OctLochem 08:56Partial coverage+1 min+2 min
Mon 5 OctLochem 08:56No data—
Sat 3 OctLochem 08:53No data—
Fri 2 OctLochem 08:55No data—
Thu 1 OctLochem 08:55No data—