Not currently tracked · last seen 1h ago
- Flights observed
- 266 showing last 50
- Avg flight time
- 1h 25m
- Typical route
- BOD → MRS
- Last seen
- 1h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-06-07 | LIL → BOD | Jun 7, 19:50 UTC | Jun 7, 20:15 UTC | 25m |
| 2026-06-07 | BOD → LIL | Jun 7, 18:00 UTC | Jun 7, 19:10 UTC | 1h 10m |
| 2026-06-07 | LIS → BOD | Jun 7, 15:45 UTC | Jun 7, 17:10 UTC | 1h 25m |
| 2026-06-07 | BOD → LIS | Jun 7, 12:05 UTC | Jun 7, 13:40 UTC | 1h 35m |
| 2026-06-07 | BUD → BOD | Jun 7, 08:50 UTC | Jun 7, 11:15 UTC | 2h 25m |
| 2026-06-07 | ALC → BFS | Jun 7, 05:40 UTC | Jun 7, 07:50 UTC | 2h 10m |
| 2026-06-06 | LYS → BOD | Jun 6, 17:00 UTC | Jun 6, 17:44 UTC | 45m |
| 2026-06-06 | BOD → LYS | Jun 6, 14:30 UTC | Jun 6, 15:19 UTC | 50m |
| 2026-06-06 | MXP → PRG | Jun 6, 10:04 UTC | Jun 6, 13:25 UTC | 3h 20m |
| 2026-06-06 | - | Jun 6, 05:15 UTC | Jun 6, 08:00 UTC | 2h 45m |
| 2026-06-05 | - | Jun 5, 17:15 UTC | Jun 5, 19:05 UTC | 1h 50m |
| 2026-06-05 | LGW → LYS | Jun 5, 14:15 UTC | Jun 5, 15:45 UTC | 1h 30m |
| 2026-06-05 | NCE → BOD | Jun 5, 10:10 UTC | Jun 5, 11:20 UTC | 1h 10m |
| 2026-06-05 | BOD → NCE | Jun 5, 07:50 UTC | Jun 5, 08:50 UTC | 1h 0m |
| 2026-06-05 | - | Jun 5, 06:00 UTC | Jun 5, 06:50 UTC | 50m |
| 2026-06-05 | BOD → LYS | Jun 5, 04:20 UTC | Jun 5, 05:05 UTC | 45m |
| 2026-06-04 | - | Jun 4, 18:50 UTC | Jun 4, 20:30 UTC | 1h 40m |
| 2026-06-04 | LGW → LYS | Jun 4, 16:00 UTC | Jun 4, 17:35 UTC | 1h 35m |
| 2026-06-04 | LIS → BOD | Jun 4, 13:55 UTC | Jun 4, 15:15 UTC | 1h 20m |
| 2026-06-04 | BOD → LIS | Jun 4, 10:45 UTC | Jun 4, 12:25 UTC | 1h 40m |
| 2026-06-04 | RAK → BOD | Jun 4, 07:30 UTC | Jun 4, 09:35 UTC | 2h 5m |
| 2026-06-04 | BOD → RAK | Jun 4, 04:10 UTC | Jun 4, 06:10 UTC | 2h 0m |
| 2026-06-03 | MXP → PRG | Jun 3, 17:25 UTC | Jun 3, 20:55 UTC | 3h 30m |
| 2026-06-03 | - | Jun 3, 13:15 UTC | Jun 3, 16:15 UTC | 3h 0m |
| 2026-06-03 | BSL → BOD | Jun 3, 10:45 UTC | Jun 3, 11:55 UTC | 1h 10m |
| 2026-06-03 | BOD → BSL | Jun 3, 08:45 UTC | Jun 3, 09:50 UTC | 1h 5m |
| 2026-06-03 | BOD → NCE | Jun 3, 07:00 UTC | Jun 3, 07:50 UTC | 50m |
| 2026-06-03 | BOD → MRS | Jun 3, 05:05 UTC | Jun 3, 05:55 UTC | 50m |
| 2026-06-02 | MRS → BOD | Jun 2, 20:00 UTC | Jun 2, 20:55 UTC | 55m |
| 2026-06-02 | BOD → MRS | Jun 2, 18:15 UTC | Jun 2, 19:05 UTC | 50m |
| 2026-06-02 | OPO → BOD | Jun 2, 16:15 UTC | Jun 2, 17:30 UTC | 1h 15m |
| 2026-06-02 | BOD → OPO | Jun 2, 13:50 UTC | Jun 2, 15:20 UTC | 1h 30m |
| 2026-06-02 | NCE → BOD | Jun 2, 11:40 UTC | Jun 2, 12:55 UTC | 1h 15m |
| 2026-06-02 | BOD → NCE | Jun 2, 09:15 UTC | Jun 2, 10:20 UTC | 1h 5m |
| 2026-06-02 | BOD → NCE | Jun 2, 07:25 UTC | Jun 2, 08:25 UTC | 1h 0m |
| 2026-06-02 | BOD → MRS | Jun 2, 05:10 UTC | Jun 2, 06:00 UTC | 50m |
| 2026-06-01 | MRS → BOD | Jun 1, 20:20 UTC | Jun 1, 21:10 UTC | 50m |
| 2026-06-01 | BOD → MRS | Jun 1, 18:30 UTC | Jun 1, 19:25 UTC | 55m |
| 2026-06-01 | BRU → BOD | Jun 1, 16:15 UTC | Jun 1, 17:30 UTC | 1h 15m |
| 2026-06-01 | PMI → NTE | Jun 1, 13:50 UTC | Jun 1, 15:00 UTC | 1h 10m |
| 2026-06-01 | LIL → BOD | Jun 1, 11:30 UTC | Jun 1, 12:35 UTC | 1h 5m |
| 2026-06-01 | BOD → LIL | Jun 1, 09:35 UTC | Jun 1, 10:40 UTC | 1h 5m |
| 2026-06-01 | LGW → BOD | Jun 1, 07:45 UTC | Jun 1, 08:50 UTC | 1h 5m |
| 2026-06-01 | BOD → LGW | Jun 1, 05:05 UTC | Jun 1, 06:15 UTC | 1h 10m |
| 2026-05-31 | LYS → BOD | May 31, 19:35 UTC | May 31, 20:25 UTC | 50m |
| 2026-05-31 | BOD → LYS | May 31, 17:45 UTC | May 31, 18:35 UTC | 50m |
| 2026-05-31 | MRS → BOD | May 31, 16:10 UTC | May 31, 17:00 UTC | 50m |
| 2026-05-31 | BOD → MRS | May 31, 14:10 UTC | May 31, 15:05 UTC | 55m |
| 2026-05-31 | ATH → BOD | May 31, 09:50 UTC | May 31, 12:45 UTC | 2h 55m |
| 2026-05-30 | BOD → ACE | May 30, 17:35 UTC | May 30, 20:05 UTC | 2h 30m |
Specifications
| Registration | OE-IVC |
| Aircraft type | AIRBUS A-320 (A320) |
| Mode-S code | 440031 · 21000061 (octal) |
Looking for transponder-level data? View the Mode-S 440031 page for country allocation, callsign history, and ADS-B signal details.
OE-IVC frequently asked
What type of aircraft is OE-IVC?
OE-IVC is a AIRBUS A-320 (ICAO type code A320).
What is the Mode-S transponder code for OE-IVC?
OE-IVC broadcasts on Mode-S (ICAO 24-bit) address 440031 (octal 21000061). View the transponder page.
What route does OE-IVC typically fly?
OE-IVC most frequently flies between BOD and MRS based on observed flights.
Where is OE-IVC right now?
OE-IVC is not currently being tracked; last seen 1h ago.