Train Arriva 37633 Bad Nieuweschans – Eemshaven

Bad Nieuweschans 10:27 → Eemshaven 12: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 12:19 0 min

  1. Bad Nieuweschans10:27
  2. Zuidbroek10:51
  3. Kropswolde11:01
  4. Groningen Noord11:21
  5. Baflo11:39
  6. Roodeschool12:04
  7. Eemshaven12:12

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

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

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

  • Early 0% · 0
  • On time 100% · 19
  • 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=5
  • 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, 19 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
10:27on time on time
10:36 / 10:39≈ on time ≈ on time
10:43 / 10:45≈ on time ≈ on time
10:51≈ on time ≈ on time
10:56≈ on time ≈ on time
10:59≈ on time ≈ on time
11:01≈ on time ≈ on time
11:10≈ on time ≈ on time
11:13 / 11:17≈ on time ≈ on time
11:21 / 11:24≈ on time ≈ on time
11:30≈ on time ≈ on time
11:35≈ on time ≈ on time
11:39 / 11:40≈ on time ≈ on time
11:45≈ on time ≈ on time
11:49 / 11:50≈ on time ≈ on time
11:55≈ on time ≈ on time
11:59 / 12:00≈ on time ≈ on time
12:04≈ on time ≈ on time
12:12on time on time

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