sensors Mode-S transponder
717CD3
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-FAW · AIRBUS A-320neo
- Hex
- 717CD3
- Octal
- 34276323
- Decimal
- 7,437,523
- Country
- SA
- Tail
- HZ-FAW
- Type
- A20N
- Flights observed
- 39
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 14d ago
Last known position
Country allocation
The ICAO 24-bit address 717CD3 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 |
|---|---|---|---|
| FAD808 | Rog-Air | 5 | 2026-04-19 |
| FAD807 | - | 5 | 2026-04-19 |
| FAD829 | Rog-Air | 2 | 2026-05-09 |
| FAD702 | - | 2 | 2026-04-25 |
| FAD701 | Rog-Air | 2 | 2026-04-24 |
| FAD6203 | - | 2 | 2026-05-16 |
| FAD6161 | - | 2 | 2026-05-08 |
| FAD304 | Rog-Air | 2 | 2026-04-24 |
| FAD830 | Rog-Air | 1 | 2026-04-16 |
| FAD756 | Rog-Air | 1 | 2026-04-20 |
| FAD6871 | - | 1 | 2026-05-18 |
| FAD6870 | - | 1 | 2026-05-18 |
| FAD6862 | - | 1 | 2026-05-19 |
| FAD6759 | - | 1 | 2026-05-17 |
| FAD6758 | - | 1 | 2026-05-17 |
| FAD6237 | - | 1 | 2026-05-12 |
| FAD6236 | - | 1 | 2026-05-11 |
| FAD6202 | - | 1 | 2026-05-15 |
| FAD608 | Rog-Air | 1 | 2026-05-02 |
| FAD607 | Rog-Air | 1 | 2026-05-02 |
Recent flights last 39
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-19 | FAD6862 | - | May 19, 02:00 UTC | May 19, 04:55 UTC | 2h 55m |
| 2026-05-18 | FAD6871 | - | May 18, 07:50 UTC | May 19, 04:55 UTC | 21h 4m |
| 2026-05-18 | FAD6870 | - | May 18, 05:15 UTC | May 19, 02:05 UTC | 20h 49m |
| 2026-05-17 | FAD6759 | - | May 17, 15:50 UTC | May 18, 07:55 UTC | 16h 5m |
| 2026-05-17 | FAD6758 | - | May 17, 02:00 UTC | May 17, 14:05 UTC | 12h 5m |
| 2026-05-16 | FAD6203 | - | May 16, 15:35 UTC | May 17, 14:05 UTC | 22h 30m |
| 2026-05-16 | FAD6203 | - | May 16, 05:00 UTC | May 16, 13:31 UTC | 8h 31m |
| 2026-05-15 | FAD6202 | - | May 15, 10:55 UTC | May 16, 05:25 UTC | 18h 29m |
| 2026-05-13 | FAD6069 | OSS → MED | May 13, 17:15 UTC | May 13, 17:40 UTC | 25m |
| 2026-05-13 | FAD6068 | - | May 13, 06:35 UTC | May 13, 15:45 UTC | 9h 10m |
| 2026-05-12 | FAD6237 | TBS → TBS | May 12, 17:05 UTC | May 13, 15:45 UTC | 22h 40m |
| 2026-05-11 | FAD6236 | TBS → TBS | May 11, 22:35 UTC | May 12, 15:50 UTC | 17h 16m |
| 2026-05-11 | FAD6062 | - | May 11, 11:55 UTC | May 11, 20:35 UTC | 8h 40m |
| 2026-05-09 | FAD829 | JED → KHI | May 9, 23:09 UTC | May 10, 11:15 UTC | 12h 5m |
| 2026-05-08 | FAD6161 | - | May 8, 11:44 UTC | May 8, 12:10 UTC | 25m |
| 2026-05-08 | FAD6161 | - | May 8, 09:54 UTC | May 8, 10:25 UTC | 30m |
| 2026-05-02 | FAD608 | CAI → RUH | May 2, 13:20 UTC | May 2, 13:30 UTC | 10m |
| 2026-05-02 | FAD607 | RUH → CAI | May 2, 11:05 UTC | May 2, 11:20 UTC | 15m |
| 2026-04-26 | FAD430 | HOF → JED | Apr 26, 09:35 UTC | Apr 26, 09:45 UTC | 10m |
| 2026-04-25 | FAD702 | - | Apr 25, 12:15 UTC | Apr 25, 13:25 UTC | 1h 10m |
| 2026-04-24 | FAD701 | JED → MCT | Apr 24, 19:10 UTC | Apr 25, 09:15 UTC | 14h 5m |
| 2026-04-24 | FAD304 | DMM → JED | Apr 24, 08:05 UTC | Apr 24, 08:15 UTC | 10m |
| 2026-04-22 | FAD322 | DMM → JED | Apr 22, 00:10 UTC | Apr 22, 00:20 UTC | 10m |
| 2026-04-20 | FAD756 | CAI → JED | Apr 20, 08:55 UTC | Apr 20, 09:05 UTC | 10m |
| 2026-04-19 | FAD808 | IST → JED | Apr 19, 20:15 UTC | Apr 20, 07:00 UTC | 10h 45m |
| 2026-04-19 | FAD807 | - | Apr 19, 09:15 UTC | Apr 19, 18:40 UTC | 9h 25m |
| 2026-04-18 | FAD702 | - | Apr 18, 12:55 UTC | Apr 19, 07:10 UTC | 18h 15m |
| 2026-04-18 | FAD701 | JED → MCT | Apr 18, 08:45 UTC | Apr 18, 09:20 UTC | 35m |
| 2026-04-17 | FAD808 | - | Apr 17, 21:25 UTC | Apr 17, 22:00 UTC | 35m |
| 2026-04-17 | FAD808 | - | Apr 17, 20:15 UTC | Apr 18, 09:55 UTC | 13h 41m |
| 2026-04-17 | FAD807 | - | Apr 17, 17:25 UTC | Apr 17, 18:25 UTC | 1h 0m |
| 2026-04-17 | FAD807 | - | Apr 17, 16:55 UTC | Apr 17, 17:15 UTC | 20m |
| 2026-04-16 | FAD830 | KHI → JED | Apr 16, 04:29 UTC | Apr 16, 04:44 UTC | 15m |
| 2026-04-15 | FAD829 | JED → KHI | Apr 15, 23:20 UTC | Apr 16, 00:20 UTC | 1h 0m |
| 2026-04-15 | FAD304 | DMM → JED | Apr 15, 08:10 UTC | Apr 15, 08:25 UTC | 15m |
| 2026-04-14 | FAD808 | - | Apr 14, 20:55 UTC | Apr 14, 21:50 UTC | 55m |
| 2026-04-14 | FAD808 | - | Apr 14, 20:10 UTC | Apr 14, 20:50 UTC | 40m |
| 2026-04-14 | FAD807 | - | Apr 14, 16:50 UTC | Apr 14, 18:15 UTC | 1h 25m |
| 2026-04-14 | FAD807 | - | Apr 14, 16:25 UTC | Apr 14, 16:45 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-FAW page for operator, model, and routing details .