Not currently tracked · last seen 2h ago
- Flights observed
- 210 showing last 50
- Avg flight time
- 1h 58m
- Typical route
- BUD → LHR
- Last seen
- 2h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-06-15 | LUX → LHR | Jun 15, 19:05 UTC | Jun 15, 20:04 UTC | 1h 0m |
| 2026-06-15 | LHR → LUX | Jun 15, 17:20 UTC | Jun 15, 18:10 UTC | 50m |
| 2026-06-15 | GOT → LHR | Jun 15, 13:15 UTC | Jun 15, 15:19 UTC | 2h 5m |
| 2026-06-15 | GOT → LHR | Jun 15, 10:30 UTC | Jun 15, 12:00 UTC | 1h 30m |
| 2026-06-15 | - | Jun 15, 05:30 UTC | Jun 15, 09:00 UTC | 3h 30m |
| 2026-06-14 | - | Jun 14, 18:45 UTC | Jun 14, 21:15 UTC | 2h 30m |
| 2026-06-14 | GIB → LHR | Jun 14, 14:40 UTC | Jun 14, 17:10 UTC | 2h 30m |
| 2026-06-14 | LHR → GIB | Jun 14, 11:10 UTC | Jun 14, 13:45 UTC | 2h 35m |
| 2026-06-14 | LED → LHR | Jun 14, 06:05 UTC | Jun 14, 09:25 UTC | 3h 20m |
| 2026-06-13 | - | Jun 13, 18:00 UTC | Jun 13, 20:30 UTC | 2h 30m |
| 2026-06-13 | BUD → LHR | Jun 13, 15:10 UTC | Jun 13, 16:25 UTC | 1h 15m |
| 2026-06-13 | - | Jun 13, 13:00 UTC | Jun 13, 14:05 UTC | 1h 5m |
| 2026-06-13 | NCE → LHR | Jun 13, 09:45 UTC | Jun 13, 11:25 UTC | 1h 40m |
| 2026-06-13 | LHR → NCE | Jun 13, 06:30 UTC | Jun 13, 07:55 UTC | 1h 25m |
| 2026-06-12 | LIN → LHR | Jun 12, 19:35 UTC | Jun 12, 21:45 UTC | 2h 10m |
| 2026-06-12 | VCE → LHR | Jun 12, 16:20 UTC | Jun 12, 18:05 UTC | 1h 45m |
| 2026-06-12 | ZAG → LHR | Jun 12, 12:10 UTC | Jun 12, 14:20 UTC | 2h 10m |
| 2026-06-12 | LHR → ZAG | Jun 12, 09:10 UTC | Jun 12, 10:50 UTC | 1h 40m |
| 2026-06-12 | NCE → LHR | Jun 12, 05:45 UTC | Jun 12, 07:30 UTC | 1h 45m |
| 2026-06-11 | - | Jun 11, 20:00 UTC | Jun 11, 21:20 UTC | 1h 20m |
| 2026-06-11 | MRS → LHR | Jun 11, 16:35 UTC | Jun 11, 18:15 UTC | 1h 40m |
| 2026-06-11 | LHR → MRS | Jun 11, 13:55 UTC | Jun 11, 15:10 UTC | 1h 15m |
| 2026-06-11 | BUD → LHR | Jun 11, 10:50 UTC | Jun 11, 12:00 UTC | 1h 10m |
| 2026-06-11 | LHR → OTP | Jun 11, 08:35 UTC | Jun 11, 09:40 UTC | 1h 5m |
| 2026-06-10 | BUD → LHR | Jun 10, 16:40 UTC | Jun 10, 19:20 UTC | 2h 40m |
| 2026-06-10 | LHR → BUD | Jun 10, 13:25 UTC | Jun 10, 15:20 UTC | 1h 55m |
| 2026-06-10 | CAI → LHR | Jun 10, 09:50 UTC | Jun 10, 12:00 UTC | 2h 10m |
| 2026-06-10 | LHR → CAI | Jun 10, 06:25 UTC | Jun 10, 08:15 UTC | 1h 50m |
| 2026-06-09 | ZAG → LHR | Jun 9, 19:00 UTC | Jun 9, 21:00 UTC | 2h 0m |
| 2026-06-09 | LHR → ZAG | Jun 9, 16:45 UTC | Jun 9, 17:40 UTC | 55m |
| 2026-06-09 | NCE → LHR | Jun 9, 13:00 UTC | Jun 9, 14:30 UTC | 1h 30m |
| 2026-06-09 | LHR → NCE | Jun 9, 09:25 UTC | Jun 9, 10:50 UTC | 1h 25m |
| 2026-06-09 | GVA → LHR | Jun 9, 05:55 UTC | Jun 9, 08:00 UTC | 2h 5m |
| 2026-06-08 | LHR → GVA | Jun 8, 18:35 UTC | Jun 8, 20:20 UTC | 1h 45m |
| 2026-06-08 | IST → LHR | Jun 8, 12:10 UTC | Jun 8, 15:10 UTC | 3h 0m |
| 2026-06-08 | PVK → LHR | Jun 8, 07:40 UTC | Jun 8, 10:10 UTC | 2h 30m |
| 2026-06-07 | LIS → LHR | Jun 7, 18:20 UTC | Jun 7, 20:30 UTC | 2h 10m |
| 2026-06-07 | LHR → FAO | Jun 7, 14:55 UTC | Jun 7, 17:05 UTC | 2h 10m |
| 2026-06-07 | IST → LHR | Jun 7, 10:15 UTC | Jun 7, 13:15 UTC | 3h 0m |
| 2026-06-07 | PVK → LHR | Jun 7, 05:40 UTC | Jun 7, 08:00 UTC | 2h 20m |
| 2026-06-06 | VIE → LHR | Jun 6, 16:04 UTC | Jun 6, 19:54 UTC | 3h 50m |
| 2026-06-06 | LHR → VIE | Jun 6, 11:14 UTC | Jun 6, 14:20 UTC | 3h 5m |
| 2026-06-06 | SPU → LHR | Jun 6, 06:25 UTC | Jun 6, 08:50 UTC | 2h 25m |
| 2026-06-05 | LHR → SPU | Jun 5, 17:35 UTC | Jun 5, 19:40 UTC | 2h 5m |
| 2026-06-05 | TFS → LHR | Jun 5, 13:25 UTC | Jun 5, 15:35 UTC | 2h 10m |
| 2026-06-05 | LHR → TFS | Jun 5, 10:30 UTC | Jun 5, 12:25 UTC | 1h 55m |
| 2026-06-05 | - | Jun 5, 07:00 UTC | Jun 5, 08:25 UTC | 1h 25m |
| 2026-06-04 | - | Jun 4, 20:25 UTC | Jun 4, 21:30 UTC | 1h 5m |
| 2026-06-04 | PSA → LHR | Jun 4, 15:50 UTC | Jun 4, 17:45 UTC | 1h 55m |
| 2026-06-04 | LHR → PSA | Jun 4, 12:50 UTC | Jun 4, 14:20 UTC | 1h 30m |
Specifications
| Registration | G-EUYI |
| Aircraft type | AIRBUS A-320 (A320) |
| Mode-S code | 406250 · 20061120 (octal) |
Looking for transponder-level data? View the Mode-S 406250 page for country allocation, callsign history, and ADS-B signal details.
G-EUYI frequently asked
What type of aircraft is G-EUYI?
G-EUYI is a AIRBUS A-320 (ICAO type code A320).
What is the Mode-S transponder code for G-EUYI?
G-EUYI broadcasts on Mode-S (ICAO 24-bit) address 406250 (octal 20061120). View the transponder page.
What route does G-EUYI typically fly?
G-EUYI most frequently flies between BUD and LHR based on observed flights.
Where is G-EUYI right now?
G-EUYI is not currently being tracked; last seen 2h ago.