Not currently tracked · last seen Jul 26, 18:35 UTC
- Flights observed
- 298 showing last 50
- Avg flight time
- 1h 40m
- Typical route
- BOD → RAK
- Last seen
- Jul 26, 18:35 UTC
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-26 | RBA → BOD | Jul 26, 16:35 UTC | Jul 26, 18:30 UTC | 1h 55m |
| 2026-07-26 | BOD → RAK | Jul 26, 07:00 UTC | Jul 26, 09:05 UTC | 2h 5m |
| 2026-07-25 | BOD → ESU | Jul 25, 17:35 UTC | Jul 25, 19:30 UTC | 1h 55m |
| 2026-07-24 | BOD → CAG | Jul 24, 18:05 UTC | Jul 24, 19:20 UTC | 1h 15m |
| 2026-07-24 | MAH → BOD | Jul 24, 15:40 UTC | Jul 24, 16:55 UTC | 1h 15m |
| 2026-07-24 | LYS → BOD | Jul 24, 11:55 UTC | Jul 24, 12:50 UTC | 55m |
| 2026-07-24 | BOD → LGW | Jul 24, 05:10 UTC | Jul 24, 06:20 UTC | 1h 10m |
| 2026-07-23 | BOD → TFS | Jul 23, 05:55 UTC | Jul 23, 09:00 UTC | 3h 5m |
| 2026-07-22 | - | Jul 22, 13:15 UTC | Jul 22, 16:00 UTC | 2h 45m |
| 2026-07-22 | - | Jul 22, 04:45 UTC | Jul 22, 05:25 UTC | 40m |
| 2026-07-21 | LYS → BOD | Jul 21, 19:25 UTC | Jul 21, 20:15 UTC | 50m |
| 2026-07-21 | BOD → BER | Jul 21, 11:35 UTC | Jul 21, 13:40 UTC | 2h 5m |
| 2026-07-21 | BOD → RAK | Jul 21, 04:10 UTC | Jul 21, 06:10 UTC | 2h 0m |
| 2026-07-20 | - | Jul 20, 20:25 UTC | Jul 20, 21:40 UTC | 1h 15m |
| 2026-07-20 | PMI → NTE | Jul 20, 14:15 UTC | Jul 20, 15:25 UTC | 1h 10m |
| 2026-07-20 | - | Jul 20, 11:30 UTC | Jul 20, 13:15 UTC | 1h 45m |
| 2026-07-20 | BOD → LYS | Jul 20, 05:05 UTC | Jul 20, 05:55 UTC | 50m |
| 2026-07-19 | BOD → NCE | Jul 19, 17:55 UTC | Jul 19, 18:50 UTC | 55m |
| 2026-07-19 | - | Jul 19, 08:20 UTC | Jul 19, 10:15 UTC | 1h 55m |
| 2026-07-18 | BOD → ESU | Jul 18, 18:05 UTC | Jul 18, 20:00 UTC | 1h 55m |
| 2026-07-18 | - | Jul 18, 13:45 UTC | Jul 18, 17:05 UTC | 3h 20m |
| 2026-07-17 | - | Jul 17, 17:30 UTC | Jul 17, 18:34 UTC | 1h 5m |
| 2026-07-17 | - | Jul 17, 13:35 UTC | Jul 17, 14:24 UTC | 50m |
| 2026-07-17 | BOD → DBV | Jul 17, 05:25 UTC | Jul 17, 07:20 UTC | 1h 55m |
| 2026-07-16 | - | Jul 16, 17:45 UTC | Jul 16, 18:34 UTC | 50m |
| 2026-07-16 | - | Jul 16, 15:45 UTC | Jul 16, 16:44 UTC | 1h 0m |
| 2026-07-16 | BOD → LYS | Jul 16, 10:04 UTC | Jul 16, 10:50 UTC | 45m |
| 2026-07-16 | LGW → BOD | Jul 16, 08:05 UTC | Jul 16, 09:15 UTC | 1h 10m |
| 2026-07-15 | - | Jul 15, 13:50 UTC | Jul 15, 16:00 UTC | 2h 10m |
| 2026-07-15 | - | Jul 15, 11:30 UTC | Jul 15, 12:25 UTC | 55m |
| 2026-07-15 | - | Jul 15, 09:50 UTC | Jul 15, 10:35 UTC | 45m |
| 2026-07-15 | LGW → BOD | Jul 15, 07:55 UTC | Jul 15, 09:05 UTC | 1h 10m |
| 2026-07-14 | - | Jul 14, 14:10 UTC | Jul 14, 17:40 UTC | 3h 30m |
| 2026-07-14 | - | Jul 14, 12:20 UTC | Jul 14, 13:20 UTC | 1h 0m |
| 2026-07-14 | BOD → IBZ | Jul 14, 10:00 UTC | Jul 14, 11:15 UTC | 1h 15m |
| 2026-07-14 | - | Jul 14, 08:10 UTC | Jul 14, 09:10 UTC | 1h 0m |
| 2026-07-14 | - | Jul 14, 05:20 UTC | Jul 14, 06:15 UTC | 55m |
| 2026-07-13 | - | Jul 13, 20:20 UTC | Jul 13, 21:05 UTC | 45m |
| 2026-07-13 | - | Jul 13, 12:55 UTC | Jul 13, 15:05 UTC | 2h 10m |
| 2026-07-13 | BOD → LGW | Jul 13, 05:10 UTC | Jul 13, 06:25 UTC | 1h 15m |
| 2026-07-12 | - | Jul 12, 20:55 UTC | Jul 12, 21:35 UTC | 40m |
| 2026-07-11 | - | Jul 11, 17:30 UTC | Jul 11, 20:40 UTC | 3h 10m |
| 2026-07-11 | KRK → CDG | Jul 11, 08:05 UTC | Jul 11, 09:55 UTC | 1h 50m |
| 2026-07-11 | - | Jul 11, 05:25 UTC | Jul 11, 07:10 UTC | 1h 45m |
| 2026-07-10 | - | Jul 10, 12:30 UTC | Jul 10, 16:15 UTC | 3h 45m |
| 2026-07-10 | - | Jul 10, 04:25 UTC | Jul 10, 06:30 UTC | 2h 5m |
| 2026-07-09 | - | Jul 9, 15:35 UTC | Jul 9, 18:40 UTC | 3h 5m |
| 2026-07-09 | - | Jul 9, 11:10 UTC | Jul 9, 14:10 UTC | 3h 0m |
| 2026-07-09 | - | Jul 9, 05:00 UTC | Jul 9, 06:30 UTC | 1h 30m |
| 2026-07-08 | - | Jul 8, 18:50 UTC | Jul 8, 21:55 UTC | 3h 5m |
Specifications
| Registration | OE-ICT |
| Aircraft type | AIRBUS A-320 (A320) |
| Mode-S code | 4402DB · 21001333 (octal) |
Looking for transponder-level data? View the Mode-S 4402DB page for country allocation, callsign history, and ADS-B signal details.
OE-ICT frequently asked
What type of aircraft is OE-ICT?
OE-ICT is a AIRBUS A-320 (ICAO type code A320).
What is the Mode-S transponder code for OE-ICT?
OE-ICT broadcasts on Mode-S (ICAO 24-bit) address 4402DB (octal 21001333). View the transponder page.
What route does OE-ICT typically fly?
OE-ICT most frequently flies between BOD and RAK based on observed flights.
Where is OE-ICT right now?
OE-ICT is not currently being tracked; last seen Jul 26, 18:35 UTC.