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