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
- 56
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 1d ago
Current 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 |
|---|---|---|---|
| FAD574 | Rog-Air | 10 | 2026-05-30 |
| FAD573 | Rog-Air | 10 | 2026-05-30 |
| FAD807 | Rog-Air | 9 | 2026-05-07 |
| FAD808 | Rog-Air | 7 | 2026-05-07 |
| FAD505 | Rog-Air | 3 | 2026-06-01 |
| FAD6155 | - | 2 | 2026-05-09 |
| 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 |
| FAD661 | Rog-Air | 1 | 2026-05-15 |
| FAD656 | Rog-Air | 1 | 2026-05-25 |
| FAD655 | Rog-Air | 1 | 2026-05-24 |
| FAD654 | Rog-Air | 1 | 2026-04-16 |
| FAD653 | - | 1 | 2026-04-15 |
| FAD652 | Rog-Air | 1 | 2026-05-22 |
| FAD6219 | - | 1 | 2026-05-08 |
| FAD613 | Rog-Air | 1 | 2026-04-18 |
| FAD306 | Rog-Air | 1 | 2026-05-03 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-01 | FAD505 | RUH → DXB | Jun 1, 06:20 UTC | Jun 1, 10:05 UTC | 3h 45m |
| 2026-05-30 | FAD574 | IST → RUH | May 30, 18:10 UTC | May 30, 19:55 UTC | 1h 45m |
| 2026-05-30 | FAD573 | RUH → IST | May 30, 06:10 UTC | May 30, 16:10 UTC | 10h 0m |
| 2026-05-29 | FAD573 | RUH → IST | May 29, 18:35 UTC | May 30, 16:10 UTC | 21h 35m |
| 2026-05-29 | FAD574 | IST → RUH | May 29, 17:55 UTC | May 30, 16:10 UTC | 22h 15m |
| 2026-05-29 | FAD573 | RUH → IST | May 29, 06:20 UTC | May 29, 16:00 UTC | 9h 40m |
| 2026-05-28 | FAD573 | RUH → IST | May 28, 18:35 UTC | May 29, 16:00 UTC | 21h 25m |
| 2026-05-28 | FAD574 | IST → RUH | May 28, 18:00 UTC | May 29, 16:00 UTC | 22h 0m |
| 2026-05-28 | FAD573 | RUH → IST | May 28, 06:35 UTC | May 28, 16:05 UTC | 9h 30m |
| 2026-05-27 | FAD573 | RUH → IST | May 27, 18:35 UTC | May 28, 16:05 UTC | 21h 30m |
| 2026-05-27 | FAD574 | IST → RUH | May 27, 17:55 UTC | May 28, 16:05 UTC | 22h 10m |
| 2026-05-27 | FAD573 | RUH → IST | May 27, 06:25 UTC | May 27, 16:15 UTC | 9h 51m |
| 2026-05-26 | FAD574 | IST → RUH | May 26, 18:34 UTC | May 27, 16:15 UTC | 21h 41m |
| 2026-05-26 | FAD574 | IST → RUH | May 26, 18:05 UTC | May 27, 14:15 UTC | 20h 10m |
| 2026-05-26 | FAD573 | RUH → IST | May 26, 06:25 UTC | May 26, 16:24 UTC | 10h 0m |
| 2026-05-25 | FAD656 | LHE → RUH | May 25, 02:45 UTC | May 25, 06:15 UTC | 3h 30m |
| 2026-05-24 | FAD655 | RUH → LHE | May 24, 21:30 UTC | May 24, 21:45 UTC | 15m |
| 2026-05-22 | FAD652 | ISB → RUH | May 22, 00:50 UTC | May 22, 03:10 UTC | 2h 20m |
| 2026-05-15 | FAD661 | RUH → KHI | May 15, 23:00 UTC | May 16, 05:10 UTC | 6h 10m |
| 2026-05-15 | FAD505 | RUH → DXB | May 15, 06:35 UTC | May 16, 05:10 UTC | 22h 34m |
| 2026-05-15 | FAD505 | RUH → DXB | May 15, 06:25 UTC | May 15, 23:15 UTC | 16h 49m |
| 2026-05-14 | FAD574 | IST → RUH | May 14, 18:30 UTC | May 15, 06:50 UTC | 12h 20m |
| 2026-05-14 | FAD573 | RUH → IST | May 14, 14:45 UTC | May 14, 15:50 UTC | 1h 5m |
| 2026-05-10 | FAD776 | CAI → MED | May 10, 19:50 UTC | May 10, 20:05 UTC | 15m |
| 2026-05-10 | FAD775 | MED → CAI | May 10, 17:55 UTC | May 10, 18:09 UTC | 15m |
| 2026-05-09 | FAD6155 | - | May 9, 16:40 UTC | May 9, 17:05 UTC | 25m |
| 2026-05-09 | FAD6155 | - | May 9, 05:35 UTC | May 9, 13:50 UTC | 8h 15m |
| 2026-05-08 | FAD6219 | TBS → TBS | May 8, 17:35 UTC | May 9, 13:50 UTC | 20h 15m |
| 2026-05-07 | FAD808 | IST → JED | May 7, 20:35 UTC | May 8, 16:15 UTC | 19h 40m |
| 2026-05-07 | FAD807 | JED → IST | May 7, 11:10 UTC | May 7, 18:25 UTC | 7h 15m |
| 2026-05-06 | FAD808 | IST → JED | May 6, 20:15 UTC | May 6, 21:55 UTC | 1h 40m |
| 2026-05-06 | FAD807 | JED → IST | May 6, 16:30 UTC | May 6, 18:05 UTC | 1h 34m |
| 2026-05-03 | FAD306 | DMM → JED | May 3, 15:00 UTC | May 3, 23:25 UTC | 8h 25m |
| 2026-05-03 | FAD304 | DMM → JED | May 3, 08:00 UTC | May 3, 08:10 UTC | 10m |
| 2026-05-02 | FAD808 | IST → JED | May 2, 20:20 UTC | May 2, 22:15 UTC | 1h 55m |
| 2026-05-02 | FAD807 | JED → IST | May 2, 11:10 UTC | May 2, 18:15 UTC | 7h 5m |
| 2026-05-01 | FAD807 | JED → IST | May 1, 20:35 UTC | May 2, 18:15 UTC | 21h 41m |
| 2026-05-01 | FAD808 | IST → JED | May 1, 20:15 UTC | May 2, 18:15 UTC | 22h 1m |
| 2026-05-01 | FAD807 | JED → IST | May 1, 11:05 UTC | May 1, 18:25 UTC | 7h 20m |
| 2026-04-29 | FAD304 | DMM → JED | Apr 29, 08:15 UTC | Apr 29, 08:34 UTC | 20m |
| 2026-04-28 | FAD808 | IST → JED | Apr 28, 20:10 UTC | Apr 28, 21:55 UTC | 1h 45m |
| 2026-04-28 | FAD807 | JED → IST | Apr 28, 16:30 UTC | Apr 28, 18:25 UTC | 1h 55m |
| 2026-04-25 | FAD808 | IST → JED | Apr 25, 20:10 UTC | Apr 25, 21:55 UTC | 1h 45m |
| 2026-04-25 | FAD807 | JED → IST | Apr 25, 09:05 UTC | Apr 25, 18:20 UTC | 9h 15m |
| 2026-04-25 | FAD755 | JED → CAI | Apr 25, 06:40 UTC | Apr 25, 07:05 UTC | 25m |
| 2026-04-23 | FAD702 | - | Apr 23, 12:15 UTC | Apr 23, 13:25 UTC | 1h 10m |
| 2026-04-22 | FAD808 | IST → JED | Apr 22, 20:25 UTC | Apr 23, 09:10 UTC | 12h 45m |
| 2026-04-22 | FAD807 | JED → IST | Apr 22, 16:55 UTC | Apr 22, 18:55 UTC | 2h 0m |
| 2026-04-20 | FAD807 | - | Apr 20, 16:30 UTC | Apr 20, 21:55 UTC | 5h 25m |
| 2026-04-18 | FAD613 | RUH → CAI | Apr 18, 13:15 UTC | Apr 19, 08:00 UTC | 18h 45m |
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 .