Not currently tracked · last seen 8h ago
- Flights observed
- 463 showing last 50
- Avg flight time
- 2h 4m
- Typical route
- NCL → BFS
- Last seen
- 8h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-13 | GVA → LGW | Jul 13, 19:30 UTC | Jul 13, 20:45 UTC | 1h 15m |
| 2026-07-13 | LGW → GVA | Jul 13, 17:15 UTC | Jul 13, 18:25 UTC | 1h 10m |
| 2026-07-13 | ZRH → LGW | Jul 13, 14:00 UTC | Jul 13, 15:30 UTC | 1h 30m |
| 2026-07-13 | LGW → ZRH | Jul 13, 11:50 UTC | Jul 13, 13:05 UTC | 1h 15m |
| 2026-07-13 | VCE → LGW | Jul 13, 07:55 UTC | Jul 13, 09:40 UTC | 1h 45m |
| 2026-07-13 | LGW → VCE | Jul 13, 05:15 UTC | Jul 13, 06:50 UTC | 1h 35m |
| 2026-07-12 | - | Jul 12, 22:45 UTC | Jul 13, 02:35 UTC | 3h 50m |
| 2026-07-12 | - | Jul 12, 17:35 UTC | Jul 12, 21:00 UTC | 3h 25m |
| 2026-07-12 | - | Jul 12, 13:20 UTC | Jul 12, 15:30 UTC | 2h 10m |
| 2026-07-12 | - | Jul 12, 09:55 UTC | Jul 12, 11:50 UTC | 1h 55m |
| 2026-07-12 | - | Jul 12, 07:20 UTC | Jul 12, 08:35 UTC | 1h 15m |
| 2026-07-12 | NCL → BFS | Jul 12, 06:01 UTC | Jul 12, 06:40 UTC | 40m |
| 2026-07-11 | - | Jul 11, 21:25 UTC | Jul 11, 23:50 UTC | 2h 25m |
| 2026-07-11 | - | Jul 11, 17:55 UTC | Jul 11, 20:25 UTC | 2h 30m |
| 2026-07-11 | RHO → NCL | Jul 11, 12:30 UTC | Jul 11, 16:35 UTC | 4h 5m |
| 2026-07-11 | - | Jul 11, 11:55 UTC | Jul 11, 12:15 UTC | 20m |
| 2026-07-11 | NCL → RHO | Jul 11, 07:00 UTC | Jul 11, 11:00 UTC | 4h 0m |
| 2026-07-10 | LIS → NCL | Jul 10, 19:15 UTC | Jul 10, 21:45 UTC | 2h 31m |
| 2026-07-10 | NCL → LIS | Jul 10, 14:55 UTC | Jul 10, 17:30 UTC | 2h 35m |
| 2026-07-10 | - | Jul 10, 10:10 UTC | Jul 10, 12:45 UTC | 2h 35m |
| 2026-07-10 | - | Jul 10, 06:35 UTC | Jul 10, 09:10 UTC | 2h 35m |
| 2026-07-09 | - | Jul 9, 18:10 UTC | Jul 9, 20:45 UTC | 2h 35m |
| 2026-07-09 | - | Jul 9, 14:10 UTC | Jul 9, 16:55 UTC | 2h 45m |
| 2026-07-09 | FAO → NCL | Jul 9, 10:05 UTC | Jul 9, 12:45 UTC | 2h 40m |
| 2026-07-09 | NCL → FAO | Jul 9, 06:30 UTC | Jul 9, 09:15 UTC | 2h 45m |
| 2026-07-08 | - | Jul 8, 18:55 UTC | Jul 8, 19:30 UTC | 35m |
| 2026-07-08 | NCL → BFS | Jul 8, 17:30 UTC | Jul 8, 18:00 UTC | 30m |
| 2026-07-08 | - | Jul 8, 11:40 UTC | Jul 8, 14:05 UTC | 2h 25m |
| 2026-07-08 | - | Jul 8, 08:00 UTC | Jul 8, 10:20 UTC | 2h 20m |
| 2026-07-07 | NCE → NCL | Jul 7, 21:35 UTC | Jul 7, 23:45 UTC | 2h 10m |
| 2026-07-07 | NCL → NCE | Jul 7, 18:05 UTC | Jul 7, 20:10 UTC | 2h 5m |
| 2026-07-07 | RHO → NCL | Jul 7, 12:50 UTC | Jul 7, 17:15 UTC | 4h 25m |
| 2026-07-07 | NCL → RHO | Jul 7, 07:30 UTC | Jul 7, 11:10 UTC | 3h 40m |
| 2026-07-06 | BRS → NCL | Jul 6, 19:20 UTC | Jul 6, 20:05 UTC | 45m |
| 2026-07-06 | NCL → BRS | Jul 6, 17:30 UTC | Jul 6, 18:15 UTC | 45m |
| 2026-07-06 | - | Jul 6, 16:00 UTC | Jul 6, 16:35 UTC | 35m |
| 2026-07-06 | NCL → BFS | Jul 6, 14:15 UTC | Jul 6, 14:55 UTC | 40m |
| 2026-07-06 | - | Jul 6, 11:45 UTC | Jul 6, 13:00 UTC | 1h 15m |
| 2026-07-06 | NCL → CDG | Jul 6, 09:25 UTC | Jul 6, 10:35 UTC | 1h 10m |
| 2026-07-06 | BRS → NCL | Jul 6, 07:45 UTC | Jul 6, 08:30 UTC | 45m |
| 2026-07-06 | NCL → BRS | Jul 6, 06:00 UTC | Jul 6, 06:45 UTC | 45m |
| 2026-07-05 | NCE → NCL | Jul 5, 19:55 UTC | Jul 5, 22:05 UTC | 2h 10m |
| 2026-07-05 | NCL → NCE | Jul 5, 16:50 UTC | Jul 5, 18:50 UTC | 2h 0m |
| 2026-07-05 | - | Jul 5, 14:45 UTC | Jul 5, 15:55 UTC | 1h 10m |
| 2026-07-05 | NCL → AMS | Jul 5, 12:40 UTC | Jul 5, 13:40 UTC | 1h 0m |
| 2026-07-05 | FAO → NCL | Jul 5, 08:35 UTC | Jul 5, 11:30 UTC | 2h 55m |
| 2026-07-05 | NCL → FAO | Jul 5, 04:50 UTC | Jul 5, 07:35 UTC | 2h 45m |
| 2026-07-04 | - | Jul 4, 19:50 UTC | Jul 5, 00:10 UTC | 4h 20m |
| 2026-07-04 | - | Jul 4, 15:00 UTC | Jul 4, 18:05 UTC | 3h 5m |
| 2026-07-04 | - | Jul 4, 10:30 UTC | Jul 4, 13:25 UTC | 2h 55m |
Specifications
| Registration | G-EZUL |
| Aircraft type | AIRBUS A-320 (A320) |
| Mode-S code | 406666 · 20063146 (octal) |
Looking for transponder-level data? View the Mode-S 406666 page for country allocation, callsign history, and ADS-B signal details.
G-EZUL frequently asked
What type of aircraft is G-EZUL?
G-EZUL is a AIRBUS A-320 (ICAO type code A320).
What is the Mode-S transponder code for G-EZUL?
G-EZUL broadcasts on Mode-S (ICAO 24-bit) address 406666 (octal 20063146). View the transponder page.
What route does G-EZUL typically fly?
G-EZUL most frequently flies between NCL and BFS based on observed flights.
Where is G-EZUL right now?
G-EZUL is not currently being tracked; last seen 8h ago.