Train Blauwnet A 8038 Emmen – Zwolle

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

✓ Today’s run finished

Today, last fix heading to Dalfsen at 10:44 0 min

  1. Emmen09:41
  2. Nieuw Amsterdam09:49
  3. Dalen09:55
  4. Gramsbergen10:06
  5. Mariënberg10:16
  6. Dalfsen10:30
  7. Zwolle10:38

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

Next departure 09:41 tomorrow · Emmen
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 6 full · 7 partial · 17 no data
On-time · 90 days
100%
16/16 runs under 3 min
RT coverage: 9 full · 7 partial · 73 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 Zwolle, in minutes. One bar per run.

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 16
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 16 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
09:41on time on time
09:44 / 09:46≈ on time ≈ on time
09:49 / 09:50≈ on time ≈ on time
09:55≈ on time ≈ on time
09:58 / 10:00≈ on time ≈ on time
10:06≈ on time ≈ on time
10:10≈ on time ≈ on time
10:16≈ on time ≈ on time
10:22 / 10:23≈ on time ≈ on time
10:30≈ on time ≈ on time
10: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 10:44Partial coverage0 min—
Fri 6 NovDalfsen 10:48No data—
Thu 5 NovDalfsen 10:44No data—
Wed 4 NovDalfsen 10:440 min—
Tue 3 NovDalfsen 10:44No data—
Mon 2 NovDalfsen 10:44No data—
Sun 1 NovEmmen Zuid 10:01Partial coverageNo data—
Sat 31 OctDalfsen 10:44Partial coverage0 min—
Fri 30 OctDalfsen 10:44No data—
Thu 29 OctDalfsen 10:44No data—
Wed 28 OctDalfsen 10:460 min—
Tue 27 OctDalfsen 10:440 min—
Mon 26 OctDalfsen 10:44No data—
Sun 25 OctDalfsen 10:45No data—
Sat 24 OctDalfsen 10:46Partial coverage+1 min+1 min
Fri 23 OctDalfsen 10:44No data—
Thu 22 OctDalfsen 10:45No data—
Wed 21 OctDalfsen 10:44No data—
Tue 20 OctDalfsen 10:440 min—
Mon 19 OctDalfsen 10:450 min—
Sun 18 OctDalfsen 10:44Partial coverage0 min—
Sat 17 OctDalfsen 10:46Partial coverage0 min—
Fri 16 OctDalfsen 10:45No data—
Thu 15 OctDalfsen 10:46No data—
Wed 14 OctDalfsen 10:46No data—
Tue 13 OctDalfsen 10:46No data—
Mon 12 OctDalfsen 10:45No data—
Sun 11 OctDalfsen 10:45Partial coverage+1 min—
Sat 10 OctDalfsen 10:45Partial coverage0 min—
Fri 9 OctDalfsen 10:440 min—