sensors Mode-S transponder
717C8B
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-FBD · AIRBUS A-320neo
- Hex
- 717C8B
- Octal
- 34276213
- Decimal
- 7,437,451
- Country
- SA
- Tail
- HZ-FBD
- Type
- A20N
- Flights observed
- 55
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 13h ago
Last known position
Country allocation
The ICAO 24-bit address 717C8B 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 |
|---|---|---|---|
| FAD573 | Rog-Air | 7 | 2026-05-09 |
| FAD775 | Rog-Air | 3 | 2026-04-27 |
| FAD6710 | - | 3 | 2026-05-17 |
| FAD613 | Rog-Air | 3 | 2026-05-26 |
| FAD574 | Rog-Air | 3 | 2026-05-08 |
| FAD6041 | Rog-Air | 2 | 2026-05-13 |
| FAD830 | Rog-Air | 1 | 2026-04-18 |
| FAD829 | Rog-Air | 1 | 2026-04-17 |
| FAD807 | - | 1 | 2026-04-12 |
| FAD776 | Rog-Air | 1 | 2026-04-27 |
| FAD762 | Rog-Air | 1 | 2026-05-06 |
| FAD761 | Rog-Air | 1 | 2026-05-05 |
| FAD755 | - | 1 | 2026-04-14 |
| FAD6877 | - | 1 | 2026-05-21 |
| FAD6876 | - | 1 | 2026-05-21 |
| FAD6774 | - | 1 | 2026-05-16 |
| FAD6749 | - | 1 | 2026-05-21 |
| FAD6745 | - | 1 | 2026-05-17 |
| FAD6729 | - | 1 | 2026-05-18 |
| FAD6728 | - | 1 | 2026-05-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | FAD608 | CAI → RUH | May 29, 13:00 UTC | May 29, 13:15 UTC | 15m |
| 2026-05-29 | FAD607 | RUH → CAI | May 29, 03:00 UTC | May 29, 11:15 UTC | 8h 15m |
| 2026-05-26 | FAD614 | CAI → RUH | May 26, 09:15 UTC | May 26, 09:29 UTC | 15m |
| 2026-05-26 | FAD613 | RUH → CAI | May 26, 07:34 UTC | May 26, 07:55 UTC | 20m |
| 2026-05-25 | FAD613 | RUH → CAI | May 25, 09:50 UTC | May 26, 07:55 UTC | 22h 5m |
| 2026-05-25 | FAD613 | RUH → CAI | May 25, 07:40 UTC | May 25, 08:00 UTC | 20m |
| 2026-05-21 | FAD6749 | - | May 21, 11:30 UTC | May 21, 11:50 UTC | 20m |
| 2026-05-21 | FAD6877 | - | May 21, 03:55 UTC | May 21, 10:00 UTC | 6h 5m |
| 2026-05-21 | FAD6876 | - | May 21, 01:55 UTC | May 21, 02:20 UTC | 25m |
| 2026-05-18 | FAD6729 | - | May 18, 13:20 UTC | May 19, 06:50 UTC | 17h 29m |
| 2026-05-18 | FAD6728 | - | May 18, 11:15 UTC | May 18, 11:35 UTC | 20m |
| 2026-05-17 | FAD6745 | AMM → AMM | May 17, 13:10 UTC | May 18, 11:35 UTC | 22h 25m |
| 2026-05-17 | FAD6711 | - | May 17, 04:50 UTC | May 17, 11:25 UTC | 6h 35m |
| 2026-05-17 | FAD6710 | - | May 17, 02:55 UTC | May 17, 03:20 UTC | 25m |
| 2026-05-16 | FAD6710 | - | May 16, 06:50 UTC | May 17, 03:20 UTC | 20h 30m |
| 2026-05-16 | FAD6710 | - | May 16, 06:41 UTC | May 17, 03:20 UTC | 20h 40m |
| 2026-05-16 | FAD6774 | - | May 16, 04:55 UTC | May 16, 05:05 UTC | 10m |
| 2026-05-15 | FAD6191 | - | May 15, 19:00 UTC | May 15, 19:30 UTC | 30m |
| 2026-05-14 | FAD6190 | - | May 14, 23:00 UTC | May 15, 16:55 UTC | 17h 54m |
| 2026-05-13 | FAD6041 | OSS → MED | May 13, 22:00 UTC | May 14, 10:25 UTC | 12h 25m |
| 2026-05-13 | FAD6041 | OSS → MED | May 13, 20:20 UTC | May 13, 20:35 UTC | 15m |
| 2026-05-13 | FAD6040 | - | May 13, 02:20 UTC | May 13, 12:00 UTC | 9h 40m |
| 2026-05-13 | FAD6053 | - | May 13, 00:25 UTC | May 13, 00:45 UTC | 20m |
| 2026-05-12 | FAD6052 | - | May 12, 16:05 UTC | May 12, 16:55 UTC | 50m |
| 2026-05-10 | - | - | May 10, 13:05 UTC | May 10, 13:14 UTC | 10m |
| 2026-05-09 | FAD573 | RUH → IST | May 9, 06:25 UTC | May 9, 20:00 UTC | 13h 35m |
| 2026-05-08 | FAD574 | IST → RUH | May 8, 18:50 UTC | May 9, 18:45 UTC | 23h 55m |
| 2026-05-08 | FAD573 | RUH → IST | May 8, 18:25 UTC | May 9, 15:55 UTC | 21h 30m |
| 2026-05-08 | FAD573 | RUH → IST | May 8, 14:20 UTC | May 8, 16:25 UTC | 2h 5m |
| 2026-05-06 | FAD762 | CAI → JED | May 6, 18:55 UTC | May 6, 19:05 UTC | 10m |
| 2026-05-05 | FAD761 | JED → CAI | May 5, 23:40 UTC | May 6, 17:00 UTC | 17h 20m |
| 2026-05-04 | FAD308 | DMM → JED | May 4, 10:55 UTC | May 4, 11:10 UTC | 15m |
| 2026-05-02 | FAD574 | IST → RUH | May 2, 18:35 UTC | May 2, 20:25 UTC | 1h 50m |
| 2026-05-02 | FAD573 | RUH → IST | May 2, 14:30 UTC | May 2, 16:10 UTC | 1h 40m |
| 2026-04-29 | FAD506 | DXB → RUH | Apr 29, 09:20 UTC | Apr 29, 10:30 UTC | 1h 10m |
| 2026-04-28 | FAD505 | RUH → DXB | Apr 28, 17:10 UTC | Apr 29, 07:35 UTC | 14h 25m |
| 2026-04-27 | FAD776 | CAI → MED | Apr 27, 19:55 UTC | Apr 27, 20:05 UTC | 10m |
| 2026-04-27 | FAD775 | MED → CAI | Apr 27, 17:45 UTC | Apr 27, 18:05 UTC | 20m |
| 2026-04-26 | FAD775 | MED → CAI | Apr 26, 20:00 UTC | Apr 27, 18:05 UTC | 22h 5m |
| 2026-04-26 | FAD775 | MED → CAI | Apr 26, 18:00 UTC | Apr 26, 18:15 UTC | 15m |
| 2026-04-23 | FAD573 | RUH → IST | Apr 23, 13:30 UTC | Apr 23, 20:00 UTC | 6h 29m |
| 2026-04-22 | FAD573 | RUH → IST | Apr 22, 18:50 UTC | Apr 23, 18:45 UTC | 23h 55m |
| 2026-04-22 | FAD574 | IST → RUH | Apr 22, 18:10 UTC | Apr 23, 15:05 UTC | 20h 55m |
| 2026-04-21 | FAD573 | RUH → IST | Apr 21, 21:35 UTC | Apr 22, 16:05 UTC | 18h 30m |
| 2026-04-21 | FAD443 | DMM → GIZ | Apr 21, 10:50 UTC | Apr 21, 11:00 UTC | 10m |
| 2026-04-20 | FAD461 | DMM → MED | Apr 20, 05:10 UTC | Apr 20, 10:55 UTC | 5h 45m |
| 2026-04-19 | FAD430 | HOF → JED | Apr 19, 09:50 UTC | Apr 19, 10:00 UTC | 10m |
| 2026-04-19 | FAD429 | JED → HOF | Apr 19, 08:20 UTC | Apr 19, 08:30 UTC | 10m |
| 2026-04-18 | FAD830 | KHI → JED | Apr 18, 04:00 UTC | Apr 18, 04:10 UTC | 10m |
| 2026-04-17 | FAD829 | JED → KHI | Apr 17, 23:25 UTC | Apr 18, 00:25 UTC | 1h 0m |
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-FBD page for operator, model, and routing details .