Train Blauwnet A 31050 Hardenberg – Almelo

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

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 13:16 from Hardenberg · Fri 6 Nov

Next departure 13:16 today · Hardenberg
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 0 full · 9 partial · 20 no data
On-time · 90 days
90%
9/10 runs under 3 min
RT coverage: 0 full · 10 partial · 77 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 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 +3 min · last fix heading to Vriezenveen +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 9
  • 3–10 min 10% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 75% T n=4
  • 100% W n=1
  • 100% T n=1
  • — F n=0
  • 100% S n=2
  • 100% S n=1

Stops and timetable

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

Last 90 days, 10 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
13:16on time +1 min
13:23 / 13:25— —
13:30 / 13:31— —
13:33— —
13:38— —
13:43— —

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
Thu 5 NovVriezenveen 13:52No data—
Wed 4 NovVriezenveen 13:52No data—
Tue 3 NovVriezenveen 13:52Partial coverage0 min—
Mon 2 NovVriezenveen 13:52No data—
Sun 1 NovVriezenveen 13:53Partial coverage+2 min+2 min
Sat 31 OctVriezenveen 13:52Partial coverage+1 min+1 min
Fri 30 OctVriezenveen 13:53No data—
Thu 29 OctVriezenveen 13:52Partial coverage0 min—
Wed 28 OctVriezenveen 13:52Partial coverage0 min—
Tue 27 OctVriezenveen 13:52Partial coverage0 min—
Mon 26 OctVriezenveen 13:52No data—
Sun 25 OctVriezenveen 13:52No data—
Sat 24 OctVriezenveen 13:52No data—
Fri 23 OctVriezenveen 13:52No data—
Thu 22 OctVriezenveen 13:52No data—
Wed 21 OctVriezenveen 13:52No data—
Tue 20 OctVriezenveen 13:52Partial coverage0 min—
Mon 19 OctVriezenveen 13:52Partial coverage0 min—
Sun 18 OctVriezenveen 13:53No data—
Sat 17 OctVriezenveen 13:52No data—
Fri 16 OctVriezenveen 13:52No data—
Thu 15 OctVriezenveen 13:52No data—
Wed 14 OctVriezenveen 13:52No data—
Tue 13 OctVriezenveen 13:52No data—
Mon 12 OctVriezenveen 13:52No data—
Sun 11 OctVriezenveen 13:52No data—
Sat 10 OctVriezenveen 13:52Partial coverage+1 min+1 min
Fri 9 OctVriezenveen 13:52No data—
Thu 8 OctVriezenveen 13:52No data—
Wed 7 OctVriezenveen 13:52No data—