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