Train Arriva 37656 Eemshaven – Bad Nieuweschans

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

Running now · updated 17:02

Heading to Bad Nieuweschans 0 min

Estimated arrival at Bad Nieuweschans 17:08

  1. Eemshaven15:18
  2. Uithuizen15:36
  3. Baflo15:50
  4. Groningen Noord16:05
  5. Kropswolde16:28
  6. Zuidbroek16:38
  7. Bad Nieuweschans17:08

Today it is running no worse than usual: typical arrival delay is 0 min; 100% of the last 15 runs arrived on time.

On-time · 30 days
100%
15/15 runs under 3 min
RT coverage: 3 full · 12 partial · 11 no data
On-time · 90 days
95%
20/21 runs under 3 min
RT coverage: 4 full · 17 partial · 55 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
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

Worst days

  • Fri 9 Oct Max en route +18 min · last fix heading to Winschoten +18 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 20
  • 3–10 min 0% · 0
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

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