Train Blauwnet A 8049 Zwolle – Emmen

Zwolle 15:52 → Emmen 16:50 Daily 0 h 58 min · 11 stops Blauwnet A

✓ Today’s run finished

Today, last fix heading to Emmen Zuid at 16:59 No data

  1. Zwolle15:52
  2. Ommen16:06
  3. Mariënberg16:14
  4. Gramsbergen16:24
  5. Dalen16:35
  6. Emmen Zuid16:44
  7. Emmen16:50

Next service: tomorrow 15:52 from Zwolle · Fri 6 Nov

Next departure 15:52 tomorrow · Zwolle
On-time · 30 days
100%
15/15 runs under 3 min
RT coverage: 6 full · 9 partial · 15 no data
On-time · 90 days
100%
17/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
+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

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 100% · 17
  • 3–10 min 0% · 0
  • 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
  • 100% S n=3

Stops and timetable

Timetable of the latest run from the operator’s GTFS (11 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:52on time on time
15:59 / 16:00≈ on time ≈ on time
16:06 / 16:07≈ on time ≈ on time
16:14≈ on time ≈ on time
16:19≈ on time ≈ on time
16:24≈ on time ≈ on time
16:30 / 16:32≈ on time ≈ +1 min
16:35≈ on time ≈ +1 min
16:40 / 16:41≈ on time ≈ +1 min
16:44 / 16:45≈ on time ≈ +1 min
16:50on 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 NovEmmen Zuid 16:59No data—
Wed 4 NovEmmen Zuid 16:59Partial coverage0 min—
Tue 3 NovEmmen Zuid 16:59No data—
Mon 2 NovEmmen Zuid 16:59No data—
Sun 1 NovEmmen Zuid 17:00+1 min+2 min
Sat 31 OctEmmen Zuid 16:590 min—
Fri 30 OctEmmen Zuid 16:59No data—
Thu 29 OctEmmen Zuid 16:59No data—
Wed 28 OctEmmen Zuid 16:59Partial coverage0 min—
Tue 27 OctEmmen Zuid 16:59Partial coverage0 min—
Mon 26 OctEmmen Zuid 16:59No data—
Sun 25 OctEmmen Zuid 16:59No data—
Sat 24 OctEmmen Zuid 16:590 min—
Fri 23 OctEmmen Zuid 16:59No data—
Thu 22 OctEmmen Zuid 17:13No data—
Wed 21 OctEmmen Zuid 17:00No data—
Tue 20 OctEmmen Zuid 16:59Partial coverage0 min—
Mon 19 OctEmmen Zuid 17:00Partial coverage0 min—
Sun 18 OctEmmen Zuid 16:590 min—
Sat 17 OctEmmen Zuid 16:59No data—
Fri 16 OctEmmen Zuid 16:59No data—
Thu 15 OctEmmen Zuid 16:59No data—
Wed 14 OctEmmen Zuid 16:59No data—
Tue 13 OctEmmen Zuid 17:00No data—
Mon 12 OctEmmen Zuid 16:59Partial coverage0 min—
Sun 11 OctEmmen Zuid 17:00+1 min+2 min
Sat 10 OctEmmen Zuid 16:590 min—
Fri 9 OctEmmen Zuid 16:59Partial coverage0 min—
Thu 8 OctEmmen Zuid 17:01Partial coverage+1 min+2 min
Wed 7 OctEmmen Zuid 17:02Partial coverage0 min+3 min