Not currently tracked · last seen 5h ago
- Flights observed
- 436 showing last 50
- Avg flight time
- 2h 44m
- Typical route
- OPO → OPO
- Last seen
- 5h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-13 | GVA → OPO | Jul 13, 19:35 UTC | Jul 13, 21:40 UTC | 2h 5m |
| 2026-07-13 | OPO → GVA | Jul 13, 16:50 UTC | Jul 13, 18:35 UTC | 1h 45m |
| 2026-07-13 | IBZ → OPO | Jul 13, 14:20 UTC | Jul 13, 15:50 UTC | 1h 30m |
| 2026-07-13 | OPO → IBZ | Jul 13, 11:55 UTC | Jul 13, 13:20 UTC | 1h 25m |
| 2026-07-13 | - | Jul 13, 08:40 UTC | Jul 13, 10:25 UTC | 1h 45m |
| 2026-07-13 | - | Jul 13, 06:05 UTC | Jul 13, 07:05 UTC | 1h 0m |
| 2026-07-12 | - | Jul 12, 20:40 UTC | Jul 12, 22:10 UTC | 1h 30m |
| 2026-07-12 | - | Jul 12, 18:01 UTC | Jul 12, 19:01 UTC | 1h 0m |
| 2026-07-12 | OPO → OPO | Jul 12, 06:35 UTC | Jul 12, 16:01 UTC | 9h 25m |
| 2026-07-11 | LGW → OPO | Jul 11, 19:30 UTC | Jul 11, 21:20 UTC | 1h 50m |
| 2026-07-11 | OPO → LGW | Jul 11, 16:40 UTC | Jul 11, 18:30 UTC | 1h 50m |
| 2026-07-11 | OPO → OPO | Jul 11, 06:15 UTC | Jul 11, 15:20 UTC | 9h 5m |
| 2026-07-10 | GVA → OPO | Jul 10, 20:25 UTC | Jul 10, 22:20 UTC | 1h 55m |
| 2026-07-10 | OPO → GVA | Jul 10, 17:00 UTC | Jul 10, 19:00 UTC | 2h 0m |
| 2026-07-10 | MAH → OPO | Jul 10, 14:25 UTC | Jul 10, 16:05 UTC | 1h 40m |
| 2026-07-10 | OPO → MAH | Jul 10, 11:45 UTC | Jul 10, 13:30 UTC | 1h 45m |
| 2026-07-10 | FNC → OPO | Jul 10, 08:05 UTC | Jul 10, 09:40 UTC | 1h 35m |
| 2026-07-10 | - | Jul 10, 07:10 UTC | Jul 10, 07:15 UTC | 5m |
| 2026-07-10 | - | Jul 10, 05:30 UTC | Jul 10, 06:30 UTC | 1h 0m |
| 2026-07-09 | FNC → OPO | Jul 9, 19:35 UTC | Jul 9, 21:20 UTC | 1h 45m |
| 2026-07-09 | - | Jul 9, 18:25 UTC | Jul 9, 18:30 UTC | 5m |
| 2026-07-09 | - | Jul 9, 16:50 UTC | Jul 9, 17:50 UTC | 1h 0m |
| 2026-07-09 | OPO → OPO | Jul 9, 06:15 UTC | Jul 9, 15:15 UTC | 9h 0m |
| 2026-07-08 | OPO → OPO | Jul 8, 12:25 UTC | Jul 8, 21:15 UTC | 8h 50m |
| 2026-07-08 | LGW → OPO | Jul 8, 09:25 UTC | Jul 8, 11:15 UTC | 1h 50m |
| 2026-07-08 | OPO → LGW | Jul 8, 06:15 UTC | Jul 8, 08:15 UTC | 2h 0m |
| 2026-07-07 | - | Jul 7, 19:30 UTC | Jul 7, 21:30 UTC | 2h 0m |
| 2026-07-07 | - | Jul 7, 16:05 UTC | Jul 7, 18:15 UTC | 2h 10m |
| 2026-07-07 | OPO → OPO | Jul 7, 06:00 UTC | Jul 7, 15:05 UTC | 9h 5m |
| 2026-07-06 | - | Jul 6, 19:55 UTC | Jul 6, 21:55 UTC | 2h 0m |
| 2026-07-06 | - | Jul 6, 16:30 UTC | Jul 6, 18:40 UTC | 2h 10m |
| 2026-07-06 | OPO → OPO | Jul 6, 06:20 UTC | Jul 6, 15:25 UTC | 9h 5m |
| 2026-07-05 | OPO → OPO | Jul 5, 12:45 UTC | Jul 5, 21:30 UTC | 8h 45m |
| 2026-07-05 | BSL → OPO | Jul 5, 09:30 UTC | Jul 5, 11:40 UTC | 2h 10m |
| 2026-07-05 | - | Jul 5, 06:30 UTC | Jul 5, 08:40 UTC | 2h 10m |
| 2026-07-04 | LYS → OPO | Jul 4, 20:20 UTC | Jul 4, 22:05 UTC | 1h 45m |
| 2026-07-04 | OPO → LYS | Jul 4, 17:40 UTC | Jul 4, 19:25 UTC | 1h 45m |
| 2026-07-04 | - | Jul 4, 14:20 UTC | Jul 4, 16:30 UTC | 2h 10m |
| 2026-07-04 | OPO → BSL | Jul 4, 11:10 UTC | Jul 4, 13:15 UTC | 2h 5m |
| 2026-07-04 | FNC → OPO | Jul 4, 08:10 UTC | Jul 4, 09:50 UTC | 1h 40m |
| 2026-07-04 | OPO → FNC | Jul 4, 07:10 UTC | Jul 4, 07:15 UTC | 5m |
| 2026-07-04 | OPO → FNC | Jul 4, 05:35 UTC | Jul 4, 06:40 UTC | 1h 5m |
| 2026-07-03 | FNC → OPO | Jul 3, 20:55 UTC | Jul 3, 22:30 UTC | 1h 35m |
| 2026-07-03 | - | Jul 3, 18:25 UTC | Jul 3, 19:20 UTC | 55m |
| 2026-07-03 | FNC → OPO | Jul 3, 15:50 UTC | Jul 3, 17:25 UTC | 1h 35m |
| 2026-07-03 | - | Jul 3, 14:50 UTC | Jul 3, 15:00 UTC | 10m |
| 2026-07-03 | - | Jul 3, 13:15 UTC | Jul 3, 14:15 UTC | 1h 0m |
| 2026-07-03 | LGW → OPO | Jul 3, 09:40 UTC | Jul 3, 11:30 UTC | 1h 50m |
| 2026-07-03 | OPO → LGW | Jul 3, 05:55 UTC | Jul 3, 08:00 UTC | 2h 5m |
| 2026-07-02 | OPO → OPO | Jul 2, 11:45 UTC | Jul 2, 20:20 UTC | 8h 35m |
Specifications
| Registration | OE-LUG |
| Aircraft type | AIRBUS A-320neo (A20N) |
| Mode-S code | 440224 · 21001044 (octal) |
Looking for transponder-level data? View the Mode-S 440224 page for country allocation, callsign history, and ADS-B signal details.
OE-LUG frequently asked
What type of aircraft is OE-LUG?
OE-LUG is a AIRBUS A-320neo (ICAO type code A20N).
What is the Mode-S transponder code for OE-LUG?
OE-LUG broadcasts on Mode-S (ICAO 24-bit) address 440224 (octal 21001044). View the transponder page.
What route does OE-LUG typically fly?
OE-LUG most frequently flies between OPO and OPO based on observed flights.
Where is OE-LUG right now?
OE-LUG is not currently being tracked; last seen 5h ago.