Train Blauwnet A 8026 Emmen – Zwolle

Emmen 06:41 → Zwolle 07:38 Daily 0 h 57 min · 11 stops Blauwnet A

✓ Today’s run finished

Today, last fix heading to Dalfsen at 07:44 No data

  1. Emmen06:41
  2. Nieuw Amsterdam06:49
  3. Dalen06:56
  4. Gramsbergen07:06
  5. Mariënberg07:16
  6. Dalfsen07:30
  7. Zwolle07:38

Next service: tomorrow 06:41 from Emmen · Sat 7 Nov

Full trip card
Next departure 06:41 tomorrow · Emmen
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 5 full · 16 partial · 9 no data
On-time · 90 days
96%
22/23 runs under 3 min
RT coverage: 5 full · 18 partial · 66 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: +2 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

  • Fri 9 Oct Max en route +3 min · last fix heading to Dalfsen +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 22
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=5
  • 100% W n=4
  • 100% T n=4
  • 75% F n=4
  • 100% S n=2
  • 100% S n=1

Stops and timetable

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

Last 90 days, 23 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
Emmen
06:41on time on time
Emmen Zuid
06:44 / 06:46≈ on time ≈ on time
Nieuw Amsterdam
06:49 / 06:51≈ on time ≈ on time
Dalen
06:56≈ on time ≈ on time
Coevorden
07:00≈ on time ≈ on time
Gramsbergen
07:06≈ on time ≈ on time
Hardenberg
07:10≈ on time ≈ on time
Mariënberg
07:16≈ on time ≈ on time
Ommen
07:22 / 07:23≈ on time ≈ on time
Dalfsen
07:30≈ on time ≈ on time
Zwolle
07:38on 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
Fri 6 NovDalfsen 07:44No data—
Thu 5 NovDalfsen 07:49No data—
Wed 4 NovDalfsen 07:44No data—
Tue 3 NovDalfsen 07:44Partial coverage0 min—
Mon 2 NovDalfsen 07:44No data—
Sun 1 NovDalfsen 07:44No data—
Sat 31 OctDalfsen 07:44Partial coverage0 min—
Fri 30 OctDalfsen 07:45Partial coverage0 min—
Thu 29 OctDalfsen 07:45Partial coverage0 min—
Wed 28 OctDalfsen 07:45Partial coverage0 min—
Tue 27 OctDalfsen 07:45Partial coverage0 min—
Mon 26 OctDalfsen 07:47Partial coverage+3 min+3 min
Sun 25 OctDalfsen 07:45No data—
Sat 24 OctDalfsen 07:44No data—
Fri 23 OctDalfsen 07:45Partial coverage+1 min—
Thu 22 OctDalfsen 07:45Partial coverage0 min—
Wed 21 OctDalfsen 07:48Partial coverage0 min—
Tue 20 OctDalfsen 07:46Partial coverage0 min—
Mon 19 OctDalfsen 07:45Partial coverage0 min—
Sun 18 OctDalfsen 07:46Partial coverage+2 min+2 min
Sat 17 OctDalfsen 07:44No data—
Fri 16 OctDalfsen 07:450 min—
Thu 15 OctDalfsen 07:450 min—
Wed 14 OctDalfsen 07:450 min—
Tue 13 OctDalfsen 07:470 min—
Mon 12 OctDalfsen 07:470 min—
Sun 11 OctDalfsen 07:44No data—
Sat 10 OctDalfsen 07:45Partial coverage0 min—
Fri 9 OctDalfsen 07:48Partial coverage+3 min+3 min
Thu 8 OctDalfsen 07:45Partial coverage+1 min—