Train Blauwnet A 31062 Hardenberg – Almelo

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

✓ Today’s run finished

Today, last fix heading to Vriezenveen at 16:52 +2 min

  1. Hardenberg16:16
  2. Mariënberg16:23
  3. Vroomshoop16:30
  4. Daarlerveen16:33
  5. Vriezenveen16:38
  6. Almelo16:43

Next service: tomorrow 16:16 from Hardenberg · Sun 8 Nov

Next departure 16:16 tomorrow · Hardenberg
On-time · 30 days
100%
10/10 runs under 3 min
RT coverage: 6 full · 4 partial · 20 no data
On-time · 90 days
100%
12/12 runs under 3 min
RT coverage: 8 full · 4 partial · 76 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 12
  • 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=2
  • 100% W n=3
  • — T n=0
  • — F n=0
  • 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, 12 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
16:16on time on time
16:23 / 16:25≈ on time ≈ on time
16:30 / 16:31≈ on time ≈ on time
16:33≈ on time ≈ on time
16:38≈ on time ≈ on time
16:43on time on time

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