Train Blauwnet A 31234 Oldenzaal – Zutphen

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

✓ Today’s run finished

Today, last fix heading to Lochem at 12:57 +2 min

  1. Oldenzaal12:03
  2. Hengelo Oost12:09
  3. Hengelo12:13
  4. Delden12:23
  5. Goor12:30
  6. Lochem12:40
  7. Zutphen12:53

Next service: tomorrow 12:03 from Oldenzaal · Tue 10 Nov

Next departure 12:03 tomorrow · Oldenzaal
On-time · 30 days
89%
8/9 runs under 3 min
RT coverage: 3 full · 6 partial · 16 no data
On-time · 90 days
80%
12/15 runs under 3 min
RT coverage: 4 full · 11 partial · 61 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
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

Worst days

  • Sat 10 Oct Max en route +7 min · last fix heading to Lochem +7 min
  • Mon 5 Oct Max en route +5 min · last fix heading to Lochem +5 min
  • Sat 7 Nov Max en route +4 min · last fix heading to Lochem +4 min

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 80% · 12
  • 3–10 min 20% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=3
  • 100% T n=3
  • 100% W n=3
  • 100% T n=1
  • 100% F n=1
  • 50% S n=4
  • — S n=0

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
12:03on time on time
12:09— —
12:13 / 12:16— —
12:18— —
12:23— —
12:30 / 12:32— —
12:40— —
12: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
Mon 9 NovLochem 12:57Partial coverage+2 min+2 min
Sat 7 NovLochem 12:54+4 min+4 min
Fri 6 NovLochem 12:54No data—
Thu 5 NovLochem 12:54No data—
Wed 4 NovLochem 12:54Partial coverage0 min—
Tue 3 NovLochem 12:54No data—
Mon 2 NovLochem 12:54No data—
Sat 31 OctLochem 12:55+1 min+2 min
Fri 30 OctLochem 12:57No data—
Thu 29 OctHengelo Oost 12:23No data—
Wed 28 OctLochem 12:55Partial coverage0 min—
Tue 27 OctLochem 12:55Partial coverage0 min—
Mon 26 OctLochem 12:55No data—
Sat 24 OctLochem 12:550 min—
Fri 23 OctLochem 12:55No data—
Thu 22 OctLochem 12:58No data—
Wed 21 OctLochem 12:55No data—
Tue 20 OctLochem 12:55Partial coverage0 min—
Mon 19 OctLochem 13:14Partial coverage0 min—
Sat 17 OctLochem 12:54No data—
Fri 16 OctLochem 12:55No data—
Thu 15 OctLochem 12:57No data—
Wed 14 OctLochem 12:54No data—
Tue 13 OctLochem 12:55No data—
Mon 12 OctLochem 12:54No data—
Sat 10 OctLochem 12:54+7 min+7 min
Fri 9 OctLochem 12:55Partial coverage0 min—
Thu 8 OctLochem 12:55Partial coverage+1 min—
Wed 7 OctLochem 12:56Partial coverage+1 min—
Tue 6 OctLochem 12:58Partial coverage+1 min+2 min