sensors Mode-S transponder
711486
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-RXX · BOEING 787-9 Dreamliner
- Hex
- 711486
- Octal
- 34212206
- Decimal
- 7,410,822
- Country
- SA
- Tail
- HZ-RXX
- Type
- B789
- Flights observed
- 173
- Distinct callsigns
- 2
- Country
- SA
- Last broadcast
- Jun 9, 12:55 UTC
Last known position
Country allocation
The ICAO 24-bit address 711486 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 2 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-09 | RXI402 | - | Jun 9, 08:55 UTC | Jun 9, 12:55 UTC | 4h 0m |
| 2026-06-08 | RXI401 | - | Jun 8, 11:35 UTC | Jun 9, 06:40 UTC | 19h 5m |
| 2026-06-08 | RXI401 | - | Jun 8, 09:35 UTC | Jun 9, 06:40 UTC | 21h 5m |
| 2026-06-08 | RXI401 | - | Jun 8, 08:45 UTC | Jun 9, 06:40 UTC | 21h 55m |
| 2026-06-07 | RXI401 | - | Jun 7, 11:35 UTC | Jun 8, 06:25 UTC | 18h 50m |
| 2026-06-07 | RXI401 | - | Jun 7, 09:35 UTC | Jun 8, 06:25 UTC | 20h 50m |
| 2026-06-07 | RXI401 | LHR → LHR | Jun 7, 09:05 UTC | Jun 8, 06:25 UTC | 21h 20m |
| 2026-06-06 | RXI401 | - | Jun 6, 11:35 UTC | Jun 7, 07:10 UTC | 19h 35m |
| 2026-06-06 | RXI401 | - | Jun 6, 09:39 UTC | Jun 7, 07:10 UTC | 21h 30m |
| 2026-06-06 | RXI401 | - | Jun 6, 02:35 UTC | Jun 6, 07:45 UTC | 5h 10m |
| 2026-06-05 | RXI401 | - | Jun 5, 11:35 UTC | Jun 6, 07:45 UTC | 20h 10m |
| 2026-06-05 | RXI401 | - | Jun 5, 09:35 UTC | Jun 6, 07:45 UTC | 22h 10m |
| 2026-06-05 | RXI401 | - | Jun 5, 08:55 UTC | Jun 6, 07:30 UTC | 22h 35m |
| 2026-06-04 | RXI401 | - | Jun 4, 11:35 UTC | Jun 5, 06:15 UTC | 18h 40m |
| 2026-06-04 | RXI401 | - | Jun 4, 09:35 UTC | Jun 5, 06:15 UTC | 20h 40m |
| 2026-06-04 | RXI401 | LHR → LHR | Jun 4, 09:05 UTC | Jun 5, 06:15 UTC | 21h 10m |
| 2026-06-03 | RXI401 | - | Jun 3, 11:35 UTC | Jun 4, 06:40 UTC | 19h 5m |
| 2026-06-03 | RXI401 | - | Jun 3, 09:35 UTC | Jun 4, 06:40 UTC | 21h 5m |
| 2026-06-03 | RXI401 | LHR → LHR | Jun 3, 09:05 UTC | Jun 4, 06:40 UTC | 21h 35m |
| 2026-06-02 | RXI401 | - | Jun 2, 11:35 UTC | Jun 3, 06:20 UTC | 18h 45m |
| 2026-06-02 | RXI401 | - | Jun 2, 09:35 UTC | Jun 3, 06:20 UTC | 20h 45m |
| 2026-06-02 | RXI401 | LHR → LHR | Jun 2, 09:00 UTC | Jun 3, 06:20 UTC | 21h 20m |
| 2026-06-01 | RXI401 | - | Jun 1, 11:35 UTC | Jun 2, 06:25 UTC | 18h 50m |
| 2026-06-01 | RXI401 | - | Jun 1, 09:35 UTC | Jun 2, 06:25 UTC | 20h 50m |
| 2026-06-01 | RXI401 | LHR → LHR | Jun 1, 08:45 UTC | Jun 2, 06:25 UTC | 21h 40m |
| 2026-05-31 | RXI401 | - | May 31, 12:30 UTC | Jun 1, 06:20 UTC | 17h 50m |
| 2026-05-31 | RXI402 | - | May 31, 09:20 UTC | May 31, 12:10 UTC | 2h 50m |
| 2026-05-30 | RXI402 | - | May 30, 09:10 UTC | May 30, 13:15 UTC | 4h 5m |
| 2026-05-29 | RXI401 | - | May 29, 11:35 UTC | May 30, 06:30 UTC | 18h 56m |
| 2026-05-29 | RXI401 | - | May 29, 09:35 UTC | May 30, 06:30 UTC | 20h 55m |
| 2026-05-29 | RXI401 | - | May 29, 09:10 UTC | May 30, 06:30 UTC | 21h 20m |
| 2026-05-28 | RXI401 | - | May 28, 11:45 UTC | May 29, 06:40 UTC | 18h 55m |
| 2026-05-28 | RXI401 | - | May 28, 09:35 UTC | May 29, 06:40 UTC | 21h 5m |
| 2026-05-28 | RXI401 | - | May 28, 08:35 UTC | May 29, 06:40 UTC | 22h 5m |
| 2026-05-27 | RXI401 | - | May 27, 11:35 UTC | May 28, 06:15 UTC | 18h 40m |
| 2026-05-27 | RXI401 | - | May 27, 09:35 UTC | May 28, 06:15 UTC | 20h 40m |
| 2026-05-27 | RXI401 | - | May 27, 08:35 UTC | May 28, 06:15 UTC | 21h 40m |
| 2026-05-26 | RXI401 | - | May 26, 11:34 UTC | May 27, 05:55 UTC | 18h 20m |
| 2026-05-26 | RXI401 | - | May 26, 09:35 UTC | May 27, 05:55 UTC | 20h 20m |
| 2026-05-26 | RXI401 | - | May 26, 09:04 UTC | May 27, 05:55 UTC | 20h 50m |
| 2026-05-25 | RXI401 | - | May 25, 11:35 UTC | May 26, 06:25 UTC | 18h 49m |
| 2026-05-25 | RXI401 | - | May 25, 09:35 UTC | May 26, 06:25 UTC | 20h 50m |
| 2026-05-25 | RXI401 | - | May 25, 09:05 UTC | May 26, 06:25 UTC | 21h 20m |
| 2026-05-24 | RXI401 | - | May 24, 11:35 UTC | May 25, 06:25 UTC | 18h 50m |
| 2026-05-24 | RXI401 | - | May 24, 09:35 UTC | May 25, 06:25 UTC | 20h 50m |
| 2026-05-24 | RXI401 | LHR → LHR | May 24, 08:40 UTC | May 25, 06:25 UTC | 21h 45m |
| 2026-05-23 | RXI401 | - | May 23, 11:35 UTC | May 24, 06:15 UTC | 18h 40m |
| 2026-05-23 | RXI401 | - | May 23, 09:35 UTC | May 24, 06:15 UTC | 20h 40m |
| 2026-05-23 | RXI401 | LHR → LHR | May 23, 08:35 UTC | May 24, 06:15 UTC | 21h 40m |
| 2026-05-22 | RXI401 | - | May 22, 11:35 UTC | May 23, 06:20 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-RXX page for operator, model, and routing details .