sensors Mode-S transponder
71157C
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-FBF · AIRBUS A-320neo
- Hex
- 71157C
- Octal
- 34212574
- Decimal
- 7,411,068
- Country
- SA
- Tail
- HZ-FBF
- Type
- A20N
- Flights observed
- 45
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 15h ago
Last known position
Country allocation
The ICAO 24-bit address 71157C 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 |
|---|---|---|---|
| FAD775 | Rog-Air | 8 | 2026-06-30 |
| FAD771 | - | 5 | 2026-07-02 |
| FAD829 | - | 3 | 2026-07-07 |
| FAD776 | Rog-Air | 3 | 2026-05-31 |
| FAD505 | - | 3 | 2026-06-24 |
| FAD813 | - | 2 | 2026-07-07 |
| FAD811 | - | 2 | 2026-07-04 |
| FAD772 | - | 2 | 2026-07-04 |
| FAD506 | - | 2 | 2026-06-24 |
| FAD427 | Rog-Air | 2 | 2026-07-04 |
| FAD816 | - | 1 | 2026-07-06 |
| FAD815 | - | 1 | 2026-07-05 |
| FAD812 | - | 1 | 2026-07-03 |
| FAD810 | - | 1 | 2026-07-09 |
| FAD809 | - | 1 | 2026-07-08 |
| FAD754 | - | 1 | 2026-06-16 |
| FAD753 | - | 1 | 2026-06-16 |
| FAD651 | Rog-Air | 1 | 2026-05-16 |
| FAD467 | Rog-Air | 1 | 2026-06-02 |
| FAD430 | - | 1 | 2026-07-09 |
Recent flights last 45
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-09 | FAD430 | - | Jul 9, 10:15 UTC | Jul 9, 10:25 UTC | 10m |
| 2026-07-09 | FAD810 | - | Jul 9, 01:50 UTC | Jul 9, 03:40 UTC | 1h 50m |
| 2026-07-08 | FAD809 | - | Jul 8, 22:30 UTC | Jul 9, 00:15 UTC | 1h 45m |
| 2026-07-07 | FAD829 | - | Jul 7, 23:10 UTC | Jul 8, 23:00 UTC | 23h 50m |
| 2026-07-07 | FAD829 | - | Jul 7, 12:40 UTC | Jul 8, 00:10 UTC | 11h 30m |
| 2026-07-07 | FAD813 | - | Jul 7, 10:15 UTC | Jul 7, 10:40 UTC | 25m |
| 2026-07-07 | FAD813 | - | Jul 7, 09:10 UTC | Jul 7, 09:45 UTC | 35m |
| 2026-07-06 | FAD816 | - | Jul 6, 06:05 UTC | Jul 6, 07:55 UTC | 1h 50m |
| 2026-07-05 | FAD815 | - | Jul 5, 11:55 UTC | Jul 6, 04:50 UTC | 16h 55m |
| 2026-07-04 | FAD811 | - | Jul 4, 18:45 UTC | Jul 5, 10:00 UTC | 15h 15m |
| 2026-07-04 | FAD427 | MED → HOF | Jul 4, 17:15 UTC | Jul 4, 17:25 UTC | 10m |
| 2026-07-04 | FAD772 | - | Jul 4, 07:30 UTC | Jul 4, 07:40 UTC | 10m |
| 2026-07-03 | FAD812 | - | Jul 3, 12:10 UTC | Jul 4, 05:15 UTC | 17h 5m |
| 2026-07-02 | FAD811 | - | Jul 2, 18:40 UTC | Jul 3, 10:05 UTC | 15h 25m |
| 2026-07-02 | FAD427 | MED → HOF | Jul 2, 07:15 UTC | Jul 2, 17:30 UTC | 10h 15m |
| 2026-07-02 | FAD771 | - | Jul 2, 05:00 UTC | Jul 2, 05:20 UTC | 20m |
| 2026-07-01 | FAD771 | - | Jul 1, 07:35 UTC | Jul 2, 05:20 UTC | 21h 45m |
| 2026-06-30 | FAD771 | - | Jun 30, 20:30 UTC | Jul 1, 05:15 UTC | 8h 45m |
| 2026-06-30 | FAD775 | MED → CAI | Jun 30, 17:50 UTC | Jun 30, 18:35 UTC | 45m |
| 2026-06-28 | FAD772 | - | Jun 28, 07:29 UTC | Jun 28, 07:44 UTC | 15m |
| 2026-06-28 | FAD771 | - | Jun 28, 04:59 UTC | Jun 28, 05:29 UTC | 30m |
| 2026-06-24 | FAD506 | - | Jun 24, 09:09 UTC | Jun 24, 09:59 UTC | 50m |
| 2026-06-24 | FAD505 | - | Jun 24, 06:29 UTC | Jun 24, 07:59 UTC | 1h 30m |
| 2026-06-22 | FAD506 | - | Jun 22, 09:00 UTC | Jun 22, 09:54 UTC | 55m |
| 2026-06-22 | FAD505 | - | Jun 22, 06:25 UTC | Jun 22, 07:49 UTC | 1h 25m |
| 2026-06-16 | FAD754 | - | Jun 16, 07:05 UTC | Jun 16, 07:20 UTC | 15m |
| 2026-06-16 | FAD753 | - | Jun 16, 05:00 UTC | Jun 16, 05:15 UTC | 15m |
| 2026-06-14 | FAD324 | DMM → JED | Jun 14, 23:25 UTC | Jun 14, 23:35 UTC | 10m |
| 2026-06-14 | FAD310 | DMM → JED | Jun 14, 12:55 UTC | Jun 14, 13:05 UTC | 10m |
| 2026-06-13 | FAD829 | JED → KHI | Jun 13, 23:05 UTC | Jun 14, 00:05 UTC | 1h 0m |
| 2026-06-04 | FAD771 | MED → CAI | Jun 4, 05:00 UTC | Jun 4, 05:15 UTC | 15m |
| 2026-06-02 | FAD467 | DMM → MED | Jun 2, 17:05 UTC | Jun 2, 17:15 UTC | 10m |
| 2026-05-31 | FAD776 | CAI → MED | May 31, 19:50 UTC | May 31, 20:10 UTC | 20m |
| 2026-05-31 | FAD775 | MED → CAI | May 31, 17:50 UTC | May 31, 18:25 UTC | 35m |
| 2026-05-28 | FAD776 | CAI → MED | May 28, 19:45 UTC | May 28, 20:05 UTC | 20m |
| 2026-05-28 | FAD775 | MED → CAI | May 28, 17:45 UTC | May 28, 18:05 UTC | 20m |
| 2026-05-27 | FAD776 | CAI → MED | May 27, 20:00 UTC | May 28, 18:05 UTC | 22h 5m |
| 2026-05-27 | FAD775 | MED → CAI | May 27, 17:30 UTC | May 27, 17:55 UTC | 25m |
| 2026-05-26 | FAD775 | MED → CAI | May 26, 19:55 UTC | May 27, 17:55 UTC | 22h 0m |
| 2026-05-26 | FAD775 | MED → CAI | May 26, 17:59 UTC | May 26, 18:24 UTC | 25m |
| 2026-05-25 | FAD775 | MED → CAI | May 25, 19:54 UTC | May 26, 18:24 UTC | 22h 30m |
| 2026-05-25 | FAD775 | MED → CAI | May 25, 17:50 UTC | May 25, 18:05 UTC | 15m |
| 2026-05-16 | FAD651 | RUH → ISB | May 16, 21:40 UTC | May 17, 06:15 UTC | 8h 35m |
| 2026-05-16 | FAD186 | DMM → RUH | May 16, 18:30 UTC | May 16, 18:45 UTC | 15m |
| 2026-05-14 | FAD505 | RUH → DXB | May 14, 06:35 UTC | May 14, 07:00 UTC | 25m |
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-FBF page for operator, model, and routing details .