sensors Mode-S transponder
711462
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-FBP · AIRBUS A-320neo
- Hex
- 711462
- Octal
- 34212142
- Decimal
- 7,410,786
- Country
- SA
- Tail
- HZ-FBP
- Type
- A20N
- Flights observed
- 110
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address 711462 falls within the block assigned to Saudi Arabia (SA) by ICAO Annex 10, Volume III. Every aircraft registered in Saudi Arabia receives a permanent address from this block at the time of registration; the address stays with the airframe even if the aircraft is re-registered to a different operator within the country.
Callsign history 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| FAD573 | - | 22 | 2026-07-13 |
| FAD574 | - | 21 | 2026-07-16 |
| FAD807 | Rog-Air | 9 | 2026-05-07 |
| FAD505 | - | 9 | 2026-07-07 |
| FAD808 | Rog-Air | 7 | 2026-05-07 |
| FAD665 | - | 5 | 2026-07-15 |
| FAD615 | Rog-Air | 3 | 2026-07-17 |
| FAD578 | - | 3 | 2026-07-17 |
| FAD657 | - | 2 | 2026-07-07 |
| FAD6155 | - | 2 | 2026-05-09 |
| FAD613 | - | 2 | 2026-07-13 |
| FAD561 | - | 2 | 2026-07-15 |
| FAD304 | Rog-Air | 2 | 2026-05-03 |
| FAD776 | Rog-Air | 1 | 2026-05-10 |
| FAD775 | Rog-Air | 1 | 2026-05-10 |
| FAD755 | Rog-Air | 1 | 2026-04-25 |
| FAD702 | - | 1 | 2026-04-23 |
| FAD666 | - | 1 | 2026-07-05 |
| FAD661 | Rog-Air | 1 | 2026-05-15 |
| FAD656 | Rog-Air | 1 | 2026-05-25 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | FAD615 | RUH → CAI | Jul 17, 10:40 UTC | Jul 17, 21:55 UTC | 11h 15m |
| 2026-07-17 | FAD578 | - | Jul 17, 09:20 UTC | Jul 17, 10:35 UTC | 1h 15m |
| 2026-07-16 | FAD574 | - | Jul 16, 18:10 UTC | Jul 17, 07:50 UTC | 13h 40m |
| 2026-07-15 | FAD665 | - | Jul 15, 21:20 UTC | Jul 16, 16:05 UTC | 18h 45m |
| 2026-07-15 | FAD665 | - | Jul 15, 10:45 UTC | Jul 16, 06:15 UTC | 19h 30m |
| 2026-07-15 | FAD561 | - | Jul 15, 08:30 UTC | Jul 15, 09:05 UTC | 35m |
| 2026-07-14 | FAD561 | - | Jul 14, 10:35 UTC | Jul 15, 09:05 UTC | 22h 29m |
| 2026-07-14 | FAD578 | - | Jul 14, 09:30 UTC | Jul 15, 08:30 UTC | 22h 59m |
| 2026-07-13 | FAD574 | - | Jul 13, 18:55 UTC | Jul 14, 08:15 UTC | 13h 20m |
| 2026-07-13 | FAD573 | - | Jul 13, 14:40 UTC | Jul 13, 16:40 UTC | 2h 0m |
| 2026-07-13 | FAD614 | - | Jul 13, 09:55 UTC | Jul 13, 10:10 UTC | 15m |
| 2026-07-13 | FAD613 | - | Jul 13, 07:10 UTC | Jul 13, 07:55 UTC | 45m |
| 2026-07-10 | FAD574 | - | Jul 10, 18:05 UTC | Jul 10, 20:05 UTC | 2h 0m |
| 2026-07-09 | FAD573 | - | Jul 9, 22:50 UTC | Jul 10, 15:50 UTC | 17h 0m |
| 2026-07-09 | FAD573 | - | Jul 9, 16:35 UTC | Jul 10, 15:50 UTC | 23h 15m |
| 2026-07-09 | FAD580 | - | Jul 9, 15:00 UTC | Jul 10, 14:30 UTC | 23h 30m |
| 2026-07-09 | FAD579 | - | Jul 9, 13:10 UTC | Jul 9, 13:35 UTC | 25m |
| 2026-07-08 | FAD665 | - | Jul 8, 21:25 UTC | Jul 9, 12:35 UTC | 15h 10m |
| 2026-07-08 | FAD665 | - | Jul 8, 04:35 UTC | Jul 9, 04:30 UTC | 23h 55m |
| 2026-07-08 | FAD665 | - | Jul 8, 04:15 UTC | Jul 9, 00:40 UTC | 20h 25m |
| 2026-07-07 | FAD657 | - | Jul 7, 21:00 UTC | Jul 8, 04:50 UTC | 7h 50m |
| 2026-07-07 | FAD657 | - | Jul 7, 09:10 UTC | Jul 8, 04:50 UTC | 19h 40m |
| 2026-07-07 | FAD505 | - | Jul 7, 06:40 UTC | Jul 7, 08:05 UTC | 1h 25m |
| 2026-07-05 | FAD666 | - | Jul 5, 13:50 UTC | Jul 6, 06:40 UTC | 16h 50m |
| 2026-07-04 | FAD574 | - | Jul 4, 18:00 UTC | Jul 5, 12:25 UTC | 18h 25m |
| 2026-07-04 | FAD573 | RUH → IST | Jul 4, 09:25 UTC | Jul 4, 16:10 UTC | 6h 45m |
| 2026-07-03 | FAD574 | - | Jul 3, 18:05 UTC | Jul 4, 07:50 UTC | 13h 45m |
| 2026-07-03 | FAD573 | RUH → IST | Jul 3, 09:35 UTC | Jul 3, 16:05 UTC | 6h 30m |
| 2026-07-03 | FAD505 | - | Jul 3, 06:55 UTC | Jul 3, 08:20 UTC | 1h 25m |
| 2026-07-02 | FAD578 | - | Jul 2, 09:20 UTC | Jul 2, 15:00 UTC | 5h 40m |
| 2026-07-02 | FAD577 | - | Jul 2, 07:50 UTC | Jul 2, 07:55 UTC | 5m |
| 2026-06-30 | FAD512 | - | Jun 30, 18:15 UTC | Jun 30, 19:05 UTC | 50m |
| 2026-06-29 | FAD511 | - | Jun 29, 20:35 UTC | Jun 30, 16:30 UTC | 19h 55m |
| 2026-06-29 | FAD574 | - | Jun 29, 19:00 UTC | Jun 30, 16:30 UTC | 21h 30m |
| 2026-06-29 | FAD573 | RUH → IST | Jun 29, 08:54 UTC | Jun 29, 17:19 UTC | 8h 25m |
| 2026-06-28 | FAD574 | - | Jun 28, 18:05 UTC | Jun 29, 07:44 UTC | 13h 40m |
| 2026-06-28 | FAD573 | RUH → IST | Jun 28, 08:59 UTC | Jun 28, 16:29 UTC | 7h 30m |
| 2026-06-28 | FAD505 | - | Jun 28, 06:40 UTC | Jun 28, 07:44 UTC | 1h 5m |
| 2026-06-25 | FAD651 | - | Jun 25, 21:50 UTC | Jun 26, 06:15 UTC | 8h 25m |
| 2026-06-18 | FAD574 | - | Jun 18, 18:10 UTC | Jun 18, 20:15 UTC | 2h 5m |
| 2026-06-18 | FAD573 | RUH → IST | Jun 18, 09:00 UTC | Jun 18, 16:05 UTC | 7h 5m |
| 2026-06-18 | FAD505 | - | Jun 18, 06:45 UTC | Jun 18, 07:10 UTC | 25m |
| 2026-06-13 | FAD574 | - | Jun 13, 18:00 UTC | Jun 13, 19:55 UTC | 1h 55m |
| 2026-06-13 | FAD573 | RUH → IST | Jun 13, 06:35 UTC | Jun 13, 16:00 UTC | 9h 25m |
| 2026-06-12 | FAD505 | RUH → DXB | Jun 12, 13:05 UTC | Jun 13, 06:55 UTC | 17h 49m |
| 2026-06-12 | FAD607 | RUH → CAI | Jun 12, 10:45 UTC | Jun 12, 11:10 UTC | 25m |
| 2026-06-10 | FAD505 | RUH → DXB | Jun 10, 06:35 UTC | Jun 10, 10:00 UTC | 3h 25m |
| 2026-06-08 | FAD615 | RUH → CAI | Jun 8, 22:00 UTC | Jun 8, 22:15 UTC | 15m |
| 2026-06-06 | FAD574 | IST → RUH | Jun 6, 18:25 UTC | Jun 6, 20:19 UTC | 1h 55m |
| 2026-06-06 | FAD573 | RUH → IST | Jun 6, 06:25 UTC | Jun 6, 15:59 UTC | 9h 35m |
About Mode-S
A Mode-S transponder code (also called an "ICAO 24-bit address" or "hex code") is a 6-character hexadecimal identifier permanently assigned to an aircraft when it's first registered. Unlike callsigns (which change with each flight) or registrations (which can change if an aircraft is sold internationally), the Mode-S address stays with the airframe for the life of the aircraft in that country.
Every ADS-B transmission from an aircraft includes its Mode-S address, making it the most reliable way to identify a specific airframe. Flight-tracking services like Apparatus use the Mode-S address as the primary key for tying position broadcasts, callsigns, and ownership records together.
Prefer a tail-number view? See the HZ-FBP page for operator, model, and routing details .