Train Blauwnet A 3835 Zwolle – Emmen

Zwolle 12:22 → Emmen 13:15 Daily 0 h 53 min · 9 stops Blauwnet A

✓ Today’s run finished

Today, last fix heading to Emmen Zuid at 13:24 No data

  1. Zwolle12:22
  2. Dalfsen12:29
  3. Mariënberg12:44
  4. Hardenberg12:49
  5. Coevorden12:58
  6. Emmen Zuid13:11
  7. Emmen13:15

Next service: tomorrow 12:22 from Zwolle · Sat 7 Nov

Next departure 12:22 tomorrow · Zwolle
On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 0 full · 12 partial · 18 no data
On-time · 90 days
100%
15/15 runs under 3 min
RT coverage: 0 full · 15 partial · 74 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

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

  • Early 0% · 0
  • On time 100% · 15
  • 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=3
  • 100% S n=3

Stops and timetable

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

Last 90 days, 15 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
12:22on time on time
12:29 / 12:30— —
12:36 / 12:37— —
12:44— —
12:49— —
12:58 / 13:00— —
13:06 / 13:07— —
13:11— —
13:15— —

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 13:24No data—
Thu 5 NovEmmen Zuid 13:24No data—
Wed 4 NovEmmen Zuid 13:24Partial coverage0 min—
Tue 3 NovEmmen Zuid 13:25No data—
Mon 2 NovEmmen Zuid 13:24No data—
Sun 1 NovEmmen Zuid 13:26Partial coverage0 min—
Sat 31 OctEmmen Zuid 13:25Partial coverage0 min—
Fri 30 OctEmmen Zuid 13:25No data—
Thu 29 OctEmmen Zuid 13:25No data—
Wed 28 OctEmmen Zuid 13:27Partial coverage0 min—
Tue 27 OctEmmen Zuid 13:25Partial coverage0 min—
Mon 26 OctEmmen Zuid 13:25No data—
Sun 25 OctEmmen Zuid 13:25No data—
Sat 24 OctEmmen Zuid 13:25Partial coverage0 min—
Fri 23 OctEmmen Zuid 13:25No data—
Thu 22 OctEmmen Zuid 13:25No data—
Wed 21 OctEmmen Zuid 13:25No data—
Tue 20 OctEmmen Zuid 13:25Partial coverage0 min—
Mon 19 OctEmmen Zuid 13:25No data—
Sun 18 OctEmmen Zuid 13:25Partial coverage0 min—
Sat 17 OctEmmen Zuid 13:25No data—
Fri 16 OctEmmen Zuid 13:27No data—
Thu 15 OctEmmen Zuid 13:25No data—
Wed 14 OctEmmen Zuid 13:27No data—
Tue 13 OctEmmen Zuid 13:25No data—
Mon 12 OctEmmen Zuid 13:25No data—
Sun 11 OctEmmen Zuid 13:25Partial coverage0 min—
Sat 10 OctEmmen Zuid 13:25Partial coverage0 min—
Fri 9 OctEmmen Zuid 13:26Partial coverage+2 min+2 min
Thu 8 OctEmmen Zuid 13:25Partial coverage0 min—