Train NS 6135 Zwolle – Groningen

Zwolle 11:53 → Groningen 12:58 Daily 1 h 05 min · 8 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 11:53 from Zwolle · Sun 8 Nov

Next departure 11:53 today · Zwolle
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 6 full · 7 partial · 16 no data
On-time · 90 days
100%
18/18 runs under 3 min
RT coverage: 11 full · 7 partial · 70 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

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=2
  • 100% T n=2
  • 100% W n=3
  • 100% T n=1
  • 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, 18 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
11:53on time on time
12:08≈ on time ≈ on time
12:19≈ on time ≈ on time
12:28≈ on time ≈ on time
12:37≈ on time ≈ on time
12:49≈ on time ≈ on time
12:55≈ on time ≈ on time
12:58on 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 NovGroningen Europapark 13:09Partial coverage0 min—
Fri 6 NovGroningen Europapark 13:09No data—
Thu 5 NovGroningen Europapark 13:09No data—
Wed 4 NovGroningen Europapark 13:090 min—
Tue 3 NovGroningen Europapark 13:09No data—
Mon 2 NovGroningen Europapark 13:09No data—
Sun 1 NovGroningen Europapark 13:11Partial coverage+1 min+1 min
Sat 31 OctGroningen Europapark 13:09Partial coverage0 min—
Fri 30 OctGroningen Europapark 13:09Partial coverage0 min—
Thu 29 OctGroningen Europapark 13:09No data—
Wed 28 OctGroningen Europapark 13:110 min—
Tue 27 OctGroningen Europapark 13:090 min—
Mon 26 OctGroningen Europapark 13:09No data—
Sun 25 OctGroningen Europapark 13:09No data—
Sat 24 OctGroningen Europapark 13:09Partial coverage0 min—
Fri 23 OctGroningen Europapark 13:120 min—
Thu 22 OctGroningen Europapark 13:09No data—
Wed 21 OctGroningen Europapark 13:18No data—
Tue 20 OctGroningen Europapark 13:09No data—
Mon 19 OctGroningen Europapark 13:090 min—
Sun 18 OctGroningen Europapark 13:09Partial coverage0 min—
Sat 17 OctGroningen Europapark 13:09No data—
Fri 16 OctGroningen Europapark 13:09No data—
Thu 15 OctGroningen Europapark 13:09No data—
Wed 14 OctGroningen Europapark 13:10No data—
Tue 13 OctGroningen Europapark 13:09No data—
Mon 12 OctGroningen Europapark 13:09No data—
Sun 11 OctGroningen Europapark 13:090 min—
Sat 10 OctGroningen Europapark 13:09Partial coverage0 min—
Fri 9 OctGroningen Europapark 13:090 min—