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