Train NS 6154 Groningen – Zwolle

Groningen 14:32 → Zwolle 15:37 Daily 1 h 05 min · 8 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November 0 min

Next service: today 14:32 from Groningen · Fri 6 Nov

Next departure 14:32 today · Groningen
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 13 full · 9 partial · 7 no data
On-time · 90 days
100%
25/25 runs under 3 min
RT coverage: 15 full · 10 partial · 63 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 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 25 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
14:32on time on time
14:35≈ on time ≈ on time
14:39≈ on time ≈ on time
14:52≈ on time ≈ on time
15:02≈ on time ≈ on time
15:10≈ on time ≈ on time
15:21≈ on time ≈ on time
15:37on 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
Thu 5 NovMeppel 15:39Partial coverage0 min—
Wed 4 NovMeppel 15:390 min—
Tue 3 NovMeppel 15:38Partial coverage0 min—
Mon 2 NovMeppel 15:390 min—
Sun 1 NovMeppel 15:390 min—
Sat 31 OctMeppel 15:36No data—
Fri 30 OctMeppel 15:38Partial coverage0 min—
Thu 29 OctMeppel 15:360 min—
Wed 28 OctMeppel 15:380 min—
Tue 27 OctMeppel 15:39Partial coverage0 min—
Mon 26 OctMeppel 15:390 min—
Sun 25 OctMeppel 15:38No data—
Sat 24 OctMeppel 15:380 min—
Fri 23 OctMeppel 15:42No data—
Thu 22 OctMeppel 15:38No data—
Wed 21 OctMeppel 15:40No data—
Tue 20 OctMeppel 15:38Partial coverage0 min—
Mon 19 OctMeppel 15:460 min—
Sun 18 OctMeppel 15:380 min—
Sat 17 OctMeppel 15:360 min—
Fri 16 OctMeppel 16:05Partial coverage0 min—
Thu 15 OctMeppel 15:51No data—
Wed 14 OctMeppel 15:38No data—
Tue 13 OctMeppel 15:38Partial coverage0 min—
Mon 12 OctMeppel 15:390 min—
Sun 11 OctMeppel 15:41Partial coverage+1 min+1 min
Sat 10 OctMeppel 15:380 min—
Fri 9 OctMeppel 15:38Partial coverage0 min—
Thu 8 OctMeppel 15:380 min—
Wed 7 OctMeppel 15:380 min—