sensors Mode-S transponder
71012A
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-FAE · AIRBUS A-320
- Hex
- 71012A
- Octal
- 34200452
- Decimal
- 7,405,866
- Country
- SA
- Tail
- HZ-FAE
- Type
- A320
- Flights observed
- 34
- Distinct callsigns
- 17
- Country
- SA
- Last broadcast
- 12h ago
Last known position
Country allocation
The ICAO 24-bit address 71012A 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 17 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| FAD911 | Rog-Air | 8 | 2026-05-19 |
| FAD465 | Rog-Air | 6 | 2026-05-16 |
| FAD616 | Rog-Air | 3 | 2026-05-29 |
| FAD615 | Rog-Air | 3 | 2026-05-29 |
| FAD455 | Rog-Air | 2 | 2026-04-23 |
| FAD607 | Rog-Air | 1 | 2026-04-26 |
| FAD605 | Rog-Air | 1 | 2026-05-22 |
| FAD497 | Rog-Air | 1 | 2026-05-01 |
| FAD485 | Rog-Air | 1 | 2026-04-30 |
| FAD471 | - | 1 | 2026-05-09 |
| FAD466 | Rog-Air | 1 | 2026-04-22 |
| FAD463 | Rog-Air | 1 | 2026-04-28 |
| FAD457 | - | 1 | 2026-04-29 |
| FAD456 | Rog-Air | 1 | 2026-04-23 |
| FAD437 | Rog-Air | 1 | 2026-05-02 |
| FAD432 | - | 1 | 2026-04-23 |
| FAD186 | Rog-Air | 1 | 2026-04-24 |
Recent flights last 34
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | FAD616 | CAI → RUH | May 29, 23:50 UTC | May 30, 00:00 UTC | 10m |
| 2026-05-29 | FAD615 | RUH → CAI | May 29, 21:55 UTC | May 29, 22:20 UTC | 25m |
| 2026-05-25 | FAD616 | CAI → RUH | May 25, 23:49 UTC | May 26, 00:00 UTC | 10m |
| 2026-05-25 | FAD615 | RUH → CAI | May 25, 22:00 UTC | May 25, 22:19 UTC | 20m |
| 2026-05-22 | FAD616 | CAI → RUH | May 22, 23:45 UTC | May 22, 23:55 UTC | 10m |
| 2026-05-22 | FAD615 | RUH → CAI | May 22, 11:20 UTC | May 22, 22:20 UTC | 11h 0m |
| 2026-05-22 | FAD605 | RUH → CAI | May 22, 09:25 UTC | May 22, 09:45 UTC | 20m |
| 2026-05-19 | FAD911 | DMM → CAI | May 19, 06:35 UTC | May 19, 16:15 UTC | 9h 40m |
| 2026-05-18 | FAD911 | DMM → CAI | May 18, 06:20 UTC | May 18, 06:45 UTC | 25m |
| 2026-05-16 | FAD465 | DMM → MED | May 16, 18:05 UTC | May 16, 22:00 UTC | 3h 55m |
| 2026-05-14 | FAD911 | DMM → CAI | May 14, 06:20 UTC | May 14, 06:35 UTC | 15m |
| 2026-05-13 | FAD911 | DMM → CAI | May 13, 12:25 UTC | May 14, 06:35 UTC | 18h 10m |
| 2026-05-09 | FAD471 | - | May 9, 08:35 UTC | May 9, 20:10 UTC | 11h 35m |
| 2026-05-09 | FAD911 | DMM → CAI | May 9, 06:05 UTC | May 9, 06:25 UTC | 20m |
| 2026-05-05 | FAD911 | DMM → CAI | May 5, 06:30 UTC | May 5, 06:50 UTC | 20m |
| 2026-05-02 | FAD437 | DMM → AHB | May 2, 20:05 UTC | May 3, 12:15 UTC | 16h 9m |
| 2026-05-01 | FAD465 | DMM → MED | May 1, 18:10 UTC | May 1, 18:20 UTC | 10m |
| 2026-05-01 | FAD497 | DMM → EAM | May 1, 06:35 UTC | May 1, 12:10 UTC | 5h 35m |
| 2026-04-30 | FAD485 | DMM → NUM | Apr 30, 12:45 UTC | May 1, 12:10 UTC | 23h 25m |
| 2026-04-30 | FAD911 | DMM → CAI | Apr 30, 04:10 UTC | Apr 30, 06:50 UTC | 2h 40m |
| 2026-04-29 | FAD465 | DMM → MED | Apr 29, 17:55 UTC | Apr 29, 18:10 UTC | 15m |
| 2026-04-29 | FAD457 | - | Apr 29, 06:39 UTC | Apr 29, 06:49 UTC | 10m |
| 2026-04-28 | FAD463 | DMM → MED | Apr 28, 12:40 UTC | Apr 28, 12:50 UTC | 10m |
| 2026-04-28 | FAD911 | DMM → CAI | Apr 28, 06:45 UTC | Apr 28, 06:55 UTC | 10m |
| 2026-04-26 | FAD607 | RUH → CAI | Apr 26, 11:05 UTC | Apr 26, 11:30 UTC | 25m |
| 2026-04-24 | FAD186 | DMM → RUH | Apr 24, 18:45 UTC | Apr 24, 18:55 UTC | 10m |
| 2026-04-23 | FAD465 | DMM → MED | Apr 23, 18:15 UTC | Apr 24, 05:10 UTC | 10h 55m |
| 2026-04-23 | FAD432 | - | Apr 23, 16:25 UTC | Apr 23, 16:35 UTC | 10m |
| 2026-04-23 | FAD456 | ABT → DMM | Apr 23, 10:40 UTC | Apr 23, 10:50 UTC | 10m |
| 2026-04-23 | FAD455 | DMM → ABT | Apr 23, 06:45 UTC | Apr 23, 07:01 UTC | 15m |
| 2026-04-22 | FAD466 | MED → DMM | Apr 22, 22:05 UTC | Apr 22, 22:30 UTC | 25m |
| 2026-04-19 | FAD465 | DMM → MED | Apr 19, 18:10 UTC | Apr 19, 18:20 UTC | 10m |
| 2026-04-13 | FAD465 | - | Apr 13, 18:00 UTC | Apr 13, 18:10 UTC | 10m |
| 2026-04-13 | FAD455 | - | Apr 13, 06:40 UTC | Apr 13, 06:50 UTC | 10m |
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-FAE page for operator, model, and routing details .