Train Arriva 37624 Eemshaven – Bad Nieuweschans

Eemshaven 07:18 → Bad Nieuweschans 09:08 Mon, Tue, Wed, Thu, Fri, Sat 1 h 50 min · 19 stops Arriva

It has not run yet today

Last recorded run: Tuesday 10 November 0 min

Next service: today 07:18 from Eemshaven · Wed 11 Nov

Next departure 07:18 today · Eemshaven
On-time · 30 days
94%
15/16 runs under 3 min
RT coverage: 4 full · 12 partial · 9 no data
On-time · 90 days
95%
20/21 runs under 3 min
RT coverage: 5 full · 16 partial · 54 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 Bad Nieuweschans, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sat 24 Oct Max en route +12 min · last fix heading to Scheemda +12 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 0% · 0
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=3
  • 100% W n=4
  • 100% T n=3
  • 100% F n=2
  • 80% S n=5
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (19 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
07:18on time on time
07:25≈ on time ≈ on time
07:29 / 07:32≈ on time ≈ +1 min
07:36≈ on time ≈ +1 min
07:41≈ on time ≈ +1 min
07:45≈ on time ≈ +2 min
07:50≈ on time ≈ +2 min
07:54 / 07:55≈ on time ≈ +2 min
08:00≈ on time ≈ +3 min
08:05 / 08:08≈ on time ≈ +3 min
08:13 / 08:17≈ on time ≈ +4 min
08:19≈ on time ≈ +4 min
08:28≈ on time ≈ +4 min
08:30≈ on time ≈ +5 min
08:33≈ on time ≈ +5 min
08:38≈ on time ≈ +5 min
08:44 / 08:45≈ on time ≈ +6 min
08:50 / 08:58≈ on time ≈ +6 min
09:08on time +7 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
Tue 10 NovWinschoten 09:13Partial coverage0 min—
Mon 9 NovWinschoten 09:13Partial coverage0 min—
Sat 7 NovScheemda 08:590 min—
Fri 6 NovWinschoten 09:24No data—
Thu 5 NovWinschoten 09:12No data—
Wed 4 NovWinschoten 09:12Partial coverage0 min—
Tue 3 NovWinschoten 09:14Partial coverage0 min—
Mon 2 NovWinschoten 09:12Partial coverage0 min—
Sat 31 OctScheemda 08:590 min—
Fri 30 OctWinschoten 09:13No data—
Thu 29 OctWinschoten 09:12Partial coverage0 min—
Wed 28 OctWinschoten 09:12Partial coverage0 min—
Tue 27 OctWinschoten 09:12No data—
Mon 26 OctWinschoten 09:22Partial coverage0 min—
Sat 24 OctScheemda 09:11+12 min+12 min
Fri 23 OctWinschoten 09:24Partial coverage0 min—
Thu 22 OctWinschoten 09:12Partial coverage0 min—
Wed 21 OctWinschoten 09:12Partial coverage0 min—
Tue 20 OctWinschoten 09:12No data—
Mon 19 OctWinschoten 09:12Partial coverage0 min—
Sat 17 OctScheemda 08:590 min—
Fri 16 OctWinschoten 09:12No data—
Thu 15 OctWinschoten 09:12No data—
Wed 14 OctWinschoten 09:12No data—
Tue 13 OctWinschoten 09:12No data—
Mon 12 OctWinschoten 09:12No data—
Sat 10 OctScheemda 08:590 min—
Fri 9 OctWinschoten 09:12Partial coverage0 min—
Thu 8 OctWinschoten 09:13Partial coverage+1 min+1 min
Wed 7 OctWinschoten 09:12Partial coverage0 min—