Train Blauwnet A 8042 Hardenberg → Zwolle
Blauwnet A 8042 Hardenberg–Zwolle: final delay under 3 min on 21 of its 21 runs with data in the last 30 days (100%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 20:07 (GMT+1).
An alert on this phone or computer when the 8042 is 5 min or more late, every day it runs. No account, no email.
✓ Today’s run finished
Today, last fix heading to Dalfsen at 11:44 0 min
- Hardenberg11:10
- Mariënberg11:16
- Ommen11:22
- Dalfsen11:30
- Zwolle11:38
Next service: tomorrow 11:10 from Hardenberg · Mon 23 Nov
Last 30 days
Arrival delay at Zwolle, 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
28 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 28
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=3
- 100% T n=4
- 100% W n=4
- 100% T n=4
- 100% F n=3
- 100% S n=6
- 100% S n=4
Stops and timetable
Timetable of the latest run from the operator’s GTFS (5 stops).
Last 90 days, 28 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 |
|---|---|---|---|
| 11:10 | on time | on time | |
| 11:16 | ≈ on time | ≈ on time | |
| 11:22 / 11:23 | ≈ on time | ≈ +1 min | |
| 11:30 | ≈ on time | ≈ +1 min | |
| 11:38 | 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 |
|---|---|---|---|
| Sun 22 Nov | Dalfsen 11:44Partial coverage | 0 min | — |
| Sat 21 Nov | Dalfsen 11:44Partial coverage | 0 min | — |
| Fri 20 Nov | Dalfsen 11:44Partial coverage | 0 min | — |
| Thu 19 Nov | Dalfsen 11:44Partial coverage | 0 min | — |
| Wed 18 Nov | Dalfsen 11:44Partial coverage | 0 min | — |
| Tue 17 Nov | Dalfsen 11:44Partial coverage | +1 min | — |
| Mon 16 Nov | Dalfsen 11:44Partial coverage | 0 min | — |
| Sun 15 Nov | Dalfsen 11:45 | 0 min | — |
| Sat 14 Nov | Dalfsen 11:44 | 0 min | — |
| Fri 13 Nov | Dalfsen 11:44 | 0 min | — |
| Thu 12 Nov | Dalfsen 11:44 | 0 min | — |
| Wed 11 Nov | Dalfsen 11:44 | 0 min | — |
| Tue 10 Nov | Dalfsen 11:44 | +1 min | +2 min |
| Mon 9 Nov | Dalfsen 11:44 | 0 min | — |
| Sun 8 Nov | Dalfsen 11:44 | No data | — |
| Sat 7 Nov | Dalfsen 11:44 | +1 min | +1 min |
| Fri 6 Nov | Dalfsen 11:44 | No data | — |
| Thu 5 Nov | Dalfsen 11:44 | No data | — |
| Wed 4 Nov | Dalfsen 11:44 | +2 min | +2 min |
| Tue 3 Nov | Dalfsen 11:44 | No data | — |
| Mon 2 Nov | Dalfsen 11:44 | No data | — |
| Sun 1 Nov | Dalfsen 11:45 | 0 min | — |
| Sat 31 Oct | Dalfsen 11:44 | 0 min | — |
| Fri 30 Oct | Dalfsen 11:45 | No data | — |
| Thu 29 Oct | Dalfsen 11:44 | 0 min | — |
| Wed 28 Oct | Dalfsen 11:45 | 0 min | — |
| Tue 27 Oct | Dalfsen 11:44 | No data | — |
| Mon 26 Oct | Dalfsen 11:44 | No data | — |
| Sun 25 Oct | Dalfsen 11:45 | No data | — |
| Sat 24 Oct | Dalfsen 11:44 | 0 min | — |