Not currently tracked · last seen 3d ago
- Flights observed
- 299 showing last 50
- Avg flight time
- 3h 49m
- Typical route
- HAM → PMI
- Last seen
- 3d ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-26 | PMI → FMO | Jul 26, 20:50 UTC | Jul 26, 23:00 UTC | 2h 10m |
| 2026-07-26 | HAM → PMI | Jul 26, 17:05 UTC | Jul 26, 19:20 UTC | 2h 15m |
| 2026-07-26 | LPA → HAM | Jul 26, 11:30 UTC | Jul 26, 15:45 UTC | 4h 15m |
| 2026-07-26 | DUS → PMI | Jul 26, 05:05 UTC | Jul 26, 09:15 UTC | 4h 11m |
| 2026-07-25 | FUE → HAM | Jul 25, 16:45 UTC | Jul 25, 21:00 UTC | 4h 15m |
| 2026-07-25 | HAM → FUE | Jul 25, 10:30 UTC | Jul 25, 14:45 UTC | 4h 15m |
| 2026-07-25 | BER → LPA | Jul 25, 06:15 UTC | Jul 25, 08:40 UTC | 2h 25m |
| 2026-07-25 | FMO → PMI | Jul 25, 02:45 UTC | Jul 25, 04:55 UTC | 2h 10m |
| 2026-07-24 | PMI → VIE | Jul 24, 20:55 UTC | Jul 24, 23:05 UTC | 2h 10m |
| 2026-07-24 | HAM → PMI | Jul 24, 17:10 UTC | Jul 24, 19:30 UTC | 2h 20m |
| 2026-07-24 | TFS → HAM | Jul 24, 11:40 UTC | Jul 24, 15:50 UTC | 4h 10m |
| 2026-07-24 | HAM → TFS | Jul 24, 04:55 UTC | Jul 24, 09:45 UTC | 4h 50m |
| 2026-07-23 | FUE → HAM | Jul 23, 16:10 UTC | Jul 23, 20:15 UTC | 4h 5m |
| 2026-07-23 | - | Jul 23, 10:05 UTC | Jul 23, 14:15 UTC | 4h 10m |
| 2026-07-23 | PMI → HAM | Jul 23, 06:10 UTC | Jul 23, 08:45 UTC | 2h 35m |
| 2026-07-23 | HAM → PMI | Jul 23, 02:35 UTC | Jul 23, 04:30 UTC | 1h 55m |
| 2026-07-22 | PMI → FMO | Jul 22, 20:55 UTC | Jul 22, 23:10 UTC | 2h 15m |
| 2026-07-22 | DUS → PMI | Jul 22, 17:00 UTC | Jul 22, 19:30 UTC | 2h 30m |
| 2026-07-22 | HAM → HAM | Jul 22, 04:55 UTC | Jul 22, 15:40 UTC | 10h 45m |
| 2026-07-21 | IBZ → PMI | Jul 21, 16:20 UTC | Jul 21, 20:30 UTC | 4h 10m |
| 2026-07-21 | HAM → LPA | Jul 21, 09:50 UTC | Jul 21, 14:10 UTC | 4h 20m |
| 2026-07-21 | PMI → HAM | Jul 21, 06:00 UTC | Jul 21, 08:25 UTC | 2h 25m |
| 2026-07-21 | FMO → PMI | Jul 21, 05:20 UTC | Jul 21, 05:30 UTC | 10m |
| 2026-07-21 | FMO → PMI | Jul 21, 02:35 UTC | Jul 21, 04:35 UTC | 2h 0m |
| 2026-07-20 | PMI → FMO | Jul 20, 21:25 UTC | Jul 20, 23:40 UTC | 2h 15m |
| 2026-07-20 | HAM → PMI | Jul 20, 17:25 UTC | Jul 20, 19:55 UTC | 2h 30m |
| 2026-07-20 | - | Jul 20, 05:35 UTC | Jul 20, 16:20 UTC | 10h 45m |
| 2026-07-19 | TFS → HAM | Jul 19, 16:35 UTC | Jul 19, 20:55 UTC | 4h 20m |
| 2026-07-19 | HAM → TFS | Jul 19, 09:55 UTC | Jul 19, 14:40 UTC | 4h 45m |
| 2026-07-19 | RHO → BER | Jul 19, 06:10 UTC | Jul 19, 08:35 UTC | 2h 25m |
| 2026-07-19 | FMO → PMI | Jul 19, 02:45 UTC | Jul 19, 04:55 UTC | 2h 10m |
| 2026-07-18 | - | Jul 18, 21:40 UTC | Jul 18, 23:50 UTC | 2h 10m |
| 2026-07-18 | FRA → HER | Jul 18, 17:55 UTC | Jul 18, 20:25 UTC | 2h 30m |
| 2026-07-18 | - | Jul 18, 05:00 UTC | Jul 18, 15:40 UTC | 10h 40m |
| 2026-07-17 | - | Jul 17, 16:55 UTC | Jul 17, 21:05 UTC | 4h 10m |
| 2026-07-17 | LPA → HAM | Jul 17, 10:15 UTC | Jul 17, 14:50 UTC | 4h 35m |
| 2026-07-17 | PMI → HAM | Jul 17, 06:20 UTC | Jul 17, 08:35 UTC | 2h 15m |
| 2026-07-17 | HER → MUC | Jul 17, 02:50 UTC | Jul 17, 04:59 UTC | 2h 10m |
| 2026-07-16 | - | Jul 16, 22:25 UTC | Jul 17, 00:25 UTC | 2h 0m |
| 2026-07-16 | - | Jul 16, 18:10 UTC | Jul 16, 20:35 UTC | 2h 25m |
| 2026-07-16 | HAM → HAM | Jul 16, 05:05 UTC | Jul 16, 16:49 UTC | 11h 45m |
| 2026-07-15 | - | Jul 15, 16:20 UTC | Jul 15, 20:25 UTC | 4h 5m |
| 2026-07-15 | - | Jul 15, 10:00 UTC | Jul 15, 14:40 UTC | 4h 40m |
| 2026-07-15 | - | Jul 15, 06:15 UTC | Jul 15, 08:35 UTC | 2h 20m |
| 2026-07-15 | - | Jul 15, 02:40 UTC | Jul 15, 04:45 UTC | 2h 5m |
| 2026-07-14 | - | Jul 14, 21:20 UTC | Jul 14, 23:30 UTC | 2h 9m |
| 2026-07-14 | - | Jul 14, 17:30 UTC | Jul 14, 19:55 UTC | 2h 25m |
| 2026-07-14 | HAM → HAM | Jul 14, 05:40 UTC | Jul 14, 16:10 UTC | 10h 30m |
| 2026-07-13 | - | Jul 13, 16:10 UTC | Jul 13, 19:55 UTC | 3h 45m |
| 2026-07-13 | - | Jul 13, 09:55 UTC | Jul 13, 14:30 UTC | 4h 35m |
Specifications
| Registration | LY-VUT |
| Aircraft type | AIRBUS A-320 (A320) |
| Mode-S code | 503E44 · 24037104 (octal) |
Looking for transponder-level data? View the Mode-S 503E44 page for country allocation, callsign history, and ADS-B signal details.
LY-VUT frequently asked
What type of aircraft is LY-VUT?
LY-VUT is a AIRBUS A-320 (ICAO type code A320).
What is the Mode-S transponder code for LY-VUT?
LY-VUT broadcasts on Mode-S (ICAO 24-bit) address 503E44 (octal 24037104). View the transponder page.
What route does LY-VUT typically fly?
LY-VUT most frequently flies between HAM and PMI based on observed flights.
Where is LY-VUT right now?
LY-VUT is not currently being tracked; last seen 3d ago.