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