Train Blauwnet A 31205 Goor – Oldenzaal

Goor 05:30 → Oldenzaal 05:57 Mon, Tue, Wed, Thu, Fri 0 h 27 min · 6 stops Blauwnet A

It does not run today

Last recorded run: Friday 6 November No data

Next service: tomorrow 05:30 from Goor · Mon 9 Nov

Next departure 05:30 tomorrow · Goor
On-time · 30 days
71%
10/14 runs under 3 min
RT coverage: 0 full · 14 partial · 6 no data
On-time · 90 days
71%
12/17 runs under 3 min
RT coverage: 0 full · 17 partial · 46 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+7min
9 in 10 runs arrive with less than this
30 days: +7 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

  • Fri 30 Oct Max en route +9 min · last fix heading to Hengelo Oost +7 min
  • Tue 20 Oct Max en route +7 min · last fix heading to Hengelo Oost +7 min
  • Wed 7 Oct Max en route +7 min · last fix heading to Hengelo Oost +7 min
  • Mon 19 Oct Max en route +7 min · last fix heading to Hengelo Oost +6 min
  • Thu 5 Nov Max en route +3 min · last fix heading to Hengelo Oost +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 71% · 12
  • 3–10 min 29% · 5
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 50% M n=2
  • 75% T n=4
  • 80% W n=5
  • 67% T n=3
  • 67% F n=3
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 17 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:30on time +1 min
05:37— —
05:40— —
05:44 / 05:47— —
05:50— —
05:57— —

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:09No data—
Thu 5 NovHengelo Oost 06:09Partial coverage+3 min+3 min
Wed 4 NovHengelo Oost 06:07Partial coverage+1 min+1 min
Tue 3 NovHengelo Oost 06:04Partial coverage0 min—
Mon 2 NovHengelo Oost 06:04No data—
Fri 30 OctHengelo Oost 06:13Partial coverage+7 min+9 min
Thu 29 OctHengelo Oost 06:07Partial coverage+1 min+1 min
Wed 28 OctHengelo Oost 06:07Partial coverage0 min—
Tue 27 OctHengelo Oost 06:07No data—
Mon 26 OctHengelo Oost 06:06No data—
Fri 23 OctHengelo Oost 06:06Partial coverage0 min—
Thu 22 OctHengelo Oost 06:06No data—
Wed 21 OctHengelo Oost 06:07Partial coverage0 min—
Tue 20 OctHengelo Oost 06:13Partial coverage+7 min+7 min
Mon 19 OctHengelo Oost 06:13Partial coverage+6 min+7 min
Fri 16 OctHengelo Oost 06:06No data—
Thu 15 OctHengelo Oost 06:08Partial coverage+2 min+2 min
Wed 14 OctHengelo Oost 06:06Partial coverage0 min+1 min
Tue 13 OctHengelo Oost 06:06Partial coverage0 min—
Mon 12 OctHengelo Oost 06:06Partial coverage+1 min+1 min
Fri 9 OctHengelo Oost 06:06Partial coverage0 min—
Thu 8 OctHengelo Oost 06:06No data—
Wed 7 OctHengelo Oost 06:13Partial coverage+7 min+7 min
Tue 6 OctHengelo Oost 06:08Partial coverage+2 min+2 min
Mon 5 OctHengelo Oost 06:07No data—
Fri 2 OctHengelo Oost 06:07No data—
Thu 1 OctHengelo Oost 06:07No data—
Wed 30 SeptHengelo Oost 06:07No data—
Tue 29 SeptHengelo Oost 06:06No data—
Mon 28 SeptHengelo Oost 06:06No data—