sensors Mode-S transponder
711539
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-FBG · AIRBUS A-320neo
- Hex
- 711539
- Octal
- 34212471
- Decimal
- 7,411,001
- Country
- SA
- Tail
- HZ-FBG
- Type
- A20N
- Flights observed
- 64
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address 711539 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 |
|---|---|---|---|
| FAD807 | Rog-Air | 6 | 2026-06-27 |
| FAD808 | - | 5 | 2026-06-28 |
| FAD7036 | Rog-Air | 3 | 2026-06-04 |
| FAD665 | - | 3 | 2026-07-13 |
| FAD661 | - | 3 | 2026-07-10 |
| FAD607 | Rog-Air | 3 | 2026-05-14 |
| FAD829 | Rog-Air | 2 | 2026-06-19 |
| FAD810 | - | 2 | 2026-06-27 |
| FAD753 | - | 2 | 2026-06-25 |
| FAD7072 | Rog-Air | 2 | 2026-06-06 |
| FAD666 | - | 2 | 2026-07-10 |
| FAD653 | Rog-Air | 2 | 2026-05-15 |
| FAD608 | Rog-Air | 2 | 2026-05-04 |
| FAD451 | Rog-Air | 2 | 2026-04-27 |
| FAD826 | - | 1 | 2026-07-02 |
| FAD825 | - | 1 | 2026-07-02 |
| FAD8114 | - | 1 | 2026-04-14 |
| FAD809 | Rog-Air | 1 | 2026-06-26 |
| FAD761 | Rog-Air | 1 | 2026-05-20 |
| FAD756 | Rog-Air | 1 | 2026-07-03 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | FAD665 | - | Jul 13, 21:20 UTC | Jul 14, 06:15 UTC | 8h 55m |
| 2026-07-10 | FAD661 | - | Jul 10, 22:55 UTC | Jul 11, 05:20 UTC | 6h 25m |
| 2026-07-10 | FAD661 | - | Jul 10, 06:20 UTC | Jul 11, 05:20 UTC | 23h 0m |
| 2026-07-10 | FAD661 | - | Jul 10, 04:25 UTC | Jul 11, 00:20 UTC | 19h 55m |
| 2026-07-10 | FAD666 | - | Jul 10, 03:45 UTC | Jul 11, 00:20 UTC | 20h 35m |
| 2026-07-10 | FAD666 | - | Jul 10, 00:20 UTC | Jul 11, 00:15 UTC | 23h 55m |
| 2026-07-09 | FAD665 | - | Jul 9, 21:20 UTC | Jul 10, 06:55 UTC | 9h 35m |
| 2026-07-07 | FAD665 | - | Jul 7, 21:40 UTC | Jul 8, 06:40 UTC | 9h 0m |
| 2026-07-05 | FAD658 | - | Jul 5, 21:05 UTC | Jul 6, 11:25 UTC | 14h 20m |
| 2026-07-04 | FAD544 | - | Jul 4, 13:30 UTC | Jul 4, 14:00 UTC | 30m |
| 2026-07-04 | FAD543 | - | Jul 4, 11:35 UTC | Jul 4, 12:20 UTC | 45m |
| 2026-07-03 | FAD756 | CAI → JED | Jul 3, 09:10 UTC | Jul 3, 09:20 UTC | 10m |
| 2026-07-02 | FAD826 | - | Jul 2, 14:40 UTC | Jul 3, 06:55 UTC | 16h 15m |
| 2026-07-02 | FAD825 | - | Jul 2, 09:15 UTC | Jul 2, 12:30 UTC | 3h 15m |
| 2026-06-28 | FAD808 | - | Jun 28, 19:59 UTC | Jun 28, 21:59 UTC | 2h 0m |
| 2026-06-27 | FAD807 | JED → IST | Jun 27, 23:00 UTC | Jun 28, 18:14 UTC | 19h 15m |
| 2026-06-27 | FAD810 | - | Jun 27, 02:20 UTC | Jun 28, 00:09 UTC | 21h 50m |
| 2026-06-27 | FAD810 | - | Jun 27, 02:04 UTC | Jun 28, 00:09 UTC | 22h 5m |
| 2026-06-26 | FAD809 | JED → SAW | Jun 26, 22:19 UTC | Jun 27, 00:14 UTC | 1h 55m |
| 2026-06-25 | FAD808 | - | Jun 25, 19:59 UTC | Jun 25, 21:55 UTC | 1h 55m |
| 2026-06-25 | FAD807 | JED → IST | Jun 25, 16:20 UTC | Jun 25, 18:24 UTC | 2h 5m |
| 2026-06-25 | FAD753 | - | Jun 25, 05:05 UTC | Jun 25, 05:20 UTC | 15m |
| 2026-06-19 | FAD829 | JED → KHI | Jun 19, 23:09 UTC | Jun 19, 23:29 UTC | 20m |
| 2026-06-06 | FAD7072 | JED → OSS | Jun 6, 12:49 UTC | Jun 6, 20:45 UTC | 7h 55m |
| 2026-06-05 | FAD7072 | JED → OSS | Jun 5, 23:25 UTC | Jun 6, 11:14 UTC | 11h 50m |
| 2026-06-05 | FAD7037 | - | Jun 5, 04:30 UTC | Jun 5, 21:45 UTC | 17h 15m |
| 2026-06-04 | FAD7036 | JED → OSS | Jun 4, 18:45 UTC | Jun 5, 05:00 UTC | 10h 15m |
| 2026-06-04 | FAD7036 | JED → OSS | Jun 4, 04:25 UTC | Jun 4, 17:40 UTC | 13h 15m |
| 2026-06-03 | FAD7036 | JED → OSS | Jun 3, 21:05 UTC | Jun 4, 17:40 UTC | 20h 35m |
| 2026-06-03 | FAD7048 | JED → OSS | Jun 3, 19:35 UTC | Jun 3, 20:05 UTC | 30m |
| 2026-05-31 | FAD808 | IST → JED | May 31, 20:30 UTC | May 31, 22:20 UTC | 1h 50m |
| 2026-05-31 | FAD807 | JED → IST | May 31, 16:25 UTC | May 31, 18:40 UTC | 2h 15m |
| 2026-05-28 | FAD754 | CAI → JED | May 28, 06:55 UTC | May 28, 07:05 UTC | 10m |
| 2026-05-28 | FAD753 | JED → CAI | May 28, 05:00 UTC | May 28, 05:20 UTC | 20m |
| 2026-05-25 | FAD829 | JED → KHI | May 25, 23:00 UTC | May 25, 23:24 UTC | 25m |
| 2026-05-23 | FAD6797 | AMM → AMM | May 23, 09:25 UTC | May 23, 09:50 UTC | 25m |
| 2026-05-22 | FAD808 | IST → JED | May 22, 20:15 UTC | May 23, 06:50 UTC | 10h 35m |
| 2026-05-22 | FAD807 | JED → IST | May 22, 16:20 UTC | May 22, 18:20 UTC | 2h 0m |
| 2026-05-21 | FAD807 | JED → IST | May 21, 23:25 UTC | May 22, 18:20 UTC | 18h 55m |
| 2026-05-21 | FAD6743 | AMM → AMM | May 21, 14:15 UTC | May 21, 14:40 UTC | 25m |
| 2026-05-20 | FAD6742 | - | May 20, 19:20 UTC | May 21, 12:25 UTC | 17h 5m |
| 2026-05-20 | FAD761 | JED → CAI | May 20, 16:50 UTC | May 20, 17:05 UTC | 15m |
| 2026-05-19 | FAD808 | IST → JED | May 19, 20:05 UTC | May 20, 10:20 UTC | 14h 16m |
| 2026-05-19 | FAD807 | JED → IST | May 19, 16:20 UTC | May 19, 18:25 UTC | 2h 5m |
| 2026-05-15 | FAD653 | RUH → SKT | May 15, 12:50 UTC | May 16, 06:41 UTC | 17h 50m |
| 2026-05-14 | FAD607 | RUH → CAI | May 14, 21:40 UTC | May 15, 11:15 UTC | 13h 35m |
| 2026-05-14 | FAD651 | RUH → ISB | May 14, 11:20 UTC | May 15, 02:55 UTC | 15h 35m |
| 2026-05-13 | FAD574 | IST → RUH | May 13, 18:25 UTC | May 14, 09:50 UTC | 15h 25m |
| 2026-05-13 | FAD573 | RUH → IST | May 13, 14:00 UTC | May 13, 15:45 UTC | 1h 45m |
| 2026-05-06 | FAD653 | RUH → SKT | May 6, 22:00 UTC | May 7, 03:25 UTC | 5h 25m |
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-FBG page for operator, model, and routing details .