Train Blauwnet A 31030 Hardenberg – Almelo

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

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 08:16 from Hardenberg · Sun 8 Nov

Next departure 08:16 today · Hardenberg
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 6 full · 3 partial · 20 no data
On-time · 90 days
100%
13/13 runs under 3 min
RT coverage: 10 full · 3 partial · 74 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: 0 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 13
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=3
  • 100% W n=3
  • 100% T n=1
  • 100% F n=1
  • 100% S n=3
  • 100% S n=1

Stops and timetable

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

Last 90 days, 13 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
08:16on time on time
08:23 / 08:25≈ on time ≈ +1 min
08:30 / 08:31≈ on time ≈ +1 min
08:34≈ on time ≈ +1 min
08:38≈ on time ≈ +1 min
08:43on time +2 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
Sat 7 NovVriezenveen 08:52Partial coverage0 min—
Fri 6 NovVriezenveen 08:52No data—
Thu 5 NovVriezenveen 08:52No data—
Wed 4 NovVriezenveen 08:53+1 min+1 min
Tue 3 NovVriezenveen 08:53No data—
Mon 2 NovVriezenveen 08:52No data—
Sun 1 NovVriezenveen 08:52No data—
Sat 31 OctVriezenveen 08:52Partial coverage0 min—
Fri 30 OctVriezenveen 08:52No data—
Thu 29 OctVriezenveen 08:53No data—
Wed 28 OctVriezenveen 08:520 min—
Tue 27 OctVriezenveen 08:520 min—
Mon 26 OctVriezenveen 08:52No data—
Sun 25 OctVriezenveen 08:52No data—
Sat 24 OctVriezenveen 08:52No data—
Fri 23 OctVriezenveen 08:53No data—
Thu 22 OctVriezenveen 08:52No data—
Wed 21 OctVriezenveen 08:52No data—
Tue 20 OctVriezenveen 08:570 min—
Mon 19 OctVriezenveen 08:520 min—
Sun 18 OctVriezenveen 08:52No data—
Sat 17 OctVriezenveen 08:52No data—
Fri 16 OctVriezenveen 08:52No data—
Thu 15 OctVriezenveen 08:52No data—
Wed 14 OctVriezenveen 08:52No data—
Tue 13 OctVriezenveen 08:52No data—
Mon 12 OctVriezenveen 08:52No data—
Sun 11 OctVriezenveen 08:520 min—
Sat 10 OctVriezenveen 08:52Partial coverage0 min—
Fri 9 OctVriezenveen 08:52+2 min+2 min