Train Blauwnet A 8074 Emmen – Zwolle

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

✓ Today’s run finished

Today, last fix heading to Dalfsen at 19:44 +2 min

  1. Emmen18:41
  2. Nieuw Amsterdam18:49
  3. Dalen18:55
  4. Gramsbergen19:06
  5. Mariënberg19:16
  6. Dalfsen19:30
  7. Zwolle19:38

Next service: tomorrow 18:41 from Emmen · Sun 8 Nov

Next departure 18:41 tomorrow · Emmen
On-time · 30 days
94%
16/17 runs under 3 min
RT coverage: 11 full · 6 partial · 12 no data
On-time · 90 days
95%
20/21 runs under 3 min
RT coverage: 15 full · 6 partial · 46 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

  • Sun 18 Oct Max en route +4 min · last fix heading to Dalfsen +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 20
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=3
  • 100% W n=2
  • 100% T n=3
  • 100% F n=3
  • 100% S n=3
  • 67% S n=3

Stops and timetable

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

Last 90 days, 21 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
18:41on time on time
18:44 / 18:46≈ on time ≈ on time
18:49 / 18:50≈ on time ≈ on time
18:55≈ on time ≈ on time
18:58 / 19:00≈ on time ≈ on time
19:06≈ on time ≈ on time
19:10≈ on time ≈ on time
19:16≈ on time ≈ on time
19:22 / 19:23≈ on time ≈ on time
19:30≈ on time ≈ on time
19: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
Sat 7 NovDalfsen 19:44Partial coverage+2 min+2 min
Fri 6 NovEmmen Zuid 19:540 min—
Thu 5 Nov— 19:390 min—
Wed 4 Nov— 19:39No data—
Mon 2 Nov— 19:390 min—
Sun 1 NovDalfsen 19:47Partial coverage+2 min+2 min
Sat 31 OctDalfsen 19:44Partial coverage0 min—
Fri 30 OctNieuw Amsterdam 19:41No data—
Thu 29 Oct— 19:410 min—
Wed 28 Oct— 19:400 min—
Tue 27 Oct— 19:440 min—
Mon 26 Oct— 19:44No data—
Sun 25 OctDalfsen 19:45No data—
Sat 24 OctDalfsen 19:45No data—
Fri 23 OctOmmen 19:42+2 min+2 min
Thu 22 OctEmmen 18:55No data—
Wed 21 Oct— 19:43No data—
Tue 20 OctEmmen Zuid 19:410 min—
Mon 19 OctEmmen 19:420 min—
Sun 18 OctDalfsen 19:47Partial coverage+4 min+4 min
Sat 17 OctDalfsen 19:45No data—
Fri 16 OctDalfsen 19:44No data—
Thu 15 Oct— 19:41No data—
Wed 14 OctDalfsen 19:42No data—
Tue 13 Oct— 19:43No data—
Mon 12 OctEmmen 19:410 min—
Sun 11 OctDalfsen 19:46Partial coverage+1 min—
Sat 10 OctDalfsen 19:46Partial coverage+1 min—
Fri 9 Oct— 19:400 min—
Thu 8 Oct— 19:420 min—