Train Blauwnet A 3860 Emmen – Zwolle

Emmen 15:15 → Zwolle 16:08 Daily 0 h 53 min · 9 stops Blauwnet A

✓ Today’s run finished

Today, last fix heading to Dalfsen at 16:14 No data

  1. Emmen15:15
  2. Emmen Zuid15:20
  3. Coevorden15:31
  4. Hardenberg15:40
  5. Mariënberg15:46
  6. Dalfsen16:00
  7. Zwolle16:08

Next service: tomorrow 15:15 from Emmen · Sat 7 Nov

Next departure 15:15 tomorrow · Emmen
On-time · 30 days
93%
13/14 runs under 3 min
RT coverage: 6 full · 8 partial · 16 no data
On-time · 90 days
94%
16/17 runs under 3 min
RT coverage: 6 full · 11 partial · 72 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 11 Oct Max en route +3 min · last fix heading to Dalfsen +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 16
  • 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=3
  • 100% W n=3
  • 100% T n=1
  • 100% F n=1
  • 100% S n=3
  • 67% S n=3

Stops and timetable

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

Last 90 days, 17 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
15:15on time on time
15:20≈ on time ≈ on time
15:23 / 15:24≈ on time ≈ on time
15:31 / 15:32≈ on time ≈ +1 min
15:40≈ on time ≈ +1 min
15:46≈ on time ≈ +2 min
15:52 / 15:53≈ on time ≈ +2 min
16:00≈ +1 min ≈ +2 min
16:08+1 min +3 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
Fri 6 NovDalfsen 16:14No data—
Thu 5 NovDalfsen 16:15No data—
Wed 4 NovDalfsen 16:14Partial coverage+1 min+1 min
Tue 3 NovDalfsen 16:14No data—
Mon 2 NovDalfsen 16:14No data—
Sun 1 NovDalfsen 16:17+2 min+2 min
Sat 31 OctDalfsen 16:150 min—
Fri 30 OctDalfsen 16:15No data—
Thu 29 OctDalfsen 16:15No data—
Wed 28 OctDalfsen 16:14Partial coverage0 min—
Tue 27 OctDalfsen 16:14Partial coverage0 min—
Mon 26 OctDalfsen 16:15No data—
Sun 25 OctDalfsen 16:15No data—
Sat 24 OctDalfsen 16:140 min—
Fri 23 OctDalfsen 16:16No data—
Thu 22 OctDalfsen 16:24No data—
Wed 21 OctDalfsen 16:14No data—
Tue 20 OctDalfsen 16:35Partial coverage0 min—
Mon 19 OctDalfsen 16:16Partial coverage0 min—
Sun 18 OctDalfsen 16:15+1 min—
Sat 17 OctDalfsen 16:15No data—
Fri 16 OctDalfsen 16:16No data—
Thu 15 OctDalfsen 16:14No data—
Wed 14 OctDalfsen 16:27No data—
Tue 13 OctDalfsen 16:15No data—
Mon 12 OctDalfsen 16:15Partial coverage0 min—
Sun 11 OctDalfsen 16:18+3 min+3 min
Sat 10 OctDalfsen 16:150 min—
Fri 9 OctDalfsen 16:15Partial coverage+1 min+1 min
Thu 8 OctDalfsen 16:16Partial coverage+2 min+2 min