sensors Mode-S transponder
71145F
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-FBQ · AIRBUS A-320neo
- Hex
- 71145F
- Octal
- 34212137
- Decimal
- 7,410,783
- Country
- SA
- Tail
- HZ-FBQ
- Type
- A20N
- Flights observed
- 54
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 71145F 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 |
|---|---|---|---|
| FAD505 | Rog-Air | 5 | 2026-04-21 |
| FAD428 | Rog-Air | 4 | 2026-05-02 |
| FAD808 | Rog-Air | 3 | 2026-06-02 |
| FAD807 | Rog-Air | 3 | 2026-06-02 |
| FAD776 | Rog-Air | 3 | 2026-05-06 |
| FAD775 | Rog-Air | 3 | 2026-05-06 |
| FAD506 | Rog-Air | 3 | 2026-04-21 |
| FAD756 | Rog-Air | 2 | 2026-05-30 |
| FAD755 | Rog-Air | 2 | 2026-05-29 |
| FAD656 | Rog-Air | 2 | 2026-04-17 |
| FAD6176 | - | 2 | 2026-05-09 |
| FAD6072 | - | 2 | 2026-05-14 |
| FAD6067 | - | 2 | 2026-05-13 |
| FAD467 | Rog-Air | 2 | 2026-05-05 |
| FAD753 | Rog-Air | 1 | 2026-05-26 |
| FAD6717 | - | 1 | 2026-05-11 |
| FAD655 | Rog-Air | 1 | 2026-04-16 |
| FAD6216 | - | 1 | 2026-05-07 |
| FAD6181 | - | 1 | 2026-05-10 |
| FAD6180 | - | 1 | 2026-05-10 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | FAD808 | IST → JED | Jun 2, 20:25 UTC | Jun 2, 22:15 UTC | 1h 50m |
| 2026-06-02 | FAD807 | JED → IST | Jun 2, 16:20 UTC | Jun 2, 18:30 UTC | 2h 10m |
| 2026-05-30 | FAD756 | CAI → JED | May 30, 09:00 UTC | May 30, 18:50 UTC | 9h 50m |
| 2026-05-29 | FAD755 | JED → CAI | May 29, 13:00 UTC | May 30, 07:15 UTC | 18h 15m |
| 2026-05-27 | FAD808 | IST → JED | May 27, 20:00 UTC | May 27, 22:00 UTC | 2h 0m |
| 2026-05-27 | FAD807 | JED → IST | May 27, 06:49 UTC | May 27, 18:25 UTC | 11h 35m |
| 2026-05-26 | FAD753 | JED → CAI | May 26, 18:50 UTC | May 27, 05:19 UTC | 10h 30m |
| 2026-05-26 | FAD756 | CAI → JED | May 26, 08:54 UTC | May 26, 16:59 UTC | 8h 5m |
| 2026-05-26 | FAD755 | JED → CAI | May 26, 06:44 UTC | May 26, 06:59 UTC | 15m |
| 2026-05-17 | FAD808 | IST → JED | May 17, 20:15 UTC | May 17, 22:01 UTC | 1h 45m |
| 2026-05-17 | FAD807 | JED → IST | May 17, 16:20 UTC | May 17, 18:35 UTC | 2h 15m |
| 2026-05-17 | FAD308 | DMM → JED | May 17, 11:01 UTC | May 17, 11:10 UTC | 10m |
| 2026-05-16 | FAD324 | DMM → JED | May 16, 23:25 UTC | May 16, 23:40 UTC | 15m |
| 2026-05-15 | FAD6073 | - | May 15, 17:40 UTC | May 16, 04:20 UTC | 10h 40m |
| 2026-05-14 | FAD6072 | - | May 14, 21:50 UTC | May 15, 16:00 UTC | 18h 9m |
| 2026-05-14 | FAD6072 | TBS → TBS | May 14, 21:35 UTC | May 15, 16:00 UTC | 18h 24m |
| 2026-05-14 | FAD6055 | - | May 14, 20:00 UTC | May 14, 20:20 UTC | 20m |
| 2026-05-14 | FAD6054 | - | May 14, 02:05 UTC | May 14, 11:45 UTC | 9h 40m |
| 2026-05-13 | FAD6044 | - | May 13, 15:45 UTC | May 14, 00:40 UTC | 8h 55m |
| 2026-05-13 | FAD6067 | TBS → TBS | May 13, 02:30 UTC | May 14, 00:40 UTC | 22h 10m |
| 2026-05-13 | FAD6067 | - | May 13, 01:20 UTC | May 13, 01:35 UTC | 15m |
| 2026-05-12 | FAD6066 | - | May 12, 16:45 UTC | May 12, 17:35 UTC | 50m |
| 2026-05-11 | FAD5826 | - | May 11, 14:00 UTC | May 11, 14:25 UTC | 25m |
| 2026-05-11 | FAD6717 | - | May 11, 05:05 UTC | May 11, 11:35 UTC | 6h 30m |
| 2026-05-10 | FAD6181 | - | May 10, 16:59 UTC | May 11, 02:50 UTC | 9h 50m |
| 2026-05-10 | FAD6180 | - | May 10, 06:45 UTC | May 10, 15:24 UTC | 8h 40m |
| 2026-05-09 | FAD6177 | TBS → TBS | May 9, 18:35 UTC | May 10, 15:24 UTC | 20h 50m |
| 2026-05-09 | FAD6176 | - | May 9, 06:05 UTC | May 9, 16:05 UTC | 10h 0m |
| 2026-05-08 | FAD6176 | - | May 8, 14:20 UTC | May 9, 06:50 UTC | 16h 30m |
| 2026-05-07 | FAD6216 | - | May 7, 18:25 UTC | May 8, 13:00 UTC | 18h 35m |
| 2026-05-06 | FAD776 | CAI → MED | May 6, 19:55 UTC | May 6, 20:10 UTC | 15m |
| 2026-05-06 | FAD775 | MED → CAI | May 6, 18:05 UTC | May 6, 18:20 UTC | 15m |
| 2026-05-05 | FAD467 | DMM → MED | May 5, 16:55 UTC | May 5, 17:10 UTC | 15m |
| 2026-05-03 | FAD776 | CAI → MED | May 3, 20:00 UTC | May 3, 20:10 UTC | 10m |
| 2026-05-03 | FAD775 | MED → CAI | May 3, 18:09 UTC | May 3, 18:25 UTC | 15m |
| 2026-05-02 | FAD428 | HOF → MED | May 2, 18:25 UTC | May 2, 18:35 UTC | 10m |
| 2026-04-30 | FAD428 | HOF → MED | Apr 30, 18:20 UTC | Apr 30, 18:30 UTC | 10m |
| 2026-04-30 | FAD427 | MED → HOF | Apr 30, 17:05 UTC | Apr 30, 17:25 UTC | 20m |
| 2026-04-28 | FAD776 | CAI → MED | Apr 28, 19:50 UTC | Apr 28, 20:00 UTC | 10m |
| 2026-04-28 | FAD775 | MED → CAI | Apr 28, 17:50 UTC | Apr 28, 18:15 UTC | 25m |
| 2026-04-25 | FAD428 | HOF → MED | Apr 25, 18:30 UTC | Apr 25, 18:45 UTC | 15m |
| 2026-04-24 | FAD467 | DMM → MED | Apr 24, 16:55 UTC | Apr 24, 17:05 UTC | 10m |
| 2026-04-23 | FAD428 | - | Apr 23, 18:35 UTC | Apr 24, 17:05 UTC | 22h 30m |
| 2026-04-21 | FAD506 | DXB → RUH | Apr 21, 09:20 UTC | Apr 21, 10:35 UTC | 1h 15m |
| 2026-04-21 | FAD505 | RUH → DXB | Apr 21, 06:35 UTC | Apr 21, 07:40 UTC | 1h 5m |
| 2026-04-20 | FAD505 | RUH → DXB | Apr 20, 09:50 UTC | Apr 21, 07:40 UTC | 21h 51m |
| 2026-04-20 | FAD506 | DXB → RUH | Apr 20, 09:20 UTC | Apr 21, 07:40 UTC | 22h 20m |
| 2026-04-20 | FAD505 | RUH → DXB | Apr 20, 06:25 UTC | Apr 20, 07:35 UTC | 1h 10m |
| 2026-04-18 | FAD506 | DXB → RUH | Apr 18, 10:05 UTC | Apr 18, 11:10 UTC | 1h 5m |
| 2026-04-18 | FAD505 | RUH → DXB | Apr 18, 07:25 UTC | Apr 18, 08:15 UTC | 50m |
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-FBQ page for operator, model, and routing details .