Train Arriva 37668 Eemshaven – Bad Nieuweschans

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

✓ Today’s run finished

Today, last fix heading to Roodeschool at 18:39 0 min

  1. Eemshaven18:18
  2. Roodeschool18:25
  3. Uithuizermeeden18:29
  4. Uithuizen18:36
  5. Baflo18:50
  6. Groningen Noord19:05
  7. Bad Nieuweschans20:08

Next service: tomorrow 18:18 from Eemshaven · Tue 17 Nov

Next departure 18:18 tomorrow · Eemshaven
On-time · 30 days
100%
11/11 runs under 3 min
RT coverage: 3 full · 8 partial · 4 no data
On-time · 90 days
100%
13/13 runs under 3 min
RT coverage: 4 full · 9 partial · 31 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 Bad Nieuweschans, 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

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

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

On-time by weekday

  • 100% M n=3
  • 100% T n=2
  • — W n=0
  • 100% T n=1
  • 100% F n=3
  • 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, 13 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
18:18on time on time
18:25— —
18:29 / 18:32— —
18:36— —
18:41— —
18:45— —
18:50— —
18:54 / 18:55— —
19:00— —
19:05 / 19:08— —
19:13 / 19:17— —
19:19— —
19:28— —
19:30— —
19:33— —
19:38— —
19:44 / 19:45— —
19:50 / 19:58— —
20:08— —

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 NovRoodeschool 18:39Partial coverage0 min—
Sat 14 NovScheemda 19:590 min—
Fri 13 NovWinsum 19:09Partial coverage0 min—
Thu 12 NovEemshaven 18:32Partial coverage0 min—
Tue 10 NovEemshaven 18:32Partial coverage0 min—
Sat 7 NovScheemda 19:59+1 min—
Fri 6 NovWarffum 18:59Partial coverage0 min—
Sat 31 OctScheemda 19:590 min—
Fri 30 OctBaflo 19:04No data—
Sat 24 OctScheemda 19:59No data—
Fri 23 OctGroningen Europapark 19:33Partial coverage0 min—
Thu 22 OctWarffum 18:59No data—
Wed 21 OctUithuizen 18:50No data—
Tue 20 OctWarffum 18:50Partial coverage0 min—
Mon 19 OctUsquert 18:55Partial coverage0 min—
Sat 17 OctScheemda 19:59No data—
Fri 16 OctScheemda 19:59No data—
Thu 15 OctRoodeschool 18:39No data—
Wed 14 OctScheemda 19:59No data—
Tue 13 OctUithuizen 18:50No data—
Mon 12 OctWarffum 18:59Partial coverage0 min—
Sat 10 OctScheemda 19:590 min—
Fri 9 OctUithuizen 18:50No data—
Sat 3 OctScheemda 20:13No data—
Fri 2 OctWarffum 18:59No data—
Sat 26 SeptScheemda 19:59No data—
Fri 25 SeptUithuizermeeden 18:46No data—
Sat 19 SeptScheemda 20:04No data—
Fri 18 SeptWarffum 18:59No data—
Sat 12 SeptScheemda 19:59No data—