Not currently tracked · last seen 51m ago
- Flights observed
- 91 showing last 50
- Avg flight time
- 4h 6m
- Typical route
- JED → HBE
- Last seen
- 51m ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-05-30 | SSH → MAD | May 30, 06:35 UTC | May 30, 10:30 UTC | 3h 55m |
| 2026-05-30 | SAW → CAI | May 30, 01:50 UTC | May 30, 03:10 UTC | 1h 20m |
| 2026-05-29 | CAI → SAW | May 29, 22:35 UTC | May 30, 00:10 UTC | 1h 35m |
| 2026-05-29 | - | May 29, 17:40 UTC | May 29, 17:50 UTC | 10m |
| 2026-05-29 | - | May 29, 14:30 UTC | May 29, 15:20 UTC | 50m |
| 2026-05-29 | - | May 29, 12:20 UTC | May 29, 13:15 UTC | 55m |
| 2026-05-29 | TBS → AMM | May 29, 06:45 UTC | May 29, 09:20 UTC | 2h 35m |
| 2026-05-29 | - | May 29, 02:55 UTC | May 29, 05:25 UTC | 2h 30m |
| 2026-05-28 | - | May 28, 07:45 UTC | May 28, 08:10 UTC | 25m |
| 2026-05-28 | JED → HBE | May 28, 00:35 UTC | May 28, 06:00 UTC | 5h 25m |
| 2026-05-27 | JED → HBE | May 27, 00:00 UTC | May 27, 13:30 UTC | 13h 31m |
| 2026-05-26 | RUH → CAI | May 26, 11:24 UTC | May 26, 16:55 UTC | 5h 30m |
| 2026-05-26 | - | May 26, 03:09 UTC | May 26, 07:45 UTC | 4h 35m |
| 2026-05-25 | AMM → HBE | May 25, 13:40 UTC | May 25, 23:40 UTC | 9h 59m |
| 2026-05-25 | ALY → AMM | May 25, 11:05 UTC | May 25, 12:00 UTC | 55m |
| 2026-05-25 | JED → HBE | May 25, 01:55 UTC | May 25, 06:45 UTC | 4h 50m |
| 2026-05-24 | MED → ALY | May 24, 09:25 UTC | May 24, 19:50 UTC | 10h 25m |
| 2026-05-23 | JED → HBE | May 23, 13:20 UTC | May 24, 06:50 UTC | 17h 31m |
| 2026-05-23 | JED → HBE | May 23, 08:25 UTC | May 23, 09:05 UTC | 40m |
| 2026-05-22 | JED → HBE | May 22, 12:00 UTC | May 23, 09:05 UTC | 21h 4m |
| 2026-05-22 | ATZ → ADJ | May 22, 09:45 UTC | May 22, 10:15 UTC | 30m |
| 2026-05-21 | MED → HMB | May 21, 01:00 UTC | May 21, 04:55 UTC | 3h 55m |
| 2026-05-20 | RUH → CAI | May 20, 10:00 UTC | May 20, 18:00 UTC | 8h 0m |
| 2026-05-20 | CAI → SHJ | May 20, 01:50 UTC | May 20, 02:05 UTC | 15m |
| 2026-05-19 | YNB → CAI | May 19, 02:25 UTC | May 19, 06:15 UTC | 3h 50m |
| 2026-05-18 | - | May 18, 17:25 UTC | May 18, 17:35 UTC | 10m |
| 2026-05-18 | AMM → HBE | May 18, 13:50 UTC | May 18, 14:55 UTC | 1h 5m |
| 2026-05-18 | ALY → AMM | May 18, 11:10 UTC | May 18, 11:45 UTC | 35m |
| 2026-05-18 | JED → HBE | May 18, 01:40 UTC | May 18, 07:30 UTC | 5h 50m |
| 2026-05-17 | MED → ALY | May 17, 17:15 UTC | May 17, 21:10 UTC | 3h 55m |
| 2026-05-17 | MED → ATZ | May 17, 10:15 UTC | May 17, 14:30 UTC | 4h 15m |
| 2026-05-17 | JED → HBE | May 17, 01:25 UTC | May 17, 06:45 UTC | 5h 20m |
| 2026-05-16 | ALY → JED | May 16, 13:11 UTC | May 16, 20:10 UTC | 7h 0m |
| 2026-05-16 | JED → HBE | May 16, 08:51 UTC | May 16, 09:21 UTC | 30m |
| 2026-05-15 | JED → HBE | May 15, 11:25 UTC | May 16, 09:21 UTC | 21h 55m |
| 2026-05-15 | ATZ → ADJ | May 15, 09:30 UTC | May 15, 09:50 UTC | 20m |
| 2026-05-13 | ADJ → ATZ | May 13, 12:10 UTC | May 13, 21:05 UTC | 8h 55m |
| 2026-05-13 | ATZ → ADJ | May 13, 10:15 UTC | May 13, 10:35 UTC | 20m |
| 2026-05-09 | MXP → CAI | May 9, 18:50 UTC | May 9, 21:14 UTC | 2h 25m |
| 2026-05-09 | CAI → MXP | May 9, 13:40 UTC | May 9, 17:10 UTC | 3h 30m |
| 2026-05-09 | JED → CAI | May 9, 06:05 UTC | May 9, 06:35 UTC | 30m |
| 2026-05-08 | CAI → YNB | May 8, 19:05 UTC | May 8, 19:25 UTC | 20m |
| 2026-05-08 | HRG → CAI | May 8, 16:35 UTC | May 8, 17:00 UTC | 25m |
| 2026-05-08 | CAI → HRG | May 8, 14:25 UTC | May 8, 14:35 UTC | 10m |
| 2026-05-08 | JED → CAI | May 8, 12:04 UTC | May 8, 12:30 UTC | 25m |
| 2026-05-08 | - | May 8, 00:34 UTC | May 8, 05:00 UTC | 4h 25m |
| 2026-05-06 | - | May 6, 23:25 UTC | May 7, 02:30 UTC | 3h 5m |
| 2026-05-06 | AUE → RZE | May 6, 18:30 UTC | May 6, 22:05 UTC | 3h 35m |
| 2026-05-06 | - | May 6, 16:00 UTC | May 6, 16:10 UTC | 10m |
| 2026-05-04 | RUH → CAI | May 4, 17:10 UTC | May 4, 17:30 UTC | 20m |
Specifications
| Registration | SU-BWF |
| Aircraft type | AIRBUS A-320 (A320) |
| Mode-S code | 010273 · 00201163 (octal) |
Looking for transponder-level data? View the Mode-S 010273 page for country allocation, callsign history, and ADS-B signal details.
SU-BWF frequently asked
What type of aircraft is SU-BWF?
SU-BWF is a AIRBUS A-320 (ICAO type code A320).
What is the Mode-S transponder code for SU-BWF?
SU-BWF broadcasts on Mode-S (ICAO 24-bit) address 010273 (octal 00201163). View the transponder page.
What route does SU-BWF typically fly?
SU-BWF most frequently flies between JED and HBE based on observed flights.
Where is SU-BWF right now?
SU-BWF is not currently being tracked; last seen 51m ago.