Train Blauwnet A 8030 Emmen – Zwolle

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

✓ Today’s run finished

Today, last fix heading to Dalfsen at 08:47 No data

  1. Emmen07:41
  2. Nieuw Amsterdam07:49
  3. Dalen07:55
  4. Gramsbergen08:06
  5. Mariënberg08:16
  6. Dalfsen08:30
  7. Zwolle08:38

Next service: tomorrow 07:41 from Emmen · Fri 6 Nov

Full trip card
Next departure 07:41 tomorrow · Emmen
On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 7 full · 11 partial · 12 no data
On-time · 90 days
95%
18/19 runs under 3 min
RT coverage: 7 full · 12 partial · 70 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 19 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
07:41on time on time
Emmen Zuid
07:44 / 07:46≈ on time ≈ on time
Nieuw Amsterdam
07:49 / 07:50≈ on time ≈ on time
Dalen
07:55≈ on time ≈ on time
Coevorden
07:58 / 08:00≈ on time ≈ on time
Gramsbergen
08:06≈ on time ≈ +1 min
Hardenberg
08:10≈ on time ≈ +1 min
Mariënberg
08:16≈ on time ≈ +1 min
Ommen
08:22 / 08:23≈ on time ≈ +1 min
Dalfsen
08:30≈ on time ≈ +1 min
Zwolle
08:38on time +1 min

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
Thu 5 NovDalfsen 08:47No data—
Wed 4 NovDalfsen 08:44Partial coverage0 min—
Tue 3 NovDalfsen 08:44No data—
Mon 2 NovDalfsen 08:44No data—
Sun 1 NovDalfsen 08:45+1 min+1 min
Sat 31 OctDalfsen 08:46+1 min+1 min
Fri 30 OctDalfsen 08:45No data—
Thu 29 OctDalfsen 08:45Partial coverage0 min—
Wed 28 OctDalfsen 08:44Partial coverage0 min—
Tue 27 OctDalfsen 08:46Partial coverage0 min—
Mon 26 OctDalfsen 08:47Partial coverage0 min—
Sun 25 OctDalfsen 08:44No data—
Sat 24 OctDalfsen 08:46+2 min+2 min
Fri 23 OctDalfsen 08:45Partial coverage0 min—
Thu 22 OctDalfsen 08:44No data—
Wed 21 OctDalfsen 08:46No data—
Tue 20 OctDalfsen 08:52Partial coverage0 min—
Mon 19 OctDalfsen 08:45Partial coverage0 min—
Sun 18 OctDalfsen 08:440 min—
Sat 17 OctDalfsen 08:450 min—
Fri 16 OctDalfsen 08:44No data—
Thu 15 OctDalfsen 08:46No data—
Wed 14 OctDalfsen 08:44No data—
Tue 13 OctDalfsen 08:47No data—
Mon 12 OctDalfsen 08:45No data—
Sun 11 OctDalfsen 08:440 min—
Sat 10 OctDalfsen 08:440 min—
Fri 9 OctDalfsen 08:48Partial coverage+3 min+3 min
Thu 8 OctDalfsen 08:44Partial coverage0 min—
Wed 7 OctDalfsen 08:46Partial coverage+2 min+2 min