Train Blauwnet A 13824 Emmen – Zwolle

Emmen 06:33 → Zwolle 07:23 Mon, Tue, Wed, Thu, Fri 0 h 50 min · 7 stops Blauwnet A

Running now · updated 07:14

Heading to Zwolle No data

Estimated arrival at Zwolle 07:23 · 97 km/h

  1. Emmen06:33
  2. Emmen Zuid06:37
  3. Coevorden06:47
  4. Hardenberg06:56
  5. Ommen07:06
  6. Dalfsen07:15
  7. Zwolle07:23
On-time · 30 days
100%
14/14 runs under 3 min
RT coverage: 0 full · 14 partial · 3 no data
On-time · 90 days
94%
15/16 runs under 3 min
RT coverage: 0 full · 16 partial · 38 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 Zwolle, in minutes. One bar per run.

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

Worst days

  • Wed 7 Oct Max en route +4 min · last fix heading to Dalfsen +4 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 94% · 15
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (7 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 10Today
06:33on time on time
06:37— —
06:47— —
06:56— —
07:06 / 07:08— —
07:15— —
07:23— —

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
Fri 6 NovOmmen 07:09No data—
Thu 5 NovDalfsen 07:33No data—
Wed 4 NovDalfsen 07:29Partial coverage0 min—
Tue 3 NovDalfsen 07:29Partial coverage0 min—
Mon 2 NovDalfsen 07:29Partial coverage0 min—
Fri 30 OctDalfsen 07:29Partial coverageNo data—
Thu 29 OctDalfsen 07:30Partial coverage+1 min+2 min
Wed 28 OctDalfsen 07:31Partial coverage+1 min—
Tue 27 OctDalfsen 07:29Partial coverage0 min—
Mon 26 OctDalfsen 07:31Partial coverage+2 min+2 min
Fri 23 OctDalfsen 07:29Partial coverage0 min—
Thu 22 OctDalfsen 07:29Partial coverage0 min—
Wed 21 OctDalfsen 07:29Partial coverage0 min—
Tue 20 OctDalfsen 07:30Partial coverage0 min—
Mon 19 OctDalfsen 07:29Partial coverage0 min—
Fri 9 OctDalfsen 07:30Partial coverage0 min+1 min
Thu 8 OctDalfsen 07:31Partial coverage+1 min+1 min
Wed 7 OctDalfsen 07:33Partial coverage+4 min+4 min
Tue 6 OctDalfsen 07:30Partial coverage0 min—
Mon 5 OctDalfsen 07:30No data—
Fri 2 OctDalfsen 07:29No data—
Thu 1 OctDalfsen 07:29No data—
Wed 30 SeptDalfsen 07:29No data—
Tue 29 SeptDalfsen 07:33No data—
Mon 28 SeptDalfsen 07:29No data—
Fri 25 SeptDalfsen 07:29No data—
Thu 24 SeptDalfsen 07:29No data—
Wed 23 SeptDalfsen 07:29No data—
Tue 22 SeptDalfsen 07:30No data—
Mon 21 SeptDalfsen 07:29No data—