Train Arriva 37649 Bad Nieuweschans – Eemshaven

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

Running now · updated 14:35

Heading to Eemshaven No data

Estimated arrival at Eemshaven 16:12 · 57 km/h

  1. Bad Nieuweschans14:27
  2. Zuidbroek14:51
  3. Kropswolde15:01
  4. Groningen Noord15:21
  5. Baflo15:39
  6. Uithuizen15:55
  7. Eemshaven16:12
On-time · 30 days
100%
10/10 runs under 3 min
RT coverage: 2 full · 8 partial · 16 no data
On-time · 90 days
100%
16/16 runs under 3 min
RT coverage: 3 full · 13 partial · 60 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 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 16 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
14:27on time on time
14:36 / 14:39— —
14:43 / 14:45— —
14:51— —
14:56— —
14:59— —
15:01— —
15:10— —
15:13 / 15:17— —
15:21 / 15:24— —
15:30— —
15:35— —
15:39 / 15:40— —
15:45— —
15:49 / 15:50— —
15:55— —
15:59 / 16:00— —
16:04— —
16:12— —

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 14:34No data—
Mon 9 NovRoodeschool 16:18Partial coverage0 min—
Sat 7 NovRoodeschool 16:180 min—
Fri 6 NovRoodeschool 16:19No data—
Thu 5 NovRoodeschool 16:20No data—
Wed 4 NovRoodeschool 16:19Partial coverage0 min—
Tue 3 NovRoodeschool 16:19No data—
Mon 2 NovRoodeschool 16:19No data—
Sat 31 OctRoodeschool 16:18No data—
Fri 30 OctRoodeschool 16:19No data—
Thu 29 OctRoodeschool 16:18No data—
Wed 28 OctRoodeschool 16:28Partial coverage0 min—
Tue 27 OctRoodeschool 16:18Partial coverage0 min—
Mon 26 OctRoodeschool 16:18No data—
Sat 24 OctRoodeschool 16:340 min+15 min
Fri 23 OctRoodeschool 16:19No data—
Thu 22 OctRoodeschool 16:20Partial coverage0 min—
Wed 21 OctRoodeschool 16:18No data—
Tue 20 OctRoodeschool 16:21Partial coverage0 min—
Mon 19 OctRoodeschool 16:19Partial coverage0 min—
Sat 17 OctGroningen Europapark 15:24No data—
Fri 16 OctGroningen Europapark 15:24No data—
Thu 15 OctRoodeschool 16:18No data—
Wed 14 OctRoodeschool 16:18No data—
Tue 13 OctRoodeschool 16:18No data—
Mon 12 OctRoodeschool 16:18Partial coverage0 min—
Sat 10 OctRoodeschool 16:180 min—
Fri 9 OctRoodeschool 16:18Partial coverage0 min—
Thu 8 OctRoodeschool 16:18Partial coverage0 min—
Wed 7 OctRoodeschool 16:18Partial coverage0 min—