Train Arriva 37740 Delfzijl – Winschoten

Delfzijl 11:31 → Winschoten 12:51 Sun 1 h 20 min · 16 stops Arriva

Running now · updated 11:35

Position estimated from the timetable

Heading to Winschoten 0 min

Estimated arrival at Winschoten 12:51 · 51 km/h

  1. Delfzijl11:31
  2. Loppersum11:43
  3. Bedum11:54
  4. Groningen12:10
  5. Kropswolde12:29
  6. Zuidbroek12:39
  7. Winschoten12:51
On-time · 30 days
100%
4/4 runs under 3 min
RT coverage: 3 full · 1 partial · 1 no data
On-time · 90 days
100%
5/5 runs under 3 min
RT coverage: 4 full · 1 partial · 8 no data
Typical delay
0min
Median at arrival, 90 days
P90
0min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Winschoten, 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

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

  • Early 0% · 0
  • On time 100% · 5
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • — S n=0
  • 100% S n=5

Stops and timetable

Timetable of the latest run from the operator’s GTFS (16 stops).

Last 90 days, 5 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
11:31on time on time
11:33— —
11:37— —
11:43— —
11:47— —
11:54— —
11:58— —
12:03 / 12:04— —
12:10 / 12:18— —
12:20— —
12:29— —
12:31— —
12:34— —
12:39— —
12:46— —
12:51— —

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
Sun 15 NovAppingedam 11:34Partial coverage0 min—
Sun 8 NovScheemda 12:590 min—
Sun 1 NovScheemda 13:010 min—
Sun 25 OctScheemda 13:00No data—
Sun 18 OctScheemda 13:000 min—
Sun 11 OctScheemda 13:000 min—
Sun 4 OctScheemda 13:00No data—
Sun 27 SeptScheemda 13:00No data—
Sun 20 SeptScheemda 13:00No data—
Sun 13 SeptScheemda 13:00No data—
Sun 6 SeptScheemda 13:00No data—
Sun 30 AugScheemda 13:00No data—
Sun 23 AugScheemda 13:00No data—