Train Blauwnet A 3835 Zwolle – Hardenberg

Zwolle 12:22 → Hardenberg 12:49 Daily 0 h 27 min · 5 stops Blauwnet A

✓ Today’s run finished

Today, last fix heading to Mariënberg at 12:59 0 min

  1. Zwolle12:22
  2. Dalfsen12:29
  3. Ommen12:36
  4. Mariënberg12:44
  5. Hardenberg12:49

Next service: tomorrow 12:22 from Zwolle · Thu 19 Nov

Next departure 12:22 tomorrow · Zwolle
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 14 full · 5 partial · 11 no data
On-time · 90 days
100%
27/27 runs under 3 min
RT coverage: 22 full · 5 partial · 62 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 Hardenberg, 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

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

  • Early 0% · 0
  • On time 100% · 27
  • 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=5
  • 100% W n=5
  • 100% T n=2
  • 100% F n=2
  • 100% S n=5
  • 100% S n=5

Stops and timetable

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

Last 90 days, 27 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
12:22on time on time
12:29 / 12:30≈ on time ≈ on time
12:36 / 12:37≈ on time ≈ on time
12:44≈ on time ≈ on time
12:49on 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
Wed 18 NovMariënberg 12:59Partial coverage0 min—
Tue 17 NovMariënberg 12:59Partial coverage+1 min+1 min
Mon 16 NovMariënberg 12:59Partial coverage0 min—
Sun 15 NovMariënberg 12:59Partial coverage+1 min+1 min
Sat 14 NovMariënberg 12:59Partial coverage+2 min+2 min
Fri 13 NovEmmen Zuid 13:240 min—
Thu 12 NovEmmen Zuid 13:240 min—
Wed 11 NovEmmen Zuid 13:240 min—
Tue 10 NovEmmen Zuid 13:24+1 min—
Mon 9 NovEmmen Zuid 13:240 min—
Sun 8 NovEmmen Zuid 13:240 min—
Sat 7 NovEmmen Zuid 13:240 min—
Fri 6 NovEmmen Zuid 13:24No data—
Thu 5 NovEmmen Zuid 13:24No data—
Wed 4 NovEmmen Zuid 13:240 min—
Tue 3 NovEmmen Zuid 13:25No data—
Mon 2 NovEmmen Zuid 13:24No data—
Sun 1 NovEmmen Zuid 13:260 min—
Sat 31 OctEmmen Zuid 13:250 min—
Fri 30 OctEmmen Zuid 13:25No data—
Thu 29 OctEmmen Zuid 13:25No data—
Wed 28 OctEmmen Zuid 13:270 min—
Tue 27 OctEmmen Zuid 13:250 min—
Mon 26 OctEmmen Zuid 13:25No data—
Sun 25 OctEmmen Zuid 13:25No data—
Sat 24 OctEmmen Zuid 13:250 min—
Fri 23 OctEmmen Zuid 13:25No data—
Thu 22 OctEmmen Zuid 13:25No data—
Wed 21 OctEmmen Zuid 13:25No data—
Tue 20 OctEmmen Zuid 13:250 min—