Train Blauwnet A 3811 Zwolle – Emmen

Zwolle 06:22 → Emmen 07:19 Mon, Tue, Wed, Thu, Fri 0 h 57 min · 9 stops Blauwnet A

✓ Today’s run finished

Today, last fix heading to Emmen Zuid at 07:29 No data

  1. Zwolle06:22
  2. Dalfsen06:29
  3. Mariënberg06:44
  4. Hardenberg06:49
  5. Coevorden06:58
  6. Emmen Zuid07:15
  7. Emmen07:19

Next service: Monday 06:22 from Zwolle · Mon 9 Nov

Next departure 06:22 Monday · Zwolle
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 5 full · 15 partial · 2 no data
On-time · 90 days
95%
21/22 runs under 3 min
RT coverage: 5 full · 17 partial · 42 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 Emmen, in minutes. One bar per run.

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

Worst days

  • Thu 29 Oct Max en route +9 min · last fix heading to Emmen Zuid +9 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 21
  • 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=5
  • 100% W n=5
  • 75% T n=4
  • 100% F n=4
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 22 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
06:22on time on time
06:29 / 06:30≈ on time ≈ on time
06:36 / 06:37≈ on time ≈ on time
06:44≈ on time ≈ on time
06:49≈ on time ≈ on time
06:58 / 07:00≈ on time ≈ on time
07:07 / 07:11≈ on time ≈ on time
07:15≈ on time ≈ on time
07:19on 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 NovEmmen Zuid 07:29No data—
Thu 5 NovEmmen Zuid 07:29No data—
Wed 4 NovEmmen Zuid 07:29Partial coverage+1 min+1 min
Tue 3 NovEmmen Zuid 07:29Partial coverage0 min—
Mon 2 NovEmmen Zuid 07:29Partial coverage0 min—
Fri 30 OctEmmen Zuid 07:30Partial coverage+1 min+1 min
Thu 29 OctEmmen Zuid 07:37Partial coverage+9 min+9 min
Wed 28 OctEmmen Zuid 07:29Partial coverage0 min—
Tue 27 OctEmmen Zuid 07:29Partial coverage0 min—
Mon 26 OctEmmen Zuid 07:29Partial coverage+1 min+1 min
Fri 23 OctEmmen Zuid 07:30Partial coverage+1 min+1 min
Thu 22 OctEmmen Zuid 07:29Partial coverage0 min—
Wed 21 OctEmmen Zuid 07:29Partial coverage0 min—
Tue 20 OctEmmen Zuid 07:29Partial coverage0 min—
Mon 19 OctEmmen Zuid 07:29Partial coverage0 min—
Fri 16 OctEmmen Zuid 07:290 min—
Thu 15 OctEmmen Zuid 07:290 min—
Wed 14 OctEmmen Zuid 07:290 min—
Tue 13 OctEmmen Zuid 07:300 min—
Mon 12 OctEmmen Zuid 07:290 min—
Fri 9 OctEmmen Zuid 07:29Partial coverage0 min—
Thu 8 OctEmmen Zuid 07:29Partial coverage0 min—
Wed 7 OctEmmen Zuid 07:30Partial coverage+2 min+2 min
Tue 6 OctEmmen Zuid 07:29Partial coverage0 min—
Mon 5 OctEmmen Zuid 07:30No data—
Fri 2 OctEmmen Zuid 07:29No data—
Thu 1 OctEmmen Zuid 07:29No data—
Wed 30 SeptEmmen Zuid 07:29No data—
Tue 29 SeptEmmen Zuid 07:29No data—
Mon 28 SeptEmmen Zuid 07:29No data—