RJ 201030 201030
View line RJ 201030
Alerts for train 201030
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line RJ 201030.
Not running right now
Last recorded run: Sunday 4 October −16 min
The mini-map returns when the train runs
On-time · 30 days
—
Too little data (0/0 runs with data)
RT coverage: 0 full · 0 partial · 0 no data
On-time · 90 days
75%
3/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
- Sat 26 Sept Max en route +112 min · last fix heading to — +112 min
Distribution · 90 days
4 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 50% · 2
- On time 25% · 1
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 25% · 1
On-time by weekday
- 100% M n=1
- — T n=0
- — W n=0
- — T n=0
- — F n=0
- 50% S n=2
- 100% S n=1
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sun 4 Oct | — 11:13 | −16 min | — |
| Sat 3 Oct | — 11:25 | −10 min | — |
| Mon 28 Sept | — 11:42 | +1 min | +1 min |
| Sat 26 Sept | — 13:37 | +112 min | +112 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.