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