sensors Mode-S transponder
711506
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-FBJ · AIRBUS A-320neo
- Hex
- 711506
- Octal
- 34212406
- Decimal
- 7,410,950
- Country
- SA
- Tail
- HZ-FBJ
- Type
- A20N
- Flights observed
- 76
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 711506 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 |
|---|---|---|---|
| FAD654 | - | 5 | 2026-06-25 |
| FAD653 | - | 5 | 2026-06-24 |
| FAD652 | Rog-Air | 4 | 2026-05-08 |
| FAD829 | Rog-Air | 3 | 2026-05-02 |
| FAD808 | Rog-Air | 3 | 2026-06-04 |
| FAD807 | Rog-Air | 3 | 2026-06-04 |
| FAD615 | - | 3 | 2026-06-22 |
| FAD6141 | - | 3 | 2026-05-17 |
| FAD310 | Rog-Air | 3 | 2026-05-20 |
| FAD773 | Rog-Air | 2 | 2026-04-30 |
| FAD7030 | Rog-Air | 2 | 2026-06-03 |
| FAD665 | - | 2 | 2026-07-12 |
| FAD651 | Rog-Air | 2 | 2026-06-18 |
| FAD616 | - | 2 | 2026-06-22 |
| FAD607 | Rog-Air | 2 | 2026-06-20 |
| FAD6065 | - | 2 | 2026-05-12 |
| FAD606 | Rog-Air | 2 | 2026-05-24 |
| FAD6059 | - | 2 | 2026-05-15 |
| FAD6058 | - | 2 | 2026-05-15 |
| FAD605 | Rog-Air | 2 | 2026-05-24 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-12 | FAD666 | - | Jul 12, 22:25 UTC | Jul 13, 06:20 UTC | 7h 55m |
| 2026-07-12 | FAD665 | - | Jul 12, 21:25 UTC | Jul 12, 22:20 UTC | 55m |
| 2026-07-11 | FAD580 | - | Jul 11, 15:15 UTC | Jul 11, 17:55 UTC | 2h 40m |
| 2026-07-10 | FAD665 | - | Jul 10, 21:30 UTC | Jul 11, 12:30 UTC | 15h 0m |
| 2026-06-25 | FAD654 | - | Jun 25, 05:20 UTC | Jun 25, 06:14 UTC | 55m |
| 2026-06-24 | FAD653 | - | Jun 24, 21:44 UTC | Jun 25, 03:20 UTC | 5h 35m |
| 2026-06-22 | FAD616 | - | Jun 22, 23:39 UTC | Jun 23, 00:00 UTC | 20m |
| 2026-06-22 | FAD615 | - | Jun 22, 21:45 UTC | Jun 22, 22:10 UTC | 25m |
| 2026-06-20 | FAD608 | CAI → RUH | Jun 20, 13:09 UTC | Jun 20, 13:24 UTC | 15m |
| 2026-06-20 | FAD607 | RUH → CAI | Jun 20, 10:55 UTC | Jun 20, 11:25 UTC | 30m |
| 2026-06-18 | FAD651 | RUH → ISB | Jun 18, 21:40 UTC | Jun 19, 05:59 UTC | 8h 19m |
| 2026-06-14 | FAD616 | CAI → RUH | Jun 14, 23:59 UTC | Jun 15, 00:10 UTC | 10m |
| 2026-06-14 | FAD615 | RUH → CAI | Jun 14, 21:55 UTC | Jun 14, 22:20 UTC | 25m |
| 2026-06-12 | FAD653 | RUH → SKT | Jun 12, 21:30 UTC | Jun 13, 03:10 UTC | 5h 40m |
| 2026-06-11 | FAD654 | SKT → RUH | Jun 11, 03:10 UTC | Jun 11, 03:35 UTC | 25m |
| 2026-06-10 | FAD653 | RUH → SKT | Jun 10, 21:45 UTC | Jun 11, 01:10 UTC | 3h 25m |
| 2026-06-10 | FAD653 | RUH → SKT | Jun 10, 00:10 UTC | Jun 10, 22:15 UTC | 22h 5m |
| 2026-06-09 | FAD615 | RUH → CAI | Jun 9, 13:20 UTC | Jun 9, 22:20 UTC | 9h 0m |
| 2026-06-09 | FAD607 | RUH → CAI | Jun 9, 10:50 UTC | Jun 9, 11:05 UTC | 15m |
| 2026-06-08 | FAD505 | RUH → DXB | Jun 8, 06:10 UTC | Jun 8, 09:55 UTC | 3h 45m |
| 2026-06-06 | FAD7057 | - | Jun 6, 11:35 UTC | Jun 6, 19:44 UTC | 8h 10m |
| 2026-06-06 | FAD7056 | JED → OSS | Jun 6, 09:19 UTC | Jun 6, 10:04 UTC | 45m |
| 2026-06-04 | FAD808 | IST → JED | Jun 4, 20:25 UTC | Jun 4, 22:25 UTC | 2h 0m |
| 2026-06-04 | FAD807 | JED → IST | Jun 4, 00:05 UTC | Jun 4, 18:30 UTC | 18h 25m |
| 2026-06-03 | FAD7031 | - | Jun 3, 10:05 UTC | Jun 3, 23:10 UTC | 13h 5m |
| 2026-06-03 | FAD7030 | JED → OSS | Jun 3, 03:00 UTC | Jun 3, 23:10 UTC | 20h 10m |
| 2026-06-03 | FAD7030 | JED → OSS | Jun 3, 00:35 UTC | Jun 3, 01:25 UTC | 50m |
| 2026-05-30 | FAD654 | SKT → RUH | May 30, 01:10 UTC | May 30, 06:20 UTC | 5h 10m |
| 2026-05-27 | FAD654 | SKT → RUH | May 27, 22:30 UTC | May 28, 06:20 UTC | 7h 50m |
| 2026-05-24 | FAD606 | CAI → RUH | May 24, 12:15 UTC | May 24, 12:25 UTC | 10m |
| 2026-05-24 | FAD605 | RUH → CAI | May 24, 10:05 UTC | May 24, 10:35 UTC | 30m |
| 2026-05-23 | FAD614 | CAI → RUH | May 23, 09:20 UTC | May 23, 09:30 UTC | 10m |
| 2026-05-23 | FAD613 | RUH → CAI | May 23, 07:30 UTC | May 23, 07:50 UTC | 20m |
| 2026-05-20 | FAD310 | DMM → JED | May 20, 13:00 UTC | May 20, 13:10 UTC | 10m |
| 2026-05-18 | FAD762 | CAI → JED | May 18, 19:00 UTC | May 19, 06:00 UTC | 11h 0m |
| 2026-05-18 | FAD6733 | - | May 18, 03:45 UTC | May 18, 17:05 UTC | 13h 20m |
| 2026-05-17 | FAD6141 | - | May 17, 14:15 UTC | May 18, 02:05 UTC | 11h 50m |
| 2026-05-17 | FAD6141 | - | May 17, 03:50 UTC | May 17, 12:20 UTC | 8h 30m |
| 2026-05-16 | FAD6141 | - | May 16, 14:35 UTC | May 17, 12:20 UTC | 21h 45m |
| 2026-05-16 | FAD6546 | - | May 16, 12:01 UTC | May 16, 12:21 UTC | 20m |
| 2026-05-15 | FAD6059 | - | May 15, 15:35 UTC | May 16, 12:21 UTC | 20h 46m |
| 2026-05-15 | FAD6059 | - | May 15, 15:25 UTC | May 16, 12:21 UTC | 20h 56m |
| 2026-05-15 | FAD6058 | - | May 15, 04:55 UTC | May 15, 13:35 UTC | 8h 40m |
| 2026-05-14 | FAD6058 | - | May 14, 08:55 UTC | May 15, 05:45 UTC | 20h 50m |
| 2026-05-14 | FAD6071 | - | May 14, 07:10 UTC | May 14, 07:30 UTC | 20m |
| 2026-05-13 | FAD6070 | - | May 13, 23:00 UTC | May 14, 00:00 UTC | 1h 0m |
| 2026-05-12 | FAD6065 | - | May 12, 13:00 UTC | May 12, 13:30 UTC | 30m |
| 2026-05-12 | FAD6065 | - | May 12, 02:50 UTC | May 12, 11:25 UTC | 8h 35m |
| 2026-05-08 | FAD654 | SKT → RUH | May 8, 21:55 UTC | May 9, 06:20 UTC | 8h 25m |
| 2026-05-08 | FAD653 | RUH → SKT | May 8, 05:05 UTC | May 9, 03:25 UTC | 22h 20m |
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-FBJ page for operator, model, and routing details .