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
- 104
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 1h 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 | 7 | 2026-06-20 |
| FAD665 | - | 7 | 2026-07-11 |
| FAD461 | Rog-Air | 6 | 2026-04-29 |
| FAD808 | - | 5 | 2026-06-20 |
| FAD505 | - | 5 | 2026-07-08 |
| FAD911 | Rog-Air | 4 | 2026-04-27 |
| FAD607 | - | 4 | 2026-07-11 |
| FAD574 | - | 4 | 2026-07-12 |
| FAD573 | - | 4 | 2026-07-14 |
| FAD761 | Rog-Air | 3 | 2026-05-29 |
| FAD655 | - | 3 | 2026-07-06 |
| FAD615 | Rog-Air | 3 | 2026-05-08 |
| FAD511 | - | 3 | 2026-07-13 |
| FAD443 | Rog-Air | 3 | 2026-05-13 |
| FAD829 | Rog-Air | 2 | 2026-06-18 |
| FAD764 | Rog-Air | 2 | 2026-06-26 |
| FAD763 | Rog-Air | 2 | 2026-06-26 |
| FAD755 | Rog-Air | 2 | 2026-05-28 |
| FAD7394 | - | 2 | 2026-06-03 |
| FAD7078 | Rog-Air | 2 | 2026-06-04 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | FAD573 | - | Jul 14, 03:15 UTC | Jul 14, 15:30 UTC | 12h 15m |
| 2026-07-13 | FAD653 | - | Jul 13, 17:50 UTC | Jul 14, 01:15 UTC | 7h 25m |
| 2026-07-13 | FAD511 | - | Jul 13, 15:05 UTC | Jul 13, 16:25 UTC | 1h 20m |
| 2026-07-12 | FAD511 | - | Jul 12, 19:35 UTC | Jul 13, 16:25 UTC | 20h 50m |
| 2026-07-12 | FAD574 | - | Jul 12, 18:25 UTC | Jul 13, 16:25 UTC | 22h 0m |
| 2026-07-11 | FAD665 | - | Jul 11, 21:35 UTC | Jul 12, 15:50 UTC | 18h 15m |
| 2026-07-11 | FAD665 | - | Jul 11, 21:25 UTC | Jul 12, 15:50 UTC | 18h 25m |
| 2026-07-11 | FAD665 | - | Jul 11, 13:00 UTC | Jul 12, 06:40 UTC | 17h 40m |
| 2026-07-11 | FAD607 | - | Jul 11, 10:40 UTC | Jul 11, 11:05 UTC | 25m |
| 2026-07-10 | FAD606 | - | Jul 10, 11:10 UTC | Jul 10, 11:20 UTC | 10m |
| 2026-07-10 | FAD605 | - | Jul 10, 09:00 UTC | Jul 10, 09:25 UTC | 25m |
| 2026-07-09 | FAD506 | - | Jul 9, 09:35 UTC | Jul 10, 09:25 UTC | 23h 50m |
| 2026-07-08 | FAD505 | - | Jul 8, 18:20 UTC | Jul 9, 08:00 UTC | 13h 40m |
| 2026-07-08 | FAD511 | - | Jul 8, 15:20 UTC | Jul 8, 16:40 UTC | 1h 20m |
| 2026-07-06 | FAD665 | - | Jul 6, 11:35 UTC | Jul 7, 06:20 UTC | 18h 45m |
| 2026-07-06 | FAD665 | - | Jul 6, 11:20 UTC | Jul 7, 06:20 UTC | 19h 0m |
| 2026-07-06 | FAD665 | - | Jul 6, 09:00 UTC | Jul 7, 06:20 UTC | 21h 20m |
| 2026-07-06 | FAD655 | - | Jul 6, 03:40 UTC | Jul 6, 06:45 UTC | 3h 5m |
| 2026-07-03 | FAD665 | - | Jul 3, 21:10 UTC | Jul 4, 06:35 UTC | 9h 25m |
| 2026-07-01 | FAD661 | RUH → KHI | Jul 1, 09:35 UTC | Jul 2, 05:20 UTC | 19h 45m |
| 2026-07-01 | FAD578 | - | Jul 1, 09:20 UTC | Jul 2, 05:20 UTC | 20h 0m |
| 2026-07-01 | FAD577 | - | Jul 1, 07:40 UTC | Jul 1, 08:05 UTC | 25m |
| 2026-06-29 | FAD608 | CAI → RUH | Jun 29, 13:24 UTC | Jun 29, 13:39 UTC | 15m |
| 2026-06-29 | FAD607 | - | Jun 29, 11:20 UTC | Jun 29, 11:45 UTC | 25m |
| 2026-06-28 | FAD608 | CAI → RUH | Jun 28, 13:04 UTC | Jun 29, 11:29 UTC | 22h 25m |
| 2026-06-28 | FAD607 | - | Jun 28, 11:00 UTC | Jun 28, 11:19 UTC | 20m |
| 2026-06-26 | FAD764 | CAI → JED | Jun 26, 21:45 UTC | Jun 26, 21:55 UTC | 10m |
| 2026-06-26 | FAD763 | JED → CAI | Jun 26, 13:10 UTC | Jun 26, 20:10 UTC | 7h 0m |
| 2026-06-20 | FAD808 | - | Jun 20, 20:14 UTC | Jun 20, 22:14 UTC | 2h 0m |
| 2026-06-20 | FAD807 | JED → IST | Jun 20, 00:04 UTC | Jun 20, 18:10 UTC | 18h 5m |
| 2026-06-18 | FAD829 | JED → KHI | Jun 18, 23:10 UTC | Jun 19, 00:14 UTC | 1h 4m |
| 2026-06-14 | FAD505 | RUH → DXB | Jun 14, 06:35 UTC | Jun 14, 10:05 UTC | 3h 30m |
| 2026-06-07 | FAD322 | DMM → JED | Jun 7, 00:05 UTC | Jun 7, 00:14 UTC | 10m |
| 2026-06-05 | FAD7067 | - | Jun 5, 05:40 UTC | Jun 5, 13:45 UTC | 8h 5m |
| 2026-06-04 | FAD7078 | JED → OSS | Jun 4, 10:35 UTC | Jun 5, 04:15 UTC | 17h 40m |
| 2026-06-03 | FAD7078 | JED → OSS | Jun 3, 23:15 UTC | Jun 4, 09:15 UTC | 10h 0m |
| 2026-06-03 | FAD7394 | - | Jun 3, 03:00 UTC | Jun 3, 10:45 UTC | 7h 45m |
| 2026-06-02 | FAD7394 | - | Jun 2, 07:15 UTC | Jun 3, 05:30 UTC | 22h 14m |
| 2026-06-01 | FAD764 | CAI → JED | Jun 1, 22:15 UTC | Jun 2, 05:25 UTC | 7h 10m |
| 2026-06-01 | FAD763 | JED → CAI | Jun 1, 20:05 UTC | Jun 1, 20:40 UTC | 35m |
| 2026-05-30 | FAD318 | DMM → JED | May 30, 18:55 UTC | May 31, 08:25 UTC | 13h 30m |
| 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 |
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 .