Train NS 6157 Zwolle – Groningen

Zwolle 17:23 → Groningen 18:28 Daily 1 h 05 min · 8 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Assen at 18:29 0 min

  1. Zwolle17:23
  2. Meppel17:38
  3. Hoogeveen17:49
  4. Assen18:07
  5. Haren18:19
  6. Groningen Europapark18:25
  7. Groningen18:28

Next service: tomorrow 17:23 from Zwolle · Fri 6 Nov

Next departure 17:23 tomorrow · Zwolle
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 10 full · 9 partial · 11 no data
On-time · 90 days
95%
20/21 runs under 3 min
RT coverage: 12 full · 9 partial · 68 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Thu 8 Oct Max en route +6 min · last fix heading to Beilen +6 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=5
  • 100% T n=2
  • 100% W n=3
  • 50% T n=2
  • 100% F n=2
  • 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, 21 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
17:23on time on time
17:38≈ on time ≈ +1 min
17:49≈ on time ≈ +2 min
17:58≈ on time ≈ +2 min
18:07≈ on time ≈ +2 min
18:19≈ on time ≈ +2 min
18:25≈ on time ≈ +2 min
18:28on time +2 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 NovAssen 18:29Partial coverage0 min—
Wed 4 NovAssen 18:290 min—
Tue 3 NovAssen 18:29No data—
Mon 2 NovAssen 18:29+2 min+2 min
Sun 1 NovGroningen Europapark 18:39Partial coverage0 min—
Sat 31 OctGroningen Europapark 18:39Partial coverage0 min—
Fri 30 OctGroningen Europapark 18:39Partial coverage0 min—
Thu 29 OctBeilen 18:30No data—
Wed 28 OctAssen 18:300 min—
Tue 27 OctBeilen 18:30No data—
Mon 26 OctAssen 18:350 min—
Sun 25 OctGroningen Europapark 18:39No data—
Sat 24 OctGroningen Europapark 18:39Partial coverage0 min—
Fri 23 OctGroningen Europapark 18:39No data—
Thu 22 OctGroningen Europapark 18:39No data—
Wed 21 OctGroningen Europapark 18:34No data—
Tue 20 OctGroningen Europapark 18:390 min—
Mon 19 OctGroningen Europapark 18:390 min—
Sun 18 OctGroningen Europapark 18:41Partial coverage+2 min+3 min
Sat 17 OctGroningen Europapark 18:42Partial coverage0 min—
Fri 16 OctGroningen Europapark 18:39No data—
Thu 15 OctGroningen Europapark 18:39No data—
Wed 14 OctGroningen Europapark 18:39No data—
Tue 13 OctGroningen Europapark 18:39No data—
Mon 12 OctGroningen Europapark 18:390 min—
Sun 11 OctGroningen Europapark 18:39Partial coverage0 min—
Sat 10 OctGroningen Europapark 18:39Partial coverage+1 min—
Fri 9 OctGroningen Europapark 18:390 min—
Thu 8 OctBeilen 18:35+6 min+6 min
Wed 7 OctAssen 18:290 min—