Train Arriva 37604 Warffum – Groningen Europapark

Warffum 07:34 → Groningen Europapark 08:05 Mon, Tue, Wed, Thu, Fri 0 h 31 min · 7 stops Arriva

Running now · updated 07:59

Heading to Groningen Europapark No data

Estimated arrival at Groningen Europapark 08:05 · 22 km/h

  1. Warffum07:34
  2. Baflo07:38
  3. Winsum07:43
  4. Sauwerd07:49
  5. Groningen Noord07:55
  6. Groningen08:00
  7. Groningen Europapark08:05
On-time · 30 days
100%
11/11 runs under 3 min
RT coverage: 0 full · 11 partial · 10 no data
On-time · 90 days
100%
12/12 runs under 3 min
RT coverage: 0 full · 12 partial · 50 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Groningen Europapark, 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

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

  • Early 0% · 0
  • On time 100% · 12
  • 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=3
  • 100% W n=3
  • 100% T n=2
  • 100% F n=2
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 12 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 10Today
07:34on time +1 min
07:38 / 07:39— —
07:43 / 07:44— —
07:49— —
07:55— —
08:00 / 08:02— —
08:05— —

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 Noord 07:54No data—
Wed 4 NovGroningen 08:14Partial coverage0 min—
Tue 3 NovGroningen 08:14No data—
Mon 2 NovGroningen 08:14No data—
Fri 30 OctGroningen 08:16No data—
Thu 29 OctGroningen 08:17Partial coverage0 min—
Wed 28 OctGroningen 08:16Partial coverage0 min—
Tue 27 OctGroningen 08:16Partial coverage0 min—
Mon 26 OctGroningen 08:16Partial coverage0 min—
Fri 23 OctGroningen 08:19Partial coverage0 min—
Thu 22 OctGroningen 08:16No data—
Wed 21 OctBaflo 07:53Partial coverageNo data—
Tue 20 OctGroningen 08:16Partial coverage0 min—
Mon 19 OctGroningen 08:20Partial coverage0 min—
Thu 15 OctGroningen 08:16No data—
Wed 14 OctGroningen 08:16No data—
Tue 13 OctGroningen 08:16No data—
Mon 12 OctGroningen 08:17No data—
Fri 9 OctGroningen 08:16Partial coverage+1 min—
Thu 8 OctGroningen 08:16Partial coverage0 min—
Wed 7 OctGroningen 08:16Partial coverage0 min—
Tue 6 OctGroningen 08:19Partial coverage+3 min+4 min
Mon 5 OctGroningen 08:17No data—
Fri 2 OctGroningen 08:18No data—
Thu 1 OctGroningen 08:17No data—
Wed 30 SeptGroningen 08:16No data—
Tue 29 SeptGroningen 08:18No data—
Mon 28 SeptGroningen 08:16No data—
Fri 25 SeptGroningen Noord 08:10No data—
Thu 24 SeptGroningen 08:16No data—