Not currently tracked · last seen 3d ago
- Flights observed
- 289 showing last 50
- Avg flight time
- 1h 24m
- Typical route
- ZRH → ZRH
- Last seen
- 3d ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-11 | - | Jul 11, 18:15 UTC | Jul 11, 19:50 UTC | 1h 35m |
| 2026-07-11 | - | Jul 11, 15:15 UTC | Jul 11, 16:45 UTC | 1h 30m |
| 2026-07-11 | - | Jul 11, 11:35 UTC | Jul 11, 13:05 UTC | 1h 30m |
| 2026-07-11 | - | Jul 11, 08:35 UTC | Jul 11, 10:05 UTC | 1h 30m |
| 2026-07-11 | ATH → ZRH | Jul 11, 04:15 UTC | Jul 11, 06:50 UTC | 2h 35m |
| 2026-07-10 | ZRH → ATH | Jul 10, 19:45 UTC | Jul 10, 22:00 UTC | 2h 15m |
| 2026-07-10 | CPH → ZRH | Jul 10, 14:00 UTC | Jul 10, 15:30 UTC | 1h 30m |
| 2026-07-10 | ZRH → CPH | Jul 10, 11:10 UTC | Jul 10, 12:40 UTC | 1h 30m |
| 2026-07-10 | HAM → ZRH | Jul 10, 07:40 UTC | Jul 10, 08:50 UTC | 1h 10m |
| 2026-07-10 | ZRH → HAM | Jul 10, 05:15 UTC | Jul 10, 06:25 UTC | 1h 10m |
| 2026-07-09 | - | Jul 9, 19:00 UTC | Jul 9, 19:35 UTC | 35m |
| 2026-07-09 | ZRH → MUC | Jul 9, 17:20 UTC | Jul 9, 18:00 UTC | 40m |
| 2026-07-09 | ARN → ZRH | Jul 9, 14:15 UTC | Jul 9, 16:10 UTC | 1h 55m |
| 2026-07-09 | ZRH → ARN | Jul 9, 10:50 UTC | Jul 9, 13:05 UTC | 2h 15m |
| 2026-07-09 | - | Jul 9, 07:50 UTC | Jul 9, 08:50 UTC | 1h 0m |
| 2026-07-09 | ZRH → BER | Jul 9, 05:35 UTC | Jul 9, 06:45 UTC | 1h 10m |
| 2026-07-08 | - | Jul 8, 19:05 UTC | Jul 8, 20:55 UTC | 1h 50m |
| 2026-07-08 | ZRH → MAD | Jul 8, 15:40 UTC | Jul 8, 17:35 UTC | 1h 55m |
| 2026-07-06 | - | Jul 6, 18:45 UTC | Jul 6, 19:35 UTC | 50m |
| 2026-07-06 | ZRH → CDG | Jul 6, 16:40 UTC | Jul 6, 17:35 UTC | 55m |
| 2026-07-05 | BCN → ZRH | Jul 5, 18:20 UTC | Jul 5, 19:50 UTC | 1h 30m |
| 2026-07-05 | ZRH → BCN | Jul 5, 15:35 UTC | Jul 5, 17:00 UTC | 1h 25m |
| 2026-07-05 | - | Jul 5, 11:25 UTC | Jul 5, 13:00 UTC | 1h 35m |
| 2026-07-05 | - | Jul 5, 08:20 UTC | Jul 5, 09:50 UTC | 1h 30m |
| 2026-07-05 | - | Jul 5, 04:50 UTC | Jul 5, 06:10 UTC | 1h 20m |
| 2026-07-04 | ZRH → CPH | Jul 4, 19:55 UTC | Jul 4, 21:30 UTC | 1h 35m |
| 2026-07-04 | ATH → ZRH | Jul 4, 14:10 UTC | Jul 4, 16:35 UTC | 2h 25m |
| 2026-07-04 | ZRH → ATH | Jul 4, 10:35 UTC | Jul 4, 12:45 UTC | 2h 10m |
| 2026-07-03 | FRA → ZRH | Jul 3, 19:05 UTC | Jul 3, 19:40 UTC | 35m |
| 2026-07-03 | ZRH → FRA | Jul 3, 17:05 UTC | Jul 3, 17:50 UTC | 45m |
| 2026-07-03 | - | Jul 3, 13:40 UTC | Jul 3, 14:40 UTC | 1h 0m |
| 2026-07-03 | ZRH → HAM | Jul 3, 11:10 UTC | Jul 3, 12:20 UTC | 1h 10m |
| 2026-07-03 | - | Jul 3, 05:50 UTC | Jul 3, 06:50 UTC | 1h 0m |
| 2026-07-02 | GVA → ZRH | Jul 2, 08:25 UTC | Jul 2, 08:55 UTC | 30m |
| 2026-07-02 | ZRH → GVA | Jul 2, 06:15 UTC | Jul 2, 06:45 UTC | 30m |
| 2026-06-30 | - | Jun 30, 11:10 UTC | Jun 30, 12:50 UTC | 1h 40m |
| 2026-06-30 | - | Jun 30, 08:15 UTC | Jun 30, 09:40 UTC | 1h 25m |
| 2026-06-30 | ZRH → ZRH | Jun 30, 06:40 UTC | Jun 30, 08:05 UTC | 1h 25m |
| 2026-06-30 | ZRH → ZRH | Jun 30, 00:09 UTC | Jun 30, 01:45 UTC | 1h 36m |
| 2026-06-29 | ZRH → ZRH | Jun 29, 20:35 UTC | Jun 29, 22:10 UTC | 1h 35m |
| 2026-06-29 | ZRH → ZRH | Jun 29, 16:55 UTC | Jun 29, 17:14 UTC | 20m |
| 2026-06-29 | BER → ZRH | Jun 29, 15:39 UTC | Jun 29, 16:44 UTC | 1h 5m |
| 2026-06-29 | ZRH → BER | Jun 29, 11:39 UTC | Jun 29, 13:00 UTC | 1h 20m |
| 2026-06-29 | WAW → ZRH | Jun 29, 08:29 UTC | Jun 29, 10:00 UTC | 1h 30m |
| 2026-06-29 | ZRH → WAW | Jun 29, 05:34 UTC | Jun 29, 07:05 UTC | 1h 30m |
| 2026-06-28 | - | Jun 28, 20:34 UTC | Jun 28, 21:45 UTC | 1h 10m |
| 2026-06-28 | ZRH → HAM | Jun 28, 18:00 UTC | Jun 28, 18:59 UTC | 1h 0m |
| 2026-06-28 | - | Jun 28, 13:10 UTC | Jun 28, 14:54 UTC | 1h 45m |
| 2026-06-28 | - | Jun 28, 08:14 UTC | Jun 28, 09:50 UTC | 1h 35m |
| 2026-06-28 | ATH → ZRH | Jun 28, 04:15 UTC | Jun 28, 06:44 UTC | 2h 30m |
Specifications
| Registration | HB-IOD |
| Aircraft type | AIRBUS A-321 (A321) |
| Mode-S code | 4B168F · 22613217 (octal) |
Looking for transponder-level data? View the Mode-S 4B168F page for country allocation, callsign history, and ADS-B signal details.
HB-IOD frequently asked
What type of aircraft is HB-IOD?
HB-IOD is a AIRBUS A-321 (ICAO type code A321).
What is the Mode-S transponder code for HB-IOD?
HB-IOD broadcasts on Mode-S (ICAO 24-bit) address 4B168F (octal 22613217). View the transponder page.
What route does HB-IOD typically fly?
HB-IOD most frequently flies between ZRH and ZRH based on observed flights.
Where is HB-IOD right now?
HB-IOD is not currently being tracked; last seen 3d ago.