Train Blauwnet A 31216 Oldenzaal – Zutphen

Oldenzaal 07:33 → Zutphen 08:23 Daily 0 h 50 min · 8 stops Blauwnet A

✓ Today’s run finished

Today, last fix heading to Lochem at 08:24 0 min

  1. Oldenzaal07:33
  2. Hengelo Oost07:39
  3. Hengelo07:43
  4. Delden07:53
  5. Goor08:00
  6. Lochem08:10
  7. Zutphen08:23

Next service: tomorrow 07:33 from Oldenzaal · Mon 9 Nov

Next departure 07:33 tomorrow · Oldenzaal
On-time · 30 days
94%
16/17 runs under 3 min
RT coverage: 1 full · 16 partial · 13 no data
On-time · 90 days
90%
19/21 runs under 3 min
RT coverage: 1 full · 20 partial · 68 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: +1 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

Worst days

  • Fri 9 Oct Max en route +5 min · last fix heading to Lochem +4 min
  • Wed 4 Nov Max en route +4 min · last fix heading to Lochem +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 19
  • 3–10 min 10% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 21 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
07:33on time on time
07:39— —
07:43 / 07:46— —
07:48— —
07:53— —
08:00 / 08:02— —
08:10— —
08:23— —

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
Sun 8 NovLochem 08:24Partial coverage0 min—
Sat 7 NovLochem 08:24Partial coverage+2 min+2 min
Fri 6 NovLochem 08:24No data—
Thu 5 NovLochem 08:28No data—
Wed 4 NovLochem 08:24Partial coverage+4 min+4 min
Tue 3 NovLochem 08:24Partial coverage0 min—
Mon 2 NovLochem 08:24No data—
Sun 1 NovLochem 08:24No data—
Sat 31 OctLochem 08:24No data—
Fri 30 OctLochem 08:25Partial coverage0 min—
Thu 29 OctLochem 08:25Partial coverage0 min—
Wed 28 OctLochem 08:25Partial coverage0 min—
Tue 27 OctLochem 08:26Partial coverage0 min—
Mon 26 OctLochem 08:25Partial coverage0 min—
Sun 25 OctLochem 08:24No data—
Sat 24 OctLochem 08:25+1 min—
Fri 23 OctLochem 08:26Partial coverage+1 min—
Thu 22 OctLochem 08:26No data—
Wed 21 OctLochem 08:25No data—
Tue 20 OctLochem 08:32Partial coverage0 min—
Mon 19 OctLochem 08:27No data—
Sun 18 OctLochem 08:25Partial coverage0 min—
Sat 17 OctLochem 08:26Partial coverage0 min—
Fri 16 OctLochem 08:25No data—
Thu 15 OctLochem 08:26No data—
Wed 14 OctLochem 08:25No data—
Tue 13 OctLochem 08:26No data—
Mon 12 OctLochem 08:25Partial coverage0 min—
Sun 11 OctLochem 08:25Partial coverage0 min—
Sat 10 OctLochem 08:25Partial coverage0 min—