Train Blauwnet A 31235 Zutphen – Oldenzaal

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

✓ Today’s run finished

Today, last fix heading to Hengelo Oost at 13:34 No data

  1. Zutphen12:36
  2. Lochem12:51
  3. Goor12:59
  4. Hengelo Gezondheidspark13:10
  5. Hengelo13:14
  6. Hengelo Oost13:20
  7. Oldenzaal13:27

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

Next departure 12:36 tomorrow · Zutphen
On-time · 30 days
94%
15/16 runs under 3 min
RT coverage: 4 full · 12 partial · 14 no data
On-time · 90 days
95%
18/19 runs under 3 min
RT coverage: 4 full · 15 partial · 70 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 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

  • Sat 31 Oct Max en route +3 min · last fix heading to Hengelo Oost +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 18
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 19 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:36on time on time
12:51— —
12:59 / 13:00— —
13:07— —
13:10— —
13:14 / 13:17— —
13:20— —
13: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 13:34No data—
Thu 5 NovHengelo Oost 13:37No data—
Wed 4 NovHengelo Oost 13:34Partial coverage0 min—
Tue 3 NovHengelo Oost 13:34Partial coverage0 min—
Mon 2 NovHengelo Oost 13:34Partial coverage0 min—
Sun 1 NovHengelo Oost 13:370 min—
Sat 31 OctHengelo Oost 13:39Partial coverage+3 min+3 min
Fri 30 OctHengelo Oost 13:36No data—
Thu 29 OctHengelo Oost 13:36Partial coverage0 min—
Wed 28 OctHengelo Oost 13:37Partial coverage0 min—
Tue 27 OctHengelo Oost 13:36Partial coverage0 min—
Mon 26 OctHengelo Oost 13:36No data—
Sun 25 OctHengelo Gezondheidspark 13:28No data—
Sat 24 OctHengelo Gezondheidspark 13:240 min—
Fri 23 OctHengelo Oost 13:36No data—
Thu 22 OctHengelo Oost 13:37No data—
Wed 21 OctHengelo Oost 13:36No data—
Tue 20 OctHengelo Oost 13:36Partial coverage0 min—
Mon 19 OctHengelo Oost 13:38Partial coverage0 min—
Sun 18 OctHengelo Oost 13:360 min—
Sat 17 OctHengelo Oost 13:36No data—
Fri 16 OctHengelo Oost 13:36No data—
Thu 15 OctHengelo Oost 13:36No data—
Wed 14 OctHengelo Oost 13:36No data—
Tue 13 OctHengelo Oost 13:37No data—
Mon 12 OctHengelo Oost 13:36No data—
Sun 11 OctHengelo Oost 13:370 min+2 min
Sat 10 OctHengelo Oost 13:40Partial coverage+2 min+3 min
Fri 9 OctHengelo Oost 13:37Partial coverage0 min—
Thu 8 OctHengelo Oost 13:36Partial coverage0 min—