Not currently tracked · last seen 17d ago
- Flights observed
- 145 showing last 50
- Avg flight time
- 1h 45m
- Typical route
- AMS → OTP
- Last seen
- 17d ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-26 | FRA → OTP | Jul 26, 18:05 UTC | Jul 26, 19:55 UTC | 1h 50m |
| 2026-07-26 | OTP → FRA | Jul 26, 14:30 UTC | Jul 26, 16:40 UTC | 2h 10m |
| 2026-07-26 | AMS → OTP | Jul 26, 10:20 UTC | Jul 26, 12:40 UTC | 2h 20m |
| 2026-07-26 | OTP → AMS | Jul 26, 06:20 UTC | Jul 26, 08:50 UTC | 2h 31m |
| 2026-07-25 | AMS → OTP | Jul 25, 10:15 UTC | Jul 25, 12:35 UTC | 2h 20m |
| 2026-07-25 | OTP → AMS | Jul 25, 06:10 UTC | Jul 25, 08:45 UTC | 2h 35m |
| 2026-07-24 | AMS → OTP | Jul 24, 19:50 UTC | Jul 24, 21:55 UTC | 2h 5m |
| 2026-07-24 | OTP → AMS | Jul 24, 15:00 UTC | Jul 24, 17:35 UTC | 2h 35m |
| 2026-07-24 | ATH → OTP | Jul 24, 12:30 UTC | Jul 24, 13:35 UTC | 1h 5m |
| 2026-07-24 | OTP → ATH | Jul 24, 09:25 UTC | Jul 24, 10:50 UTC | 1h 25m |
| 2026-07-23 | CLJ → OTP | Jul 23, 17:25 UTC | Jul 23, 18:00 UTC | 35m |
| 2026-07-23 | OTP → CLJ | Jul 23, 15:45 UTC | Jul 23, 16:15 UTC | 30m |
| 2026-07-23 | MAD → OTP | Jul 23, 11:05 UTC | Jul 23, 14:05 UTC | 3h 0m |
| 2026-07-23 | OTP → MAD | Jul 23, 05:40 UTC | Jul 23, 09:15 UTC | 3h 35m |
| 2026-07-22 | ATH → OTP | Jul 22, 16:35 UTC | Jul 22, 17:45 UTC | 1h 10m |
| 2026-07-22 | OTP → ATH | Jul 22, 14:00 UTC | Jul 22, 15:20 UTC | 1h 20m |
| 2026-07-21 | TSR → OTP | Jul 21, 11:35 UTC | Jul 21, 12:10 UTC | 35m |
| 2026-07-21 | OTP → TSR | Jul 21, 10:00 UTC | Jul 21, 10:30 UTC | 30m |
| 2026-07-20 | ATH → OTP | Jul 20, 16:10 UTC | Jul 20, 17:15 UTC | 1h 5m |
| 2026-07-20 | OTP → ATH | Jul 20, 13:15 UTC | Jul 20, 14:30 UTC | 1h 15m |
| 2026-07-20 | FRA → OTP | Jul 20, 09:40 UTC | Jul 20, 11:30 UTC | 1h 50m |
| 2026-07-20 | OTP → FRA | Jul 20, 05:45 UTC | Jul 20, 08:00 UTC | 2h 15m |
| 2026-07-19 | ATH → OTP | Jul 19, 19:25 UTC | Jul 19, 20:30 UTC | 1h 5m |
| 2026-07-19 | OTP → ATH | Jul 19, 16:40 UTC | Jul 19, 18:05 UTC | 1h 25m |
| 2026-07-19 | AMS → OTP | Jul 19, 10:45 UTC | Jul 19, 13:00 UTC | 2h 15m |
| 2026-07-19 | OTP → AMS | Jul 19, 05:45 UTC | Jul 19, 08:20 UTC | 2h 35m |
| 2026-07-18 | AMS → OTP | Jul 18, 10:05 UTC | Jul 18, 12:15 UTC | 2h 10m |
| 2026-07-18 | OTP → AMS | Jul 18, 05:55 UTC | Jul 18, 08:35 UTC | 2h 40m |
| 2026-07-17 | - | Jul 17, 18:40 UTC | Jul 17, 20:55 UTC | 2h 15m |
| 2026-07-17 | - | Jul 17, 14:30 UTC | Jul 17, 17:05 UTC | 2h 35m |
| 2026-07-16 | - | Jul 16, 18:10 UTC | Jul 16, 18:44 UTC | 35m |
| 2026-07-16 | - | Jul 16, 16:35 UTC | Jul 16, 17:10 UTC | 35m |
| 2026-07-16 | - | Jul 16, 12:05 UTC | Jul 16, 15:10 UTC | 3h 5m |
| 2026-07-16 | - | Jul 16, 06:20 UTC | Jul 16, 10:10 UTC | 3h 50m |
| 2026-07-15 | MLA → OTP | Jul 15, 12:40 UTC | Jul 15, 14:35 UTC | 1h 55m |
| 2026-07-14 | ZRH → MLA | Jul 14, 18:00 UTC | Jul 14, 19:55 UTC | 1h 55m |
| 2026-07-14 | MLA → ZRH | Jul 14, 14:35 UTC | Jul 14, 16:40 UTC | 2h 5m |
| 2026-07-14 | VIE → MLA | Jul 14, 10:55 UTC | Jul 14, 12:45 UTC | 1h 50m |
| 2026-07-14 | MLA → VIE | Jul 14, 07:40 UTC | Jul 14, 09:40 UTC | 2h 0m |
| 2026-07-13 | - | Jul 13, 19:25 UTC | Jul 13, 20:35 UTC | 1h 10m |
| 2026-07-13 | MLA → FCO | Jul 13, 16:40 UTC | Jul 13, 17:50 UTC | 1h 10m |
| 2026-07-13 | LIN → MLA | Jul 13, 13:45 UTC | Jul 13, 15:20 UTC | 1h 35m |
| 2026-07-13 | MLA → LIN | Jul 13, 10:50 UTC | Jul 13, 12:30 UTC | 1h 40m |
| 2026-07-13 | - | Jul 13, 08:15 UTC | Jul 13, 09:20 UTC | 1h 5m |
| 2026-07-13 | - | Jul 13, 05:10 UTC | Jul 13, 06:25 UTC | 1h 15m |
| 2026-07-12 | LIN → MLA | Jul 12, 19:05 UTC | Jul 12, 20:30 UTC | 1h 25m |
| 2026-07-12 | MLA → LIN | Jul 12, 16:15 UTC | Jul 12, 18:01 UTC | 1h 45m |
| 2026-07-12 | - | Jul 12, 14:10 UTC | Jul 12, 15:05 UTC | 55m |
| 2026-07-12 | - | Jul 12, 11:25 UTC | Jul 12, 12:35 UTC | 1h 10m |
| 2026-07-12 | - | Jul 12, 08:35 UTC | Jul 12, 09:35 UTC | 1h 0m |
Specifications
| Registration | LY-NVJ |
| Aircraft type | AIRBUS A-320 (A320) |
| Mode-S code | 503CFF · 24036377 (octal) |
Looking for transponder-level data? View the Mode-S 503CFF page for country allocation, callsign history, and ADS-B signal details.
LY-NVJ frequently asked
What type of aircraft is LY-NVJ?
LY-NVJ is a AIRBUS A-320 (ICAO type code A320).
What is the Mode-S transponder code for LY-NVJ?
LY-NVJ broadcasts on Mode-S (ICAO 24-bit) address 503CFF (octal 24036377). View the transponder page.
What route does LY-NVJ typically fly?
LY-NVJ most frequently flies between AMS and OTP based on observed flights.
Where is LY-NVJ right now?
LY-NVJ is not currently being tracked; last seen 17d ago.