Train Blauwnet A 31251 Zutphen – Oldenzaal

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

✓ Today’s run finished

Today, last fix heading to Hengelo Oost at 17:34 0 min

  1. Zutphen16:36
  2. Lochem16:51
  3. Goor16:59
  4. Hengelo Gezondheidspark17:10
  5. Hengelo17:14
  6. Hengelo Oost17:20
  7. Oldenzaal17:27

Next service: tomorrow 16:36 from Zutphen · Sat 7 Nov

Next departure 16:36 tomorrow · Zutphen
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 1 full · 12 partial · 17 no data
On-time · 90 days
94%
15/16 runs under 3 min
RT coverage: 1 full · 15 partial · 73 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

Worst days

  • Mon 5 Oct Max en route +5 min · last fix heading to Hengelo Oost +3 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 94% · 15
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 50% M n=2
  • 100% T n=3
  • 100% W n=3
  • 100% T n=1
  • 100% F n=2
  • 100% S n=2
  • 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:36on time on time
16:51— —
16:59 / 17:00— —
17:07— —
17:10— —
17:14 / 17:17— —
17:20— —
17: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
Fri 6 NovHengelo Oost 17:34Partial coverage0 min—
Thu 5 NovHengelo Oost 17:34No data—
Wed 4 NovHengelo Oost 17:34Partial coverage0 min—
Tue 3 NovHengelo Oost 17:34No data—
Mon 2 NovHengelo Oost 17:34No data—
Sun 1 NovHengelo Oost 17:37Partial coverage0 min—
Sat 31 OctHengelo Oost 17:37Partial coverage0 min—
Fri 30 OctHengelo Oost 17:37No data—
Thu 29 OctHengelo Oost 17:33No data—
Wed 28 OctHengelo Oost 17:34Partial coverage0 min—
Tue 27 OctHengelo Oost 17:34Partial coverage0 min—
Mon 26 OctHengelo Oost 17:34No data—
Sun 25 OctHengelo Gezondheidspark 17:25No data—
Sat 24 OctHengelo Gezondheidspark 17:250 min—
Fri 23 OctHengelo Oost 17:40No data—
Thu 22 OctHengelo Oost 17:35No data—
Wed 21 OctHengelo Oost 17:34No data—
Tue 20 OctHengelo Oost 17:35Partial coverage0 min—
Mon 19 OctHengelo Oost 17:34No data—
Sun 18 OctHengelo Oost 17:40Partial coverage0 min—
Sat 17 OctHengelo Oost 17:36No data—
Fri 16 OctHengelo Oost 17:37No data—
Thu 15 OctHengelo Oost 17:34No data—
Wed 14 OctHengelo Oost 17:36No data—
Tue 13 OctHengelo Oost 17:34No data—
Mon 12 OctHengelo Oost 17:34Partial coverage0 min—
Sun 11 OctHengelo Oost 17:43Partial coverage0 min—
Sat 10 OctHengelo Oost 17:36No data—
Fri 9 OctHengelo Oost 17:34Partial coverage0 min—
Thu 8 OctHengelo Oost 17:34Partial coverage0 min—