Train NS 6144 Groningen – Zwolle

Groningen 12:02 → Zwolle 13:07 Daily 1 h 05 min · 8 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Meppel at 13:08 0 min

  1. Groningen12:02
  2. Groningen Europapark12:05
  3. Haren12:09
  4. Beilen12:32
  5. Hoogeveen12:40
  6. Meppel12:51
  7. Zwolle13:07

Next service: tomorrow 12:02 from Groningen · Sun 8 Nov

Next departure 12:02 tomorrow · Groningen
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 10 full · 9 partial · 11 no data
On-time · 90 days
96%
22/23 runs under 3 min
RT coverage: 14 full · 9 partial · 66 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

Worst days

  • Mon 5 Oct Max en route +3 min · last fix heading to Meppel +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 22
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 23 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:02on time on time
12:05≈ on time ≈ on time
12:09≈ on time ≈ on time
12:22≈ on time ≈ on time
12:32≈ on time ≈ on time
12:40≈ on time ≈ on time
12:51≈ on time ≈ on time
13:07on 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 NovMeppel 13:08Partial coverage0 min—
Fri 6 NovMeppel 13:08No data—
Thu 5 NovMeppel 13:08Partial coverage0 min—
Wed 4 NovMeppel 13:090 min—
Tue 3 NovMeppel 13:08No data—
Mon 2 NovMeppel 13:09No data—
Sun 1 NovMeppel 13:09Partial coverage+1 min+1 min
Sat 31 OctMeppel 13:18Partial coverage0 min—
Fri 30 OctMeppel 13:060 min—
Thu 29 OctMeppel 13:10No data—
Wed 28 OctMeppel 13:080 min—
Tue 27 OctMeppel 13:090 min—
Mon 26 OctMeppel 13:080 min—
Sun 25 OctMeppel 13:08No data—
Sat 24 OctMeppel 13:09Partial coverage0 min—
Fri 23 OctMeppel 13:08No data—
Thu 22 OctMeppel 13:11No data—
Wed 21 OctMeppel 13:11No data—
Tue 20 OctMeppel 13:120 min—
Mon 19 OctMeppel 13:080 min—
Sun 18 OctMeppel 13:06Partial coverage0 min—
Sat 17 OctMeppel 13:08Partial coverage0 min—
Fri 16 OctMeppel 13:150 min—
Thu 15 OctMeppel 13:11No data—
Wed 14 OctMeppel 13:08No data—
Tue 13 OctMeppel 13:08No data—
Mon 12 OctMeppel 13:090 min—
Sun 11 OctMeppel 13:08Partial coverage0 min—
Sat 10 OctMeppel 13:08Partial coverage0 min—
Fri 9 OctMeppel 13:090 min—