Train Arriva 37637 Bad Nieuweschans – Eemshaven

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

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 11:27 from Bad Nieuweschans · Sat 7 Nov

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

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

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