Train Blauwnet A 31207 Zutphen – Oldenzaal

Zutphen 05:39 → Oldenzaal 06:27 Mon, Tue, Wed, Thu, Fri 0 h 48 min · 8 stops Blauwnet A

✓ Today’s run finished

Today, last fix heading to Hengelo Oost at 06:37 No data

  1. Zutphen05:39
  2. Lochem05:50
  3. Goor05:59
  4. Hengelo Gezondheidspark06:10
  5. Hengelo06:14
  6. Hengelo Oost06:20
  7. Oldenzaal06:27

Next service: Monday 05:39 from Zutphen · Mon 9 Nov

Next departure 05:39 Monday · Zutphen
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 0 full · 21 partial · 1 no data
On-time · 90 days
100%
23/23 runs under 3 min
RT coverage: 0 full · 23 partial · 41 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 23
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=5
  • 100% W n=5
  • 100% T n=5
  • 100% F n=4
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 23 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
05:39on time on time
05:50— —
05:59 / 06:00— —
06:07— —
06:10— —
06:14 / 06:17— —
06:20— —
06: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 06:37No data—
Thu 5 NovHengelo Oost 06:34Partial coverage0 min—
Wed 4 NovHengelo Oost 06:34Partial coverage0 min—
Tue 3 NovHengelo Oost 06:34Partial coverage0 min+1 min
Mon 2 NovHengelo Oost 06:34Partial coverage0 min—
Fri 30 OctHengelo Oost 06:37Partial coverage0 min—
Thu 29 OctHengelo Oost 06:36Partial coverage0 min—
Wed 28 OctHengelo Oost 06:36Partial coverage0 min—
Tue 27 OctHengelo Oost 06:37Partial coverage0 min—
Mon 26 OctHengelo Oost 06:37Partial coverage0 min—
Fri 23 OctHengelo Oost 06:37Partial coverage0 min—
Thu 22 OctHengelo Oost 06:36Partial coverage0 min—
Wed 21 OctHengelo Oost 06:36Partial coverage0 min—
Tue 20 OctHengelo Oost 06:39Partial coverage+2 min+4 min
Mon 19 OctHengelo Oost 06:38Partial coverage+1 min+4 min
Fri 16 OctHengelo Oost 06:37Partial coverage0 min—
Thu 15 OctHengelo Oost 06:37Partial coverage0 min—
Wed 14 OctHengelo Oost 06:36Partial coverage0 min—
Tue 13 OctHengelo Oost 06:36Partial coverage0 min—
Mon 12 OctHengelo Oost 06:36Partial coverage0 min—
Fri 9 OctHengelo Oost 06:36Partial coverage0 min—
Thu 8 OctHengelo Oost 06:37Partial coverage0 min—
Wed 7 OctHengelo Oost 06:36Partial coverage0 min—
Tue 6 OctHengelo Oost 06:36Partial coverage0 min—
Mon 5 OctHengelo Oost 06:38No data—
Fri 2 OctHengelo Oost 06:36No data—
Thu 1 OctHengelo Oost 06:36No data—
Wed 30 SeptHengelo Oost 06:36No data—
Tue 29 SeptHengelo Oost 06:37No data—
Mon 28 SeptHengelo Oost 06:36No data—