Train NS 6145 Zwolle – Groningen

Zwolle 14:23 → Groningen 15:28 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:23 from Zwolle · Fri 6 Nov

Next departure 14:23 today · Zwolle
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 8 full · 9 partial · 12 no data
On-time · 90 days
95%
19/20 runs under 3 min
RT coverage: 11 full · 9 partial · 68 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 Groningen, 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 +5 min · last fix heading to Haren +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 19
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 20 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:23on time on time
14:38≈ on time ≈ on time
14:49≈ on time ≈ on time
14:58≈ on time ≈ on time
15:07≈ on time ≈ on time
15:19≈ on time ≈ +1 min
15:25≈ on time ≈ +1 min
15:28on 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 NovGroningen Europapark 15:39Partial coverage0 min—
Wed 4 NovGroningen Europapark 15:39+1 min+2 min
Tue 3 NovGroningen Europapark 15:39No data—
Mon 2 NovGroningen Europapark 15:39No data—
Sun 1 NovGroningen Europapark 15:39Partial coverage0 min—
Sat 31 OctGroningen Europapark 15:39Partial coverage0 min—
Fri 30 OctGroningen Europapark 15:39Partial coverage0 min—
Thu 29 OctGroningen Europapark 15:39No data—
Wed 28 OctGroningen Europapark 15:390 min—
Tue 27 OctGroningen Europapark 15:390 min—
Mon 26 OctGroningen Europapark 15:39No data—
Sun 25 OctGroningen Europapark 15:39No data—
Sat 24 OctGroningen Europapark 15:39Partial coverage0 min—
Fri 23 OctGroningen Europapark 15:390 min—
Thu 22 OctGroningen Europapark 15:39No data—
Wed 21 OctGroningen Europapark 15:49No data—
Tue 20 OctGroningen Europapark 15:39No data—
Mon 19 OctGroningen Europapark 15:400 min—
Sun 18 OctGroningen Europapark 15:39Partial coverage0 min—
Sat 17 OctGroningen Europapark 15:39Partial coverage0 min—
Fri 16 OctGroningen Europapark 15:40No data—
Thu 15 OctGroningen Europapark 15:39No data—
Wed 14 OctGroningen Europapark 15:39No data—
Tue 13 OctGroningen Europapark 15:39No data—
Mon 12 OctGroningen Europapark 15:390 min—
Sun 11 OctGroningen Europapark 15:39Partial coverage0 min—
Sat 10 OctGroningen Europapark 15:39Partial coverage0 min—
Fri 9 OctGroningen Europapark 15:390 min—
Thu 8 OctGroningen Europapark 15:390 min—
Wed 7 OctGroningen Europapark 15:390 min—