sensors Mode-S transponder
7110F7
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-FAZ · AIRBUS A-320neo
- Hex
- 7110F7
- Octal
- 34210367
- Decimal
- 7,409,911
- Country
- SA
- Tail
- HZ-FAZ
- Type
- A20N
- Flights observed
- 37
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 5d ago
Last known position
Country allocation
The ICAO 24-bit address 7110F7 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 |
|---|---|---|---|
| FAD911 | Rog-Air | 8 | 2026-05-03 |
| FAD613 | Rog-Air | 5 | 2026-05-21 |
| FAD912 | Rog-Air | 2 | 2026-04-23 |
| FAD755 | Rog-Air | 2 | 2026-05-25 |
| FAD607 | Rog-Air | 2 | 2026-05-22 |
| FAD505 | Rog-Air | 2 | 2026-05-16 |
| FAD463 | Rog-Air | 2 | 2026-05-03 |
| FAD764 | Rog-Air | 1 | 2026-04-17 |
| FAD763 | Rog-Air | 1 | 2026-04-17 |
| FAD761 | - | 1 | 2026-04-15 |
| FAD756 | Rog-Air | 1 | 2026-05-25 |
| FAD753 | Rog-Air | 1 | 2026-04-14 |
| FAD616 | Rog-Air | 1 | 2026-05-19 |
| FAD615 | Rog-Air | 1 | 2026-05-19 |
| FAD614 | Rog-Air | 1 | 2026-05-13 |
| FAD608 | Rog-Air | 1 | 2026-05-22 |
| FAD481 | Rog-Air | 1 | 2026-04-26 |
| FAD465 | Rog-Air | 1 | 2026-05-02 |
| FAD461 | Rog-Air | 1 | 2026-05-02 |
| FAD452 | Rog-Air | 1 | 2026-05-06 |
Recent flights last 37
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-25 | FAD756 | CAI → JED | May 25, 09:00 UTC | May 25, 09:10 UTC | 10m |
| 2026-05-25 | FAD755 | JED → CAI | May 25, 06:40 UTC | May 25, 06:55 UTC | 15m |
| 2026-05-22 | FAD608 | CAI → RUH | May 22, 12:50 UTC | May 22, 13:05 UTC | 15m |
| 2026-05-22 | FAD607 | RUH → CAI | May 22, 11:00 UTC | May 22, 11:20 UTC | 20m |
| 2026-05-21 | FAD613 | RUH → CAI | May 21, 07:40 UTC | May 21, 08:05 UTC | 25m |
| 2026-05-19 | FAD616 | CAI → RUH | May 19, 23:55 UTC | May 20, 00:10 UTC | 15m |
| 2026-05-19 | FAD615 | RUH → CAI | May 19, 10:05 UTC | May 19, 22:30 UTC | 12h 25m |
| 2026-05-19 | FAD613 | RUH → CAI | May 19, 07:50 UTC | May 19, 08:15 UTC | 25m |
| 2026-05-16 | FAD505 | RUH → DXB | May 16, 06:31 UTC | May 16, 10:01 UTC | 3h 30m |
| 2026-05-13 | FAD614 | CAI → RUH | May 13, 09:20 UTC | May 13, 09:30 UTC | 10m |
| 2026-05-13 | FAD613 | RUH → CAI | May 13, 07:25 UTC | May 13, 07:40 UTC | 15m |
| 2026-05-12 | FAD613 | RUH → CAI | May 12, 07:30 UTC | May 12, 07:50 UTC | 20m |
| 2026-05-11 | FAD607 | RUH → CAI | May 11, 10:45 UTC | May 11, 11:10 UTC | 25m |
| 2026-05-10 | FAD505 | RUH → DXB | May 10, 06:20 UTC | May 10, 09:55 UTC | 3h 35m |
| 2026-05-08 | FAD613 | RUH → CAI | May 8, 07:29 UTC | May 8, 07:55 UTC | 25m |
| 2026-05-06 | FAD452 | TIF → DMM | May 6, 15:55 UTC | May 6, 16:15 UTC | 20m |
| 2026-05-03 | FAD463 | DMM → MED | May 3, 12:35 UTC | May 3, 18:20 UTC | 5h 45m |
| 2026-05-03 | FAD911 | DMM → CAI | May 3, 04:25 UTC | May 3, 07:05 UTC | 2h 40m |
| 2026-05-02 | FAD465 | DMM → MED | May 2, 18:05 UTC | May 2, 18:20 UTC | 15m |
| 2026-05-02 | FAD461 | DMM → MED | May 2, 05:10 UTC | May 2, 10:55 UTC | 5h 45m |
| 2026-05-01 | FAD911 | DMM → CAI | May 1, 04:25 UTC | May 1, 06:40 UTC | 2h 15m |
| 2026-04-29 | FAD911 | DMM → CAI | Apr 29, 04:10 UTC | Apr 29, 06:39 UTC | 2h 30m |
| 2026-04-26 | FAD481 | DMM → HAS | Apr 26, 17:50 UTC | Apr 27, 12:20 UTC | 18h 30m |
| 2026-04-26 | FAD911 | DMM → CAI | Apr 26, 04:15 UTC | Apr 26, 06:55 UTC | 2h 40m |
| 2026-04-25 | FAD911 | DMM → CAI | Apr 25, 06:30 UTC | Apr 25, 06:50 UTC | 20m |
| 2026-04-23 | FAD912 | CAI → DMM | Apr 23, 10:45 UTC | Apr 23, 11:01 UTC | 15m |
| 2026-04-23 | FAD911 | DMM → CAI | Apr 23, 04:15 UTC | Apr 23, 07:01 UTC | 2h 46m |
| 2026-04-22 | FAD1438 | AHB → DMM | Apr 22, 21:40 UTC | Apr 22, 21:55 UTC | 15m |
| 2026-04-21 | FAD463 | - | Apr 21, 12:45 UTC | Apr 21, 16:45 UTC | 4h 0m |
| 2026-04-21 | FAD911 | DMM → CAI | Apr 21, 04:25 UTC | Apr 21, 07:00 UTC | 2h 35m |
| 2026-04-20 | FAD912 | CAI → DMM | Apr 20, 08:35 UTC | Apr 20, 08:45 UTC | 10m |
| 2026-04-20 | FAD911 | DMM → CAI | Apr 20, 06:20 UTC | Apr 20, 06:45 UTC | 25m |
| 2026-04-17 | FAD764 | CAI → JED | Apr 17, 22:05 UTC | Apr 17, 22:15 UTC | 10m |
| 2026-04-17 | FAD763 | JED → CAI | Apr 17, 20:15 UTC | Apr 17, 20:30 UTC | 15m |
| 2026-04-15 | FAD761 | - | Apr 15, 17:05 UTC | Apr 15, 17:20 UTC | 15m |
| 2026-04-15 | FAD755 | JED → CAI | Apr 15, 07:01 UTC | Apr 15, 07:15 UTC | 15m |
| 2026-04-14 | FAD753 | JED → CAI | Apr 14, 05:15 UTC | Apr 14, 05:25 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-FAZ page for operator, model, and routing details .