Train Blauwnet A 31252 Oldenzaal – Zutphen

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

✓ Today’s run finished

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

  1. Oldenzaal16:33
  2. Hengelo Oost16:39
  3. Hengelo16:43
  4. Delden16:53
  5. Goor17:00
  6. Lochem17:10
  7. Zutphen17:23

Next service: tomorrow 16:33 from Oldenzaal · Sun 8 Nov

Next departure 16:33 tomorrow · Oldenzaal
On-time · 30 days
92%
12/13 runs under 3 min
RT coverage: 1 full · 12 partial · 16 no data
On-time · 90 days
88%
14/16 runs under 3 min
RT coverage: 2 full · 14 partial · 71 no data
Typical delay
0min
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

  • Mon 5 Oct Max en route +9 min · last fix heading to Lochem +9 min
  • Sat 24 Oct Max en route +6 min · last fix heading to Lochem +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 14
  • 3–10 min 13% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 50% M n=2
  • 100% T n=1
  • 100% W n=3
  • 100% T n=1
  • 100% F n=2
  • 75% 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, 16 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
16:33on time on time
16:39— —
16:43 / 16:46— —
16:48— —
16:53— —
17:00 / 17:02— —
17:10— —
17: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
Sat 7 NovLochem 17:24Partial coverage0 min—
Fri 6 NovLochem 17:24Partial coverage0 min—
Thu 5 NovLochem 17:24No data—
Wed 4 NovLochem 17:24Partial coverage0 min—
Tue 3 NovLochem 17:24No data—
Mon 2 NovLochem 17:24No data—
Sun 1 NovLochem 17:25Partial coverage+1 min—
Sat 31 OctLochem 17:25Partial coverage0 min—
Fri 30 OctLochem 17:25No data—
Thu 29 OctLochem 17:24No data—
Wed 28 OctLochem 17:24Partial coverage0 min—
Tue 27 OctLochem 17:24No data—
Mon 26 OctLochem 17:24No data—
Sun 25 OctLochem 17:25No data—
Sat 24 OctLochem 17:25+6 min+6 min
Thu 22 OctLochem 17:25No data—
Wed 21 OctLochem 17:24No data—
Tue 20 OctLochem 17:25Partial coverage0 min—
Mon 19 OctLochem 17:30No data—
Sun 18 OctLochem 17:24Partial coverage0 min—
Sat 17 OctLochem 17:25No data—
Fri 16 OctLochem 17:26No data—
Thu 15 OctLochem 17:24No data—
Wed 14 OctLochem 17:25No data—
Tue 13 OctLochem 17:24No data—
Mon 12 OctLochem 17:24Partial coverage0 min—
Sun 11 OctLochem 17:24Partial coverage0 min—
Sat 10 OctLochem 17:25Partial coverage0 min—
Fri 9 OctLochem 17:24Partial coverage+2 min+2 min
Thu 8 OctLochem 17:24+1 min+1 min