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