Airborne now · flying as CFG3UY at 36,000 ft
- Flights observed
- 143 showing last 50
- Avg flight time
- 3h 45m
- Typical route
- HAM → PMI
- Last seen
- 1h ago
Live position
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-06-14 | PMI → FMO | Jun 14, 20:35 UTC | Jun 14, 21:00 UTC | 25m |
| 2026-06-14 | HAM → PMI | Jun 14, 17:00 UTC | Jun 14, 19:15 UTC | 2h 15m |
| 2026-06-14 | LPA → HAM | Jun 14, 11:20 UTC | Jun 14, 15:25 UTC | 4h 5m |
| 2026-06-14 | DUS → PMI | Jun 14, 04:55 UTC | Jun 14, 09:25 UTC | 4h 30m |
| 2026-06-13 | PMI → DUS | Jun 13, 17:35 UTC | Jun 13, 20:30 UTC | 2h 55m |
| 2026-06-13 | STR → FUE | Jun 13, 13:25 UTC | Jun 13, 16:30 UTC | 3h 5m |
| 2026-06-13 | BER → LPA | Jun 13, 06:20 UTC | Jun 13, 08:40 UTC | 2h 20m |
| 2026-06-13 | FMO → PMI | Jun 13, 02:45 UTC | Jun 13, 04:45 UTC | 1h 59m |
| 2026-06-12 | PMI → VIE | Jun 12, 21:00 UTC | Jun 12, 23:15 UTC | 2h 15m |
| 2026-06-12 | HAM → PMI | Jun 12, 16:50 UTC | Jun 12, 19:00 UTC | 2h 10m |
| 2026-06-12 | TFS → HAM | Jun 12, 11:10 UTC | Jun 12, 15:25 UTC | 4h 15m |
| 2026-06-12 | HAM → TFS | Jun 12, 04:50 UTC | Jun 12, 09:20 UTC | 4h 30m |
| 2026-06-11 | FUE → HAM | Jun 11, 17:05 UTC | Jun 11, 21:25 UTC | 4h 20m |
| 2026-06-11 | - | Jun 11, 10:25 UTC | Jun 11, 14:45 UTC | 4h 20m |
| 2026-06-11 | - | Jun 11, 06:15 UTC | Jun 11, 08:55 UTC | 2h 40m |
| 2026-06-11 | HAM → PMI | Jun 11, 02:50 UTC | Jun 11, 04:45 UTC | 1h 55m |
| 2026-06-10 | PMI → FMO | Jun 10, 20:45 UTC | Jun 10, 23:05 UTC | 2h 20m |
| 2026-06-10 | DUS → PMI | Jun 10, 16:55 UTC | Jun 10, 19:15 UTC | 2h 20m |
| 2026-06-10 | HAM → HAM | Jun 10, 05:00 UTC | Jun 10, 15:40 UTC | 10h 40m |
| 2026-06-09 | IBZ → PMI | Jun 9, 17:15 UTC | Jun 9, 20:25 UTC | 3h 10m |
| 2026-06-09 | HAM → LPA | Jun 9, 09:45 UTC | Jun 9, 14:20 UTC | 4h 35m |
| 2026-06-09 | - | Jun 9, 06:00 UTC | Jun 9, 08:20 UTC | 2h 20m |
| 2026-06-09 | FMO → PMI | Jun 9, 02:35 UTC | Jun 9, 04:45 UTC | 2h 10m |
| 2026-06-08 | PMI → FMO | Jun 8, 21:40 UTC | Jun 8, 23:40 UTC | 2h 0m |
| 2026-06-08 | HAM → PMI | Jun 8, 19:30 UTC | Jun 8, 20:15 UTC | 45m |
| 2026-06-08 | - | Jun 8, 05:05 UTC | Jun 8, 16:05 UTC | 11h 0m |
| 2026-06-07 | TFS → HAM | Jun 7, 16:00 UTC | Jun 7, 20:25 UTC | 4h 25m |
| 2026-06-07 | HAM → TFS | Jun 7, 09:50 UTC | Jun 7, 14:10 UTC | 4h 20m |
| 2026-06-07 | RHO → BER | Jun 7, 06:15 UTC | Jun 7, 08:35 UTC | 2h 20m |
| 2026-06-07 | FMO → PMI | Jun 7, 02:40 UTC | Jun 7, 04:55 UTC | 2h 15m |
| 2026-06-06 | PMI → HAM | Jun 6, 20:45 UTC | Jun 6, 22:55 UTC | 2h 10m |
| 2026-06-06 | FRA → HER | Jun 6, 17:00 UTC | Jun 6, 19:24 UTC | 2h 25m |
| 2026-06-06 | HAM → HAM | Jun 6, 05:00 UTC | Jun 6, 15:44 UTC | 10h 45m |
| 2026-06-05 | - | Jun 5, 16:00 UTC | Jun 5, 20:20 UTC | 4h 20m |
| 2026-06-05 | LPA → HAM | Jun 5, 10:00 UTC | Jun 5, 14:40 UTC | 4h 40m |
| 2026-06-05 | PMI → HAM | Jun 5, 06:25 UTC | Jun 5, 08:40 UTC | 2h 15m |
| 2026-06-05 | HER → MUC | Jun 5, 03:10 UTC | Jun 5, 05:20 UTC | 2h 10m |
| 2026-06-04 | MUC → TFS | Jun 4, 21:05 UTC | Jun 4, 23:15 UTC | 2h 10m |
| 2026-06-04 | HAM → PMI | Jun 4, 17:10 UTC | Jun 4, 19:50 UTC | 2h 40m |
| 2026-06-04 | HAM → HAM | Jun 4, 04:55 UTC | Jun 4, 15:55 UTC | 11h 0m |
| 2026-06-03 | TFS → HAM | Jun 3, 16:35 UTC | Jun 3, 20:45 UTC | 4h 10m |
| 2026-06-03 | HAM → TFS | Jun 3, 10:10 UTC | Jun 3, 14:45 UTC | 4h 35m |
| 2026-06-03 | PMI → FRA | Jun 3, 06:10 UTC | Jun 3, 08:45 UTC | 2h 35m |
| 2026-06-03 | - | Jun 3, 02:40 UTC | Jun 3, 04:40 UTC | 2h 0m |
| 2026-06-02 | PMI → FMO | Jun 2, 21:10 UTC | Jun 2, 23:30 UTC | 2h 20m |
| 2026-06-02 | HAM → PMI | Jun 2, 17:05 UTC | Jun 2, 19:35 UTC | 2h 30m |
| 2026-06-02 | HAM → HAM | Jun 2, 04:55 UTC | Jun 2, 15:40 UTC | 10h 45m |
| 2026-06-01 | IBZ → PMI | Jun 1, 16:10 UTC | Jun 1, 20:20 UTC | 4h 10m |
| 2026-06-01 | HAM → FUE | Jun 1, 10:15 UTC | Jun 1, 14:35 UTC | 4h 20m |
| 2026-06-01 | PMI → HAM | Jun 1, 06:15 UTC | Jun 1, 08:50 UTC | 2h 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 currently airborne flying as CFG3UY. Live position is shown on the map above.