Train Arriva 37661 Bad Nieuweschans – Eemshaven

Bad Nieuweschans 17:27 → Eemshaven 19:12 Mon, Tue, Wed, Thu, Fri, Sat 1 h 45 min · 19 stops Arriva

It has not run yet today

Last recorded run: Monday 16 November 0 min

Next service: today 17:27 from Bad Nieuweschans · Tue 17 Nov

Next departure 17:27 today · Bad Nieuweschans
On-time · 30 days
100%
16/16 runs under 3 min
RT coverage: 3 full · 13 partial · 9 no data
On-time · 90 days
100%
23/23 runs under 3 min
RT coverage: 5 full · 18 partial · 52 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: +1 min

Last 30 days

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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 23 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:27on time on time
17:36 / 17:39≈ on time ≈ on time
17:43 / 17:45≈ on time ≈ on time
17:51≈ on time ≈ on time
17:56≈ on time ≈ on time
17:59≈ on time ≈ on time
18:01≈ on time ≈ on time
18:10≈ on time ≈ on time
18:13 / 18:17≈ on time ≈ on time
18:21 / 18:24≈ on time ≈ on time
18:30≈ on time ≈ +1 min
18:35≈ on time ≈ +1 min
18:39 / 18:40≈ on time ≈ +1 min
18:45≈ on time ≈ +1 min
18:49 / 18:50≈ on time ≈ +1 min
18:55≈ on time ≈ +1 min
18:59 / 19:00≈ on time ≈ +1 min
19:04≈ on time ≈ +1 min
19:12on 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
Mon 16 NovGroningen Noord 18:38Partial coverage0 min—
Sat 14 NovRoodeschool 19:19+1 min—
Fri 13 NovUithuizen 19:09Partial coverage+1 min—
Thu 12 NovGroningen 18:29Partial coverage0 min—
Wed 11 NovGroningen Europapark 18:24Partial coverage0 min—
Tue 10 NovGroningen 18:29Partial coverage0 min—
Mon 9 NovGroningen Europapark 18:24Partial coverage0 min—
Sat 7 NovRoodeschool 19:180 min—
Fri 6 NovWarffum 18:59Partial coverage0 min—
Thu 5 NovGroningen Europapark 18:24No data—
Wed 4 NovGroningen Europapark 18:24Partial coverage0 min—
Tue 3 NovGroningen Europapark 18:24No data—
Mon 2 NovGroningen Europapark 18:24No data—
Sat 31 OctRoodeschool 19:180 min—
Fri 30 OctUsquert 19:04No data—
Thu 29 OctKropswolde 18:15No data—
Wed 28 OctGroningen Europapark 18:24Partial coverage0 min—
Tue 27 OctKropswolde 18:15Partial coverage0 min—
Mon 26 OctKropswolde 18:15No data—
Sat 24 OctRoodeschool 19:19No data—
Fri 23 OctRoodeschool 19:15Partial coverage+1 min+1 min
Thu 22 OctWarffum 18:59No data—
Wed 21 OctBaflo 18:54No data—
Tue 20 OctWarffum 18:50Partial coverage0 min—
Mon 19 OctBaflo 18:54Partial coverage0 min—
Sat 17 OctGroningen Europapark 18:24No data—
Fri 16 OctGroningen Europapark 18:24No data—
Thu 15 OctSauwerd 18:44No data—
Wed 14 OctRoodeschool 19:18No data—
Tue 13 OctBaflo 18:50No data—