sensors Mode-S transponder
717CE0
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-FAO · AIRBUS A-320neo
- Hex
- 717CE0
- Octal
- 34276340
- Decimal
- 7,437,536
- Country
- SA
- Tail
- HZ-FAO
- Type
- A20N
- Flights observed
- 51
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 4d ago
Last known position
Country allocation
The ICAO 24-bit address 717CE0 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 |
|---|---|---|---|
| FAD761 | - | 6 | 2026-07-01 |
| FAD615 | - | 6 | 2026-07-12 |
| FAD762 | - | 5 | 2026-07-01 |
| FAD763 | - | 3 | 2026-07-06 |
| FAD616 | Rog-Air | 3 | 2026-06-16 |
| FAD607 | - | 3 | 2026-07-14 |
| FAD911 | Rog-Air | 2 | 2026-05-15 |
| FAD764 | Rog-Air | 2 | 2026-07-02 |
| FAD755 | Rog-Air | 2 | 2026-05-03 |
| FAD754 | - | 2 | 2026-07-04 |
| FAD562 | Rog-Air | 2 | 2026-06-23 |
| FAD506 | - | 2 | 2026-07-13 |
| FAD505 | - | 2 | 2026-07-13 |
| FAD186 | Rog-Air | 2 | 2026-05-15 |
| FAD912 | Rog-Air | 1 | 2026-05-15 |
| FAD756 | Rog-Air | 1 | 2026-04-26 |
| FAD753 | - | 1 | 2026-07-04 |
| FAD608 | Rog-Air | 1 | 2026-07-14 |
| FAD606 | Rog-Air | 1 | 2026-05-20 |
| FAD605 | Rog-Air | 1 | 2026-05-20 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | FAD608 | CAI → RUH | Jul 14, 13:20 UTC | Jul 14, 13:30 UTC | 10m |
| 2026-07-14 | FAD607 | - | Jul 14, 11:05 UTC | Jul 14, 11:30 UTC | 25m |
| 2026-07-13 | FAD506 | - | Jul 13, 09:30 UTC | Jul 13, 10:20 UTC | 50m |
| 2026-07-13 | FAD505 | - | Jul 13, 00:30 UTC | Jul 13, 07:55 UTC | 7h 25m |
| 2026-07-12 | FAD615 | - | Jul 12, 13:50 UTC | Jul 12, 22:45 UTC | 8h 55m |
| 2026-07-12 | FAD543 | - | Jul 12, 11:50 UTC | Jul 12, 12:20 UTC | 30m |
| 2026-07-06 | FAD763 | - | Jul 6, 19:30 UTC | Jul 6, 19:50 UTC | 20m |
| 2026-07-05 | FAD322 | - | Jul 5, 00:25 UTC | Jul 5, 19:10 UTC | 18h 45m |
| 2026-07-04 | FAD754 | - | Jul 4, 07:15 UTC | Jul 4, 22:50 UTC | 15h 35m |
| 2026-07-04 | FAD753 | - | Jul 4, 05:20 UTC | Jul 4, 05:40 UTC | 20m |
| 2026-07-03 | FAD310 | - | Jul 3, 13:05 UTC | Jul 3, 13:15 UTC | 10m |
| 2026-07-02 | FAD764 | CAI → JED | Jul 2, 22:00 UTC | Jul 2, 22:15 UTC | 15m |
| 2026-07-02 | FAD763 | JED → CAI | Jul 2, 19:35 UTC | Jul 2, 20:05 UTC | 30m |
| 2026-07-01 | FAD762 | - | Jul 1, 19:20 UTC | Jul 1, 19:40 UTC | 20m |
| 2026-07-01 | FAD761 | - | Jul 1, 17:05 UTC | Jul 1, 17:30 UTC | 25m |
| 2026-06-29 | FAD762 | - | Jun 29, 19:24 UTC | Jun 29, 19:39 UTC | 15m |
| 2026-06-29 | FAD761 | - | Jun 29, 11:25 UTC | Jun 29, 16:59 UTC | 5h 35m |
| 2026-06-28 | FAD754 | - | Jun 28, 07:34 UTC | Jun 28, 07:44 UTC | 10m |
| 2026-06-27 | FAD762 | CAI → JED | Jun 27, 18:54 UTC | Jun 28, 05:24 UTC | 10h 30m |
| 2026-06-27 | FAD761 | JED → CAI | Jun 27, 09:34 UTC | Jun 27, 17:09 UTC | 7h 35m |
| 2026-06-23 | FAD562 | DAM → RUH | Jun 23, 10:19 UTC | Jun 23, 10:29 UTC | 10m |
| 2026-06-16 | FAD616 | CAI → RUH | Jun 16, 23:45 UTC | Jun 17, 00:05 UTC | 20m |
| 2026-06-16 | FAD615 | - | Jun 16, 21:55 UTC | Jun 16, 22:30 UTC | 35m |
| 2026-06-12 | FAD616 | CAI → RUH | Jun 12, 23:50 UTC | Jun 13, 00:10 UTC | 20m |
| 2026-06-12 | FAD615 | RUH → CAI | Jun 12, 21:45 UTC | Jun 12, 22:05 UTC | 20m |
| 2026-06-11 | FAD562 | DAM → RUH | Jun 11, 10:10 UTC | Jun 11, 10:25 UTC | 15m |
| 2026-06-06 | FAD616 | CAI → RUH | Jun 6, 23:50 UTC | Jun 7, 00:14 UTC | 25m |
| 2026-06-06 | FAD615 | RUH → CAI | Jun 6, 21:50 UTC | Jun 6, 22:30 UTC | 40m |
| 2026-06-05 | FAD615 | RUH → CAI | Jun 5, 23:50 UTC | Jun 6, 22:00 UTC | 22h 10m |
| 2026-06-05 | FAD615 | RUH → CAI | Jun 5, 21:40 UTC | Jun 5, 22:05 UTC | 25m |
| 2026-05-28 | FAD607 | RUH → CAI | May 28, 10:50 UTC | May 28, 12:50 UTC | 2h 0m |
| 2026-05-20 | FAD606 | CAI → RUH | May 20, 11:40 UTC | May 20, 11:50 UTC | 10m |
| 2026-05-20 | FAD605 | RUH → CAI | May 20, 09:30 UTC | May 20, 09:50 UTC | 20m |
| 2026-05-15 | FAD186 | DMM → RUH | May 15, 18:35 UTC | May 15, 18:45 UTC | 10m |
| 2026-05-15 | FAD912 | CAI → DMM | May 15, 08:25 UTC | May 15, 08:35 UTC | 10m |
| 2026-05-15 | FAD911 | DMM → CAI | May 15, 06:30 UTC | May 15, 06:55 UTC | 25m |
| 2026-05-12 | FAD911 | DMM → CAI | May 12, 04:30 UTC | May 12, 06:40 UTC | 2h 10m |
| 2026-05-07 | FAD762 | CAI → JED | May 7, 18:50 UTC | May 7, 19:10 UTC | 20m |
| 2026-05-07 | FAD761 | JED → CAI | May 7, 16:50 UTC | May 7, 17:15 UTC | 25m |
| 2026-05-03 | FAD755 | JED → CAI | May 3, 00:01 UTC | May 3, 07:20 UTC | 7h 19m |
| 2026-05-01 | FAD762 | CAI → JED | May 1, 18:55 UTC | May 1, 19:10 UTC | 15m |
| 2026-05-01 | FAD761 | JED → CAI | May 1, 16:50 UTC | May 1, 17:05 UTC | 15m |
| 2026-04-29 | FAD607 | RUH → CAI | Apr 29, 11:10 UTC | Apr 29, 11:35 UTC | 25m |
| 2026-04-26 | FAD756 | CAI → JED | Apr 26, 09:00 UTC | Apr 26, 09:10 UTC | 10m |
| 2026-04-25 | FAD755 | JED → CAI | Apr 25, 19:10 UTC | Apr 26, 07:10 UTC | 12h 0m |
| 2026-04-25 | FAD761 | JED → CAI | Apr 25, 16:35 UTC | Apr 25, 17:00 UTC | 25m |
| 2026-04-24 | FAD506 | DXB → RUH | Apr 24, 10:10 UTC | Apr 24, 11:20 UTC | 1h 10m |
| 2026-04-24 | FAD505 | RUH → DXB | Apr 24, 06:35 UTC | Apr 24, 07:45 UTC | 1h 10m |
| 2026-04-14 | FAD764 | CAI → JED | Apr 14, 22:00 UTC | Apr 14, 22:15 UTC | 15m |
| 2026-04-14 | FAD763 | JED → CAI | Apr 14, 20:10 UTC | Apr 14, 20:25 UTC | 15m |
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-FAO page for operator, model, and routing details .