Train Arriva 37648 Eemshaven – Bad Nieuweschans

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

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 13:18 from Eemshaven · Thu 5 Nov

Next departure 13:18 today · Eemshaven
On-time · 30 days
100%
14/14 runs under 3 min
RT coverage: 3 full · 11 partial · 11 no data
On-time · 90 days
100%
16/16 runs under 3 min
RT coverage: 3 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 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

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 10
13:18on time on time
13:25— —
13:29 / 13:32— —
13:36— —
13:41— —
13:45— —
13:50— —
13:54 / 13:55— —
14:00— —
14:05 / 14:08— —
14:13 / 14:17— —
14:19— —
14:28— —
14:30— —
14:33— —
14:38— —
14:44 / 14:45— —
14:50 / 14:58— —
15: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
Wed 4 NovWinschoten 15:12Partial coverage0 min—
Tue 3 NovWinschoten 15:12Partial coverage0 min—
Mon 2 NovWinschoten 15:12Partial coverage0 min—
Sat 31 OctScheemda 14:590 min—
Fri 30 OctWinschoten 15:14No data—
Thu 29 OctWinschoten 15:12Partial coverage0 min—
Wed 28 OctWinschoten 15:12Partial coverage0 min—
Tue 27 OctWinschoten 15:12No data—
Mon 26 OctWinschoten 15:12Partial coverage0 min—
Sat 24 OctScheemda 14:590 min—
Fri 23 OctWinschoten 15:12No data—
Thu 22 OctWinschoten 15:12No data—
Wed 21 OctWinschoten 15:12No data—
Tue 20 OctWinschoten 15:12Partial coverage0 min—
Mon 19 OctWinschoten 15:13Partial coverage0 min—
Sat 17 OctScheemda 14:59No data—
Fri 16 OctWinschoten 15:12No data—
Thu 15 OctWinschoten 15:13No data—
Wed 14 OctWinschoten 15:22No data—
Tue 13 OctWinschoten 15:12No data—
Mon 12 OctWinschoten 15:12No data—
Sat 10 OctScheemda 15:000 min—
Fri 9 OctWinschoten 15:13Partial coverage0 min—
Thu 8 OctWinschoten 15:15Partial coverage+3 min+3 min
Wed 7 OctWinschoten 15:12Partial coverage0 min—
Tue 6 OctWinschoten 15:12Partial coverage0 min—
Mon 5 OctWinschoten 15:17Partial coverage0 min—
Sat 3 OctScheemda 14:59No data—
Fri 2 OctScheemda 14:59No data—
Thu 1 OctScheemda 15:00No data—