Train Arriva 37846 Delfzijl – Veendam
✓ Today’s run finished
Today, last fix heading to Zuidbroek at 14:04 0 min
- Delfzijl12:48
- Appingedam12:54
- Bedum13:11
- Groningen Noord13:20
- Groningen Europapark13:31
- Zuidbroek13:50
- Veendam13:57
Next service: Monday 12:48 from Delfzijl · Mon 9 Nov
Last 30 days
Arrival delay at Veendam, 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
17 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 17
- 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=4
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (15 stops).
Last 90 days, 17 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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 12:48 | on time | on time | |
| 12:50 | ≈ on time | ≈ on time | |
| 12:54 | ≈ on time | ≈ on time | |
| 13:00 | ≈ on time | ≈ on time | |
| 13:04 | ≈ on time | ≈ on time | |
| 13:11 | ≈ on time | ≈ on time | |
| 13:15 | ≈ on time | ≈ on time | |
| 13:20 / 13:23 | ≈ on time | ≈ on time | |
| 13:28 / 13:29 | ≈ on time | ≈ on time | |
| 13:31 | ≈ on time | ≈ on time | |
| 13:40 | ≈ on time | ≈ on time | |
| 13:42 | ≈ on time | ≈ on time | |
| 13:45 | ≈ on time | ≈ on time | |
| 13:50 | ≈ on time | ≈ on time | |
| 13:57 | on 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sat 7 Nov | Zuidbroek 14:04Partial coverage | 0 min | — |
| Fri 6 Nov | Zuidbroek 14:04 | No data | — |
| Thu 5 Nov | Zuidbroek 14:04 | No data | — |
| Wed 4 Nov | Zuidbroek 14:04 | 0 min | — |
| Tue 3 Nov | Zuidbroek 14:04 | 0 min | — |
| Mon 2 Nov | Zuidbroek 14:04 | 0 min | — |
| Sat 31 Oct | Zuidbroek 14:04Partial coverage | 0 min | — |
| Fri 30 Oct | Zuidbroek 14:05 | No data | — |
| Thu 29 Oct | Zuidbroek 14:04 | 0 min | — |
| Wed 28 Oct | Zuidbroek 14:04 | 0 min | — |
| Tue 27 Oct | Zuidbroek 14:04 | No data | — |
| Mon 26 Oct | Zuidbroek 14:05 | 0 min | — |
| Sat 24 Oct | Zuidbroek 14:04Partial coverage | +1 min | +1 min |
| Fri 23 Oct | Zuidbroek 14:05 | No data | — |
| Thu 22 Oct | Zuidbroek 14:05 | No data | — |
| Wed 21 Oct | Zuidbroek 14:04 | No data | — |
| Tue 20 Oct | Zuidbroek 14:04 | 0 min | — |
| Mon 19 Oct | Zuidbroek 14:04 | 0 min | — |
| Sat 17 Oct | Zuidbroek 14:04 | No data | — |
| Fri 16 Oct | Zuidbroek 14:05 | No data | — |
| Thu 15 Oct | Zuidbroek 14:04 | No data | — |
| Wed 14 Oct | Zuidbroek 14:04 | No data | — |
| Tue 13 Oct | Zuidbroek 14:04 | No data | — |
| Mon 12 Oct | Zuidbroek 14:04 | No data | — |
| Sat 10 Oct | Zuidbroek 14:06Partial coverage | +1 min | +1 min |
| Fri 9 Oct | Zuidbroek 14:04 | 0 min | — |
| Thu 8 Oct | Zuidbroek 14:04 | 0 min | — |
| Wed 7 Oct | Zuidbroek 14:04 | 0 min | — |
| Tue 6 Oct | Zuidbroek 14:05 | 0 min | — |
| Mon 5 Oct | Zuidbroek 14:04 | 0 min | — |