EC 30357 30357
View line EC 30357
Alerts for train 30357
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line EC 30357.
Not running right now
Last recorded run: Thursday 1 October +14 min
The mini-map returns when the train runs
On-time · 30 days
—
Too little data (1/1 runs with data)
RT coverage: 1 full · 0 partial · 0 no data
On-time · 90 days
25%
1/4 runs under 3 min
RT coverage: 4 full · 0 partial · 0 no data
Typical delay
—
Needs at least 5 runs with data (4 so far)
P90
—
Needs at least 5 runs with data (4 so far)
Last 30 days
Delay at the end of each run, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Thu 1 Oct Max en route +14 min · last fix heading to — +14 min
- Tue 29 Sept Max en route +12 min · last fix heading to — +12 min
- Wed 23 Sept Max en route +8 min · last fix heading to — +8 min
Distribution · 90 days
4 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 25% · 1
- 3–10 min 25% · 1
- 10–30 min 50% · 2
- 30+ min 0% · 0
On-time by weekday
- — M n=0
- 0% T n=1
- 0% W n=1
- 0% T n=1
- — F n=0
- 100% S n=1
- — S n=0
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Thu 1 Oct | — 17:00 | +14 min | +14 min |
| Tue 29 Sept | — 16:57 | +12 min | +12 min |
| Wed 23 Sept | — 16:54 | +8 min | +8 min |
| Sat 15 Aug | — 16:46 | 0 min | +1 min |
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.