Train Blauwnet A 31066 Hardenberg – Almelo

Hardenberg 17:16 → Almelo 17:43 Daily 0 h 27 min · 6 stops Blauwnet A

It has not run yet today

Last recorded run: Monday 9 November 0 min

Next service: today 17:16 from Hardenberg · Tue 10 Nov

Next departure 17:16 today · Hardenberg
On-time · 30 days
91%
10/11 runs under 3 min
RT coverage: 4 full · 7 partial · 18 no data
On-time · 90 days
88%
14/16 runs under 3 min
RT coverage: 6 full · 10 partial · 70 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Almelo, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Tue 6 Oct Max en route +5 min · last fix heading to Vriezenveen +5 min
  • Sat 31 Oct Max en route +3 min · last fix heading to Vriezenveen +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 14
  • 3–10 min 13% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 16 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
17:16on time +1 min
17:23 / 17:25≈ +1 min ≈ +1 min
17:30 / 17:31≈ +1 min ≈ +2 min
17:33≈ +1 min ≈ +2 min
17:38≈ +1 min ≈ +2 min
17:43+1 min +3 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

DateLast stopFinalMax
Mon 9 NovVriezenveen 17:52Partial coverage0 min—
Sun 8 NovVriezenveen 17:52+1 min+1 min
Sat 7 NovVriezenveen 17:52+2 min+2 min
Fri 6 NovVriezenveen 17:52No data—
Thu 5 NovVriezenveen 17:52No data—
Wed 4 NovVriezenveen 17:52Partial coverage0 min—
Tue 3 NovVriezenveen 17:52No data—
Mon 2 NovVriezenveen 17:52No data—
Sun 1 NovVriezenveen 17:52No data—
Sat 31 OctVriezenveen 17:52+3 min+3 min
Fri 30 OctVriezenveen 17:52No data—
Thu 29 OctVriezenveen 17:52No data—
Wed 28 OctVriezenveen 17:52Partial coverage0 min—
Tue 27 OctVriezenveen 17:52Partial coverage0 min—
Mon 26 OctVriezenveen 17:52No data—
Sun 25 OctVriezenveen 17:52No data—
Sat 24 OctVriezenveen 17:52No data—
Fri 23 OctVriezenveen 17:52No data—
Thu 22 OctVriezenveen 17:52No data—
Wed 21 OctVriezenveen 17:52No data—
Tue 20 OctVriezenveen 17:52Partial coverage0 min—
Mon 19 OctVriezenveen 17:52Partial coverage0 min—
Sun 18 OctVriezenveen 17:54+1 min+1 min
Sat 17 OctVriezenveen 17:52No data—
Fri 16 OctVriezenveen 17:52No data—
Thu 15 OctVriezenveen 17:52No data—
Wed 14 OctVriezenveen 17:52No data—
Tue 13 OctVriezenveen 17:52No data—
Mon 12 OctVriezenveen 17:52Partial coverage0 min—
Sun 11 OctVriezenveen 17:52+1 min+1 min