NOR 333
Alerts for train 333
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line NOR.
108,107,332,333: final delay under 3 min on 2 of its 8 runs with data in the last 30 days (25%). Median final delay: +5 min. Running now, 5 min late. TrainsRadar data as of 21 Nov 2026, 06:24 (GMT-5).
An alert on this phone or computer when the 333 is 5 min or more late, every day it runs. No account, no email.
Running now · updated 06:23
Running now +5 min
Today it is running worse than usual: typical arrival delay is +5 min; 25% of the last 8 runs arrived on time.
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 19 Nov Max en route +19 min · last fix heading to septa-rail:1 +12 min
- Sat 21 Nov Max en route +7 min · last fix heading to septa-rail:90007 +5 min
- Fri 20 Nov Max en route +13 min · last fix heading to septa-rail:1 +5 min
- Sat 14 Nov Max en route +13 min · last fix heading to septa-rail:90300 +5 min
- Wed 18 Nov Max en route +25 min · last fix heading to septa-rail:1 +4 min
Distribution · 90 days
8 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 25% · 2
- 3–10 min 63% · 5
- 10–30 min 13% · 1
- 30+ min 0% · 0
On-time by weekday
- — M n=0
- — T n=0
- 67% W n=3
- 0% T n=1
- 0% F n=1
- 0% S n=2
- 0% S n=1
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sat 21 Nov | septa-rail:90007 06:19 | +5 min | +7 min |
| Fri 20 Nov | septa-rail:1 19:13 | +5 min | +13 min |
| Thu 19 Nov | septa-rail:1 22:43 | +12 min | +19 min |
| Wed 18 Nov | septa-rail:1 21:23 | +4 min | +25 min |
| Sun 15 Nov | septa-rail:90300 10:34 | +3 min | +4 min |
| Sat 14 Nov | septa-rail:90300 23:35 | +5 min | +13 min |
| Wed 4 Nov | septa-rail:90220 07:29 | 0 min | — |
| Wed 28 Oct | septa-rail:1 22:18 | 0 min | +6 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 10 July 2026.