Train Blauwnet A 31209 Goor → Oldenzaal
Blauwnet A 31209 Goor–Oldenzaal: final delay under 3 min on 21 of its 22 runs with data in the last 30 days (95%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 21:48 (GMT+1).
An alert on this phone or computer when the 31209 is 5 min or more late, every day it runs. No account, no email.
It does not run today
Last recorded run: Saturday 21 November 0 min
Next service: tomorrow 06:30 from Goor · Mon 23 Nov
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 19 Oct Max en route +5 min · last fix heading to Hengelo Oost +5 min
- Sat 14 Nov Max en route +5 min · last fix heading to Hengelo Oost +5 min
Distribution · 90 days
36 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 94% · 34
- 3–10 min 6% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 83% M n=6
- 100% T n=6
- 100% W n=7
- 100% T n=6
- 100% F n=4
- 86% S n=7
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (6 stops).
Last 90 days, 36 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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 06:30 | on time | on time | |
| 06:37 | ≈ on time | ≈ +1 min | |
| 06:40 | ≈ on time | ≈ +1 min | |
| 06:44 / 06:47 | ≈ on time | ≈ +1 min | |
| 06:50 | ≈ on time | ≈ +1 min | |
| 06:57 | on time | +1 min |
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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sat 21 Nov | Hengelo Oost 07:04Partial coverage | 0 min | — |
| Fri 20 Nov | Hengelo Oost 07:09 | +3 min | +3 min |
| Thu 19 Nov | Hengelo Oost 07:07 | +1 min | +1 min |
| Wed 18 Nov | Hengelo Oost 07:04 | +1 min | +1 min |
| Tue 17 Nov | Hengelo Oost 07:04 | 0 min | — |
| Mon 16 Nov | Hengelo Oost 07:08 | +2 min | +2 min |
| Sat 14 Nov | Hengelo Oost 07:04Partial coverage | +5 min | +5 min |
| Thu 12 Nov | Hengelo Oost 07:04 | 0 min | — |
| Wed 11 Nov | Hengelo Oost 07:07 | +1 min | +3 min |
| Tue 10 Nov | Hengelo Oost 07:07 | 0 min | — |
| Mon 9 Nov | Hengelo Oost 07:04 | 0 min | — |
| Sat 7 Nov | Hengelo Oost 07:08Partial coverage | +1 min | +2 min |
| Fri 6 Nov | Hengelo Oost 07:07 | No data | — |
| Thu 5 Nov | Hengelo Oost 07:09 | 0 min | — |
| Wed 4 Nov | Hengelo Oost 07:04 | 0 min | +1 min |
| Tue 3 Nov | Hengelo Oost 07:07 | 0 min | — |
| Mon 2 Nov | Hengelo Oost 07:07 | 0 min | — |
| Sat 31 Oct | Hengelo Oost 07:06Partial coverage | 0 min | — |
| Fri 30 Oct | Hengelo Oost 07:04 | 0 min | — |
| Thu 29 Oct | Hengelo Oost 07:07 | 0 min | +1 min |
| Wed 28 Oct | Hengelo Oost 07:06 | 0 min | — |
| Tue 27 Oct | Hengelo Oost 07:04 | No data | — |
| Mon 26 Oct | Hengelo Oost 07:07 | +1 min | +1 min |
| Sat 24 Oct | Hengelo Gezondheidspark 06:56 | +1 min | +2 min |
| Fri 23 Oct | Hengelo Oost 07:07 | +1 min | +1 min |
| Thu 22 Oct | Hengelo Oost 07:06 | No data | — |
| Wed 21 Oct | Hengelo Oost 07:07 | +1 min | +1 min |
| Tue 20 Oct | Hengelo Oost 07:07 | 0 min | +2 min |
| Mon 19 Oct | Hengelo Oost 07:10 | +5 min | +5 min |
| Sat 17 Oct | Hengelo Oost 07:06Partial coverage | 0 min | — |