Train NS 548 Groningen → Den Haag Centraal

Groningen 13:18 → Den Haag Centraal 15:50 Daily 2 h 32 min · 7 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 20 November +1 min

Next service: today 13:18 from Groningen · Sat 21 Nov

Next departure 13:18 today · Groningen
On-time · 30 days
92%
22/24 runs under 3 min
RT coverage: 4 full · 20 partial · 5 no data
On-time · 90 days
91%
32/35 runs under 3 min
RT coverage: 8 full · 27 partial · 53 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 Den Haag Centraal, 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 12 Nov Max en route +11 min · last fix heading to Gouda +10 min
  • Mon 9 Nov Max en route +6 min · last fix heading to Gouda +6 min
  • Thu 8 Oct Max en route +4 min · last fix heading to Gouda +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 32
  • 3–10 min 9% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 100% T n=5
  • 100% W n=5
  • 50% T n=4
  • 100% F n=5
  • 100% S n=5
  • 100% S n=5

Stops and timetable

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

Last 90 days, 35 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
13:18on time on time
13:35≈ on time ≈ on time
14:14 / 14:19≈ on time ≈ on time
14:54 / 14:56≈ on time ≈ +1 min
15:09 / 15:13≈ on time ≈ +1 min
15:31 / 15:33≈ on time ≈ +1 min
15:50on 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
Fri 20 NovGouda 15:52Partial coverage+1 min—
Thu 19 NovGouda 15:54Partial coverage+2 min+2 min
Wed 18 NovGouda 15:52Partial coverage+1 min+2 min
Tue 17 NovGouda 15:52Partial coverage+1 min+2 min
Mon 16 NovGouda 15:54Partial coverage+2 min+3 min
Sun 15 NovGouda 15:49+1 min+1 min
Sat 14 NovGouda 15:49Partial coverage0 min—
Fri 13 NovGouda 15:49Partial coverage0 min—
Thu 12 NovGouda 16:08Partial coverage+10 min+11 min
Wed 11 NovGouda 15:49Partial coverage0 min—
Tue 10 NovGouda 15:52Partial coverage+1 min—
Mon 9 NovGouda 16:03Partial coverage+6 min+6 min
Sun 8 NovLansingerland-Zoetermeer 15:540 min—
Sat 7 NovLansingerland-Zoetermeer 15:57+1 min+1 min
Fri 6 NovGouda 15:49No data—
Thu 5 NovGouda 16:04No data—
Wed 4 NovGouda 15:49Partial coverage+1 min+1 min
Tue 3 NovGouda 16:07No data—
Mon 2 NovGouda 15:52No data—
Sun 1 NovGouda 15:48Partial coverage0 min—
Sat 31 OctGouda 15:47Partial coverage0 min—
Fri 30 OctGouda 15:510 min—
Thu 29 OctGouda 15:51Partial coverage0 min—
Wed 28 OctGouda 15:55Partial coverage0 min—
Tue 27 OctGouda 15:54Partial coverage0 min—
Mon 26 OctGouda 15:52Partial coverage0 min—
Sun 25 OctGouda 15:52No data—
Sat 24 OctGouda 15:51Partial coverage0 min—
Fri 23 OctGouda 15:52Partial coverage0 min—
Thu 22 OctGouda 15:56No data—