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