Train Arriva 37641 Bad Nieuweschans – Eemshaven

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

✓ Today’s run finished

Today, last fix heading to Roodeschool at 14:19 No data

  1. Bad Nieuweschans12:27
  2. Zuidbroek12:51
  3. Kropswolde13:01
  4. Groningen Noord13:21
  5. Baflo13:39
  6. Roodeschool14:04
  7. Eemshaven14:12

Next service: tomorrow 12:27 from Bad Nieuweschans · Fri 6 Nov

Next departure 12:27 tomorrow · Bad Nieuweschans
On-time · 30 days
100%
15/15 runs under 3 min
RT coverage: 4 full · 11 partial · 11 no data
On-time · 90 days
100%
17/17 runs under 3 min
RT coverage: 4 full · 13 partial · 59 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

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

  • Early 0% · 0
  • On time 100% · 17
  • 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=4
  • 100% W n=4
  • 100% T n=3
  • 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, 17 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
12:27on time on time
12:36 / 12:39— —
12:43 / 12:45— —
12:51— —
12:56— —
12:59— —
13:01— —
13:10— —
13:13 / 13:17— —
13:21 / 13:24— —
13:30— —
13:35— —
13:39 / 13:40— —
13:45— —
13:49 / 13:50— —
13:55— —
13:59 / 14:00— —
14:04— —
14: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
Thu 5 NovRoodeschool 14:19No data—
Wed 4 NovRoodeschool 14:18Partial coverage0 min—
Tue 3 NovRoodeschool 14:18No data—
Mon 2 NovRoodeschool 14:18No data—
Sat 31 OctRoodeschool 14:180 min—
Fri 30 OctRoodeschool 14:18No data—
Thu 29 OctRoodeschool 14:19Partial coverage0 min—
Wed 28 OctRoodeschool 14:18Partial coverage0 min—
Tue 27 OctUithuizermeeden 14:23Partial coverage0 min—
Mon 26 OctRoodeschool 14:18No data—
Sat 24 OctRoodeschool 14:180 min—
Fri 23 OctRoodeschool 14:18No data—
Thu 22 OctRoodeschool 14:20Partial coverage0 min—
Wed 21 OctRoodeschool 14:18Partial coverage0 min—
Tue 20 OctRoodeschool 14:18Partial coverage0 min—
Mon 19 OctRoodeschool 14:18Partial coverage0 min—
Sat 17 OctGroningen Europapark 13:24No data—
Fri 16 OctGroningen Europapark 13:24No data—
Thu 15 OctRoodeschool 14:46No data—
Wed 14 OctRoodeschool 14:24No data—
Tue 13 OctUithuizermeeden 14:230 min—
Mon 12 OctRoodeschool 14:18No data—
Sat 10 OctRoodeschool 14:180 min—
Fri 9 OctRoodeschool 14:19Partial coverage0 min—
Thu 8 OctRoodeschool 14:18Partial coverage0 min—
Wed 7 OctRoodeschool 14:18Partial coverage0 min—
Tue 6 OctRoodeschool 14:18Partial coverage0 min—
Mon 5 OctRoodeschool 14:18Partial coverage0 min—
Sat 3 OctRoodeschool 14:18No data—
Fri 2 OctRoodeschool 14:19No data—