sensors Mode-S transponder
71152E
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-FBH · AIRBUS A-320neo
- Hex
- 71152E
- Octal
- 34212456
- Decimal
- 7,410,990
- Country
- SA
- Tail
- HZ-FBH
- Type
- A20N
- Flights observed
- 63
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 17h ago
Last known position
Country allocation
The ICAO 24-bit address 71152E 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-05-24 |
| FAD461 | Rog-Air | 6 | 2026-04-29 |
| FAD911 | Rog-Air | 4 | 2026-04-27 |
| FAD808 | Rog-Air | 4 | 2026-05-24 |
| FAD761 | Rog-Air | 3 | 2026-05-29 |
| FAD615 | Rog-Air | 3 | 2026-05-08 |
| FAD574 | Rog-Air | 3 | 2026-05-16 |
| FAD573 | Rog-Air | 3 | 2026-05-15 |
| FAD505 | Rog-Air | 3 | 2026-05-07 |
| FAD443 | Rog-Air | 3 | 2026-05-13 |
| FAD755 | Rog-Air | 2 | 2026-05-28 |
| FAD701 | Rog-Air | 2 | 2026-04-22 |
| FAD655 | Rog-Air | 2 | 2026-05-17 |
| FAD481 | - | 2 | 2026-04-19 |
| FAD471 | - | 2 | 2026-04-25 |
| FAD465 | Rog-Air | 2 | 2026-04-26 |
| FAD1437 | Rog-Air | 2 | 2026-04-29 |
| FAD829 | Rog-Air | 1 | 2026-04-22 |
| FAD762 | Rog-Air | 1 | 2026-05-29 |
| FAD702 | - | 1 | 2026-04-22 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | FAD762 | CAI → JED | May 29, 18:55 UTC | May 29, 19:15 UTC | 20m |
| 2026-05-29 | FAD761 | JED → CAI | May 29, 16:40 UTC | May 29, 17:00 UTC | 20m |
| 2026-05-28 | FAD761 | JED → CAI | May 28, 18:50 UTC | May 29, 17:00 UTC | 22h 11m |
| 2026-05-28 | FAD761 | JED → CAI | May 28, 09:10 UTC | May 28, 16:55 UTC | 7h 45m |
| 2026-05-28 | FAD755 | JED → CAI | May 28, 07:00 UTC | May 28, 07:15 UTC | 15m |
| 2026-05-27 | FAD755 | JED → CAI | May 27, 11:10 UTC | May 28, 07:15 UTC | 20h 5m |
| 2026-05-24 | FAD808 | IST → JED | May 24, 20:35 UTC | May 24, 21:45 UTC | 1h 10m |
| 2026-05-24 | FAD807 | JED → IST | May 24, 16:40 UTC | May 24, 18:45 UTC | 2h 5m |
| 2026-05-23 | FAD807 | JED → IST | May 23, 21:35 UTC | May 24, 18:45 UTC | 21h 10m |
| 2026-05-23 | FAD808 | IST → JED | May 23, 20:15 UTC | May 24, 18:45 UTC | 22h 30m |
| 2026-05-23 | FAD807 | JED → IST | May 23, 16:30 UTC | May 23, 18:30 UTC | 2h 1m |
| 2026-05-22 | FAD807 | JED → IST | May 22, 23:30 UTC | May 23, 18:30 UTC | 19h 0m |
| 2026-05-21 | FAD808 | IST → JED | May 21, 20:20 UTC | May 21, 22:05 UTC | 1h 45m |
| 2026-05-21 | FAD807 | JED → IST | May 21, 16:30 UTC | May 21, 18:35 UTC | 2h 5m |
| 2026-05-20 | FAD808 | IST → JED | May 20, 21:05 UTC | May 21, 18:35 UTC | 21h 30m |
| 2026-05-20 | FAD807 | JED → IST | May 20, 11:20 UTC | May 20, 18:30 UTC | 7h 10m |
| 2026-05-19 | FAD6765 | AMM → AMM | May 19, 08:50 UTC | May 19, 09:10 UTC | 20m |
| 2026-05-19 | FAD6764 | - | May 19, 06:20 UTC | May 19, 06:50 UTC | 30m |
| 2026-05-18 | FAD656 | LHE → RUH | May 18, 02:55 UTC | May 18, 11:20 UTC | 8h 25m |
| 2026-05-17 | FAD655 | RUH → LHE | May 17, 21:45 UTC | May 18, 00:50 UTC | 3h 5m |
| 2026-05-16 | FAD574 | IST → RUH | May 16, 18:25 UTC | May 16, 20:05 UTC | 1h 40m |
| 2026-05-15 | FAD573 | RUH → IST | May 15, 19:35 UTC | May 16, 16:31 UTC | 20h 56m |
| 2026-05-15 | FAD574 | IST → RUH | May 15, 18:30 UTC | May 16, 16:31 UTC | 22h 1m |
| 2026-05-15 | FAD573 | RUH → IST | May 15, 02:40 UTC | May 15, 15:55 UTC | 13h 14m |
| 2026-05-14 | FAD655 | RUH → LHE | May 14, 21:45 UTC | May 15, 00:30 UTC | 2h 45m |
| 2026-05-13 | FAD443 | DMM → GIZ | May 13, 10:45 UTC | May 13, 10:55 UTC | 10m |
| 2026-05-08 | FAD616 | CAI → RUH | May 8, 23:45 UTC | May 9, 00:00 UTC | 15m |
| 2026-05-08 | FAD615 | RUH → CAI | May 8, 05:14 UTC | May 8, 22:30 UTC | 17h 15m |
| 2026-05-08 | FAD615 | RUH → CAI | May 8, 03:04 UTC | May 8, 22:30 UTC | 19h 25m |
| 2026-05-08 | FAD615 | RUH → CAI | May 8, 00:29 UTC | May 8, 22:30 UTC | 22h 0m |
| 2026-05-07 | FAD505 | RUH → DXB | May 7, 06:15 UTC | May 8, 05:24 UTC | 23h 10m |
| 2026-05-06 | FAD505 | RUH → DXB | May 6, 13:10 UTC | May 7, 07:00 UTC | 17h 49m |
| 2026-05-06 | FAD607 | RUH → CAI | May 6, 10:50 UTC | May 6, 11:15 UTC | 25m |
| 2026-05-03 | FAD574 | IST → RUH | May 3, 18:20 UTC | May 3, 20:10 UTC | 1h 50m |
| 2026-05-03 | FAD573 | RUH → IST | May 3, 09:00 UTC | May 3, 15:55 UTC | 6h 55m |
| 2026-05-03 | FAD505 | RUH → DXB | May 3, 06:05 UTC | May 3, 07:35 UTC | 1h 30m |
| 2026-04-29 | FAD1437 | DMM → AHB | Apr 29, 18:00 UTC | Apr 29, 18:10 UTC | 10m |
| 2026-04-29 | FAD461 | DMM → MED | Apr 29, 05:20 UTC | Apr 29, 05:30 UTC | 10m |
| 2026-04-28 | - | - | Apr 28, 05:10 UTC | Apr 28, 05:20 UTC | 10m |
| 2026-04-27 | FAD463 | DMM → MED | Apr 27, 12:25 UTC | Apr 27, 17:45 UTC | 5h 20m |
| 2026-04-27 | FAD911 | DMM → CAI | Apr 27, 04:20 UTC | Apr 27, 06:45 UTC | 2h 25m |
| 2026-04-26 | FAD465 | DMM → MED | Apr 26, 18:00 UTC | Apr 26, 18:10 UTC | 10m |
| 2026-04-26 | FAD461 | DMM → MED | Apr 26, 05:05 UTC | Apr 26, 10:50 UTC | 5h 45m |
| 2026-04-25 | FAD471 | - | Apr 25, 17:25 UTC | Apr 25, 17:35 UTC | 10m |
| 2026-04-25 | FAD461 | DMM → MED | Apr 25, 05:15 UTC | Apr 25, 10:55 UTC | 5h 40m |
| 2026-04-24 | FAD461 | DMM → MED | Apr 24, 12:05 UTC | Apr 25, 10:55 UTC | 22h 50m |
| 2026-04-24 | FAD911 | DMM → CAI | Apr 24, 04:20 UTC | Apr 24, 06:50 UTC | 2h 30m |
| 2026-04-22 | FAD829 | JED → KHI | Apr 22, 22:55 UTC | Apr 23, 15:10 UTC | 16h 15m |
| 2026-04-22 | FAD702 | - | Apr 22, 12:00 UTC | Apr 23, 04:20 UTC | 16h 20m |
| 2026-04-22 | FAD701 | JED → MCT | Apr 22, 08:01 UTC | Apr 22, 09:10 UTC | 1h 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-FBH page for operator, model, and routing details .