Not currently tracked · last seen Jul 26, 21:05 UTC
- Flights observed
- 560 showing last 50
- Avg flight time
- 1h 29m
- Typical route
- BOD → GVA
- Last seen
- Jul 26, 21:05 UTC
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-26 | SPU → GVA | Jul 26, 19:55 UTC | Jul 26, 21:05 UTC | 1h 10m |
| 2026-07-26 | GVA → DBV | Jul 26, 16:55 UTC | Jul 26, 18:05 UTC | 1h 10m |
| 2026-07-26 | - | Jul 26, 11:15 UTC | Jul 26, 15:45 UTC | 4h 30m |
| 2026-07-26 | - | Jul 26, 08:20 UTC | Jul 26, 10:00 UTC | 1h 40m |
| 2026-07-26 | GVA → NBE | Jul 26, 05:25 UTC | Jul 26, 06:55 UTC | 1h 31m |
| 2026-07-25 | MLA → GVA | Jul 25, 19:15 UTC | Jul 25, 21:20 UTC | 2h 5m |
| 2026-07-25 | GVA → MLA | Jul 25, 16:20 UTC | Jul 25, 18:10 UTC | 1h 50m |
| 2026-07-25 | - | Jul 25, 10:35 UTC | Jul 25, 15:20 UTC | 4h 45m |
| 2026-07-25 | CLY → GVA | Jul 25, 07:00 UTC | Jul 25, 07:55 UTC | 55m |
| 2026-07-25 | GVA → CLY | Jul 25, 05:05 UTC | Jul 25, 05:55 UTC | 50m |
| 2026-07-24 | BUD → GVA | Jul 24, 19:10 UTC | Jul 24, 20:45 UTC | 1h 35m |
| 2026-07-24 | GVA → BUD | Jul 24, 16:50 UTC | Jul 24, 18:20 UTC | 1h 30m |
| 2026-07-24 | RNS → GVA | Jul 24, 14:40 UTC | Jul 24, 15:50 UTC | 1h 10m |
| 2026-07-24 | GVA → RNS | Jul 24, 12:45 UTC | Jul 24, 13:55 UTC | 1h 10m |
| 2026-07-24 | BOD → GVA | Jul 24, 10:40 UTC | Jul 24, 11:35 UTC | 55m |
| 2026-07-24 | GVA → BOD | Jul 24, 08:35 UTC | Jul 24, 09:45 UTC | 1h 10m |
| 2026-07-24 | NCE → GVA | Jul 24, 06:15 UTC | Jul 24, 07:00 UTC | 45m |
| 2026-07-24 | GVA → NCE | Jul 24, 04:20 UTC | Jul 24, 05:00 UTC | 40m |
| 2026-07-23 | NCE → GVA | Jul 23, 19:50 UTC | Jul 23, 20:35 UTC | 45m |
| 2026-07-23 | GVA → NCE | Jul 23, 18:10 UTC | Jul 23, 18:50 UTC | 40m |
| 2026-07-23 | SVQ → GVA | Jul 23, 15:10 UTC | Jul 23, 17:00 UTC | 1h 50m |
| 2026-07-23 | GVA → SVQ | Jul 23, 12:10 UTC | Jul 23, 14:10 UTC | 2h 0m |
| 2026-07-23 | ATH → GVA | Jul 23, 08:25 UTC | Jul 23, 11:10 UTC | 2h 45m |
| 2026-07-23 | GVA → ATH | Jul 23, 04:50 UTC | Jul 23, 07:10 UTC | 2h 20m |
| 2026-07-22 | BOD → GVA | Jul 22, 18:55 UTC | Jul 22, 19:45 UTC | 50m |
| 2026-07-22 | GVA → BOD | Jul 22, 17:05 UTC | Jul 22, 18:05 UTC | 1h 0m |
| 2026-07-22 | - | Jul 22, 15:00 UTC | Jul 22, 16:00 UTC | 1h 0m |
| 2026-07-22 | - | Jul 22, 13:15 UTC | Jul 22, 14:05 UTC | 50m |
| 2026-07-22 | BOD → GVA | Jul 22, 11:20 UTC | Jul 22, 12:10 UTC | 50m |
| 2026-07-22 | GVA → NAP | Jul 22, 04:20 UTC | Jul 22, 05:25 UTC | 1h 5m |
| 2026-07-21 | VLC → GVA | Jul 21, 19:30 UTC | Jul 21, 21:00 UTC | 1h 30m |
| 2026-07-21 | GVA → VLC | Jul 21, 16:40 UTC | Jul 21, 18:10 UTC | 1h 30m |
| 2026-07-21 | - | Jul 21, 13:45 UTC | Jul 21, 15:40 UTC | 1h 55m |
| 2026-07-21 | - | Jul 21, 10:55 UTC | Jul 21, 12:40 UTC | 1h 45m |
| 2026-07-21 | OPO → GVA | Jul 21, 07:20 UTC | Jul 21, 09:05 UTC | 1h 45m |
| 2026-07-21 | GVA → OPO | Jul 21, 04:15 UTC | Jul 21, 06:25 UTC | 2h 10m |
| 2026-07-20 | - | Jul 20, 20:10 UTC | Jul 20, 21:35 UTC | 1h 25m |
| 2026-07-20 | - | Jul 20, 17:40 UTC | Jul 20, 18:55 UTC | 1h 15m |
| 2026-07-20 | - | Jul 20, 15:35 UTC | Jul 20, 16:35 UTC | 1h 0m |
| 2026-07-20 | - | Jul 20, 13:20 UTC | Jul 20, 14:20 UTC | 1h 0m |
| 2026-07-20 | NCE → GVA | Jul 20, 11:30 UTC | Jul 20, 12:10 UTC | 40m |
| 2026-07-20 | GVA → NCE | Jul 20, 09:40 UTC | Jul 20, 10:25 UTC | 45m |
| 2026-07-20 | BRU → GVA | Jul 20, 07:25 UTC | Jul 20, 08:30 UTC | 1h 5m |
| 2026-07-20 | GVA → BRU | Jul 20, 05:35 UTC | Jul 20, 06:35 UTC | 1h 0m |
| 2026-07-19 | PRN → GVA | Jul 19, 18:55 UTC | Jul 19, 20:45 UTC | 1h 50m |
| 2026-07-19 | - | Jul 19, 16:05 UTC | Jul 19, 17:40 UTC | 1h 35m |
| 2026-07-19 | LIS → GVA | Jul 19, 12:25 UTC | Jul 19, 14:15 UTC | 1h 50m |
| 2026-07-19 | - | Jul 19, 08:40 UTC | Jul 19, 10:55 UTC | 2h 15m |
| 2026-07-19 | - | Jul 19, 06:20 UTC | Jul 19, 07:35 UTC | 1h 15m |
| 2026-07-19 | GVA → SPU | Jul 19, 04:00 UTC | Jul 19, 05:05 UTC | 1h 5m |
Specifications
| Registration | HB-JYD |
| Aircraft type | AIRBUS A-320 (A320) |
| Mode-S code | 4B1A37 · 22615067 (octal) |
Looking for transponder-level data? View the Mode-S 4B1A37 page for country allocation, callsign history, and ADS-B signal details.
HB-JYD frequently asked
What type of aircraft is HB-JYD?
HB-JYD is a AIRBUS A-320 (ICAO type code A320).
What is the Mode-S transponder code for HB-JYD?
HB-JYD broadcasts on Mode-S (ICAO 24-bit) address 4B1A37 (octal 22615067). View the transponder page.
What route does HB-JYD typically fly?
HB-JYD most frequently flies between BOD and GVA based on observed flights.
Where is HB-JYD right now?
HB-JYD is not currently being tracked; last seen Jul 26, 21:05 UTC.