sensors Mode-S transponder
717CD8
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-FAU · AIRBUS A-320neo
- Hex
- 717CD8
- Octal
- 34276330
- Decimal
- 7,437,528
- Country
- SA
- Tail
- HZ-FAU
- Type
- A20N
- Flights observed
- 36
- Distinct callsigns
- 18
- Country
- SA
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address 717CD8 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 18 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| FAD808 | Rog-Air | 5 | 2026-05-29 |
| FAD807 | Rog-Air | 5 | 2026-05-29 |
| FAD654 | Rog-Air | 4 | 2026-05-21 |
| FAD829 | Rog-Air | 3 | 2026-04-29 |
| FAD762 | Rog-Air | 3 | 2026-05-27 |
| FAD761 | Rog-Air | 2 | 2026-05-26 |
| FAD653 | Rog-Air | 2 | 2026-05-22 |
| FAD324 | Rog-Air | 2 | 2026-04-21 |
| FAD754 | Rog-Air | 1 | 2026-04-16 |
| FAD753 | Rog-Air | 1 | 2026-04-16 |
| FAD656 | Rog-Air | 1 | 2026-05-22 |
| FAD655 | Rog-Air | 1 | 2026-04-23 |
| FAD615 | Rog-Air | 1 | 2026-05-23 |
| FAD574 | Rog-Air | 1 | 2026-05-24 |
| FAD573 | Rog-Air | 1 | 2026-05-24 |
| FAD322 | Rog-Air | 1 | 2026-05-01 |
| FAD318 | Rog-Air | 1 | 2026-04-22 |
| FAD304 | Rog-Air | 1 | 2026-04-18 |
Recent flights last 36
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | FAD808 | IST → JED | May 29, 20:25 UTC | May 29, 22:15 UTC | 1h 50m |
| 2026-05-29 | FAD807 | JED → IST | May 29, 16:30 UTC | May 29, 18:45 UTC | 2h 15m |
| 2026-05-27 | FAD762 | CAI → JED | May 27, 18:55 UTC | May 27, 19:10 UTC | 15m |
| 2026-05-26 | FAD761 | JED → CAI | May 26, 22:05 UTC | May 27, 16:55 UTC | 18h 51m |
| 2026-05-26 | FAD808 | IST → JED | May 26, 20:09 UTC | May 27, 16:55 UTC | 20h 46m |
| 2026-05-26 | FAD807 | JED → IST | May 26, 16:30 UTC | May 26, 18:34 UTC | 2h 5m |
| 2026-05-25 | FAD807 | JED → IST | May 25, 22:05 UTC | May 26, 18:34 UTC | 20h 30m |
| 2026-05-25 | FAD808 | IST → JED | May 25, 20:19 UTC | May 26, 18:34 UTC | 22h 15m |
| 2026-05-25 | FAD807 | JED → IST | May 25, 16:20 UTC | May 25, 18:30 UTC | 2h 10m |
| 2026-05-24 | FAD574 | IST → RUH | May 24, 18:05 UTC | May 25, 17:50 UTC | 23h 45m |
| 2026-05-24 | FAD573 | RUH → IST | May 24, 00:00 UTC | May 24, 16:30 UTC | 16h 30m |
| 2026-05-23 | FAD615 | RUH → CAI | May 23, 12:55 UTC | May 23, 22:55 UTC | 10h 0m |
| 2026-05-22 | FAD653 | RUH → SKT | May 22, 21:50 UTC | May 23, 11:10 UTC | 13h 19m |
| 2026-05-22 | FAD653 | RUH → SKT | May 22, 06:05 UTC | May 23, 03:20 UTC | 21h 14m |
| 2026-05-22 | FAD656 | LHE → RUH | May 22, 02:45 UTC | May 23, 00:45 UTC | 22h 0m |
| 2026-05-21 | FAD654 | SKT → RUH | May 21, 06:05 UTC | May 22, 00:40 UTC | 18h 35m |
| 2026-05-21 | FAD654 | SKT → RUH | May 21, 05:55 UTC | May 22, 00:40 UTC | 18h 45m |
| 2026-05-21 | FAD654 | SKT → RUH | May 21, 02:55 UTC | May 22, 00:40 UTC | 21h 45m |
| 2026-05-21 | FAD654 | SKT → RUH | May 21, 00:40 UTC | May 21, 06:20 UTC | 5h 40m |
| 2026-05-01 | FAD322 | DMM → JED | May 1, 00:05 UTC | May 1, 00:20 UTC | 15m |
| 2026-04-29 | FAD829 | JED → KHI | Apr 29, 22:50 UTC | Apr 30, 04:20 UTC | 5h 29m |
| 2026-04-29 | FAD829 | JED → KHI | Apr 29, 00:20 UTC | Apr 29, 23:55 UTC | 23h 35m |
| 2026-04-23 | FAD655 | RUH → LHE | Apr 23, 21:40 UTC | Apr 24, 06:35 UTC | 8h 55m |
| 2026-04-22 | FAD318 | DMM → JED | Apr 22, 19:05 UTC | Apr 22, 19:35 UTC | 30m |
| 2026-04-21 | FAD324 | DMM → JED | Apr 21, 21:20 UTC | Apr 21, 23:35 UTC | 2h 15m |
| 2026-04-20 | FAD324 | DMM → JED | Apr 20, 23:20 UTC | Apr 21, 21:20 UTC | 22h 0m |
| 2026-04-19 | FAD829 | JED → KHI | Apr 19, 00:40 UTC | Apr 19, 01:45 UTC | 1h 5m |
| 2026-04-18 | FAD304 | DMM → JED | Apr 18, 07:55 UTC | Apr 18, 08:05 UTC | 10m |
| 2026-04-16 | FAD754 | CAI → JED | Apr 16, 07:09 UTC | Apr 16, 07:19 UTC | 10m |
| 2026-04-16 | FAD753 | JED → CAI | Apr 16, 05:29 UTC | Apr 16, 05:39 UTC | 10m |
| 2026-04-15 | FAD808 | - | Apr 15, 21:05 UTC | Apr 15, 22:05 UTC | 1h 0m |
| 2026-04-15 | FAD808 | - | Apr 15, 20:20 UTC | Apr 15, 21:00 UTC | 40m |
| 2026-04-15 | FAD807 | - | Apr 15, 17:05 UTC | Apr 15, 18:45 UTC | 1h 40m |
| 2026-04-14 | FAD762 | CAI → JED | Apr 14, 19:05 UTC | Apr 14, 19:15 UTC | 10m |
| 2026-04-13 | FAD762 | CAI → JED | Apr 13, 19:10 UTC | Apr 13, 19:25 UTC | 15m |
| 2026-04-13 | FAD761 | - | Apr 13, 16:45 UTC | Apr 13, 17:05 UTC | 20m |
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-FAU page for operator, model, and routing details .