030 2651 Odense St. – Ringe
View line 030
Alerts for train 2651
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line 030.
Not running right now
Last recorded run: Friday 2 October No data
On-time · 30 days
—
Too little data (0/5 runs with data)
RT coverage: 0 full · 0 partial · 5 no data
On-time · 90 days
—
Too little data (0/5 runs with data)
RT coverage: 0 full · 0 partial · 5 no data
Typical delay
—
Needs at least 5 runs with data (0 so far)
P90
—
Needs at least 5 runs with data (0 so far)
Last 30 days
Arrival delay at Ringe, 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
No runs with a known final delay yet.
On-time by weekday
- — M n=0
- — T n=0
- — W n=0
- — T n=0
- — F n=0
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (8 stops).
| Stop | Sched. |
|---|---|
| 15:11 | |
| 15:14 / 15:15 | |
| 15:17 | |
| 15:19 / 15:20 | |
| 15:23 / 15:24 | |
| 15:27 / 15:28 | |
| 15:30 | |
| 15:35 |
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 14 September 2026.
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Fri 2 Oct | Ringe 15:34 | No data | — |
| Thu 1 Oct | Ringe 15:34 | No data | — |
| Wed 30 Sept | Ringe 15:34 | No data | — |
| Tue 29 Sept | Ringe 15:34 | No data | — |
| Mon 28 Sept | Ringe 15:34 | No data | — |