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
- 95
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 7h 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 |
|---|---|---|---|
| FAD583 | - | 11 | 2026-07-12 |
| FAD573 | Rog-Air | 8 | 2026-07-09 |
| FAD584 | - | 5 | 2026-07-12 |
| FAD613 | - | 4 | 2026-06-26 |
| FAD591 | - | 4 | 2026-07-13 |
| FAD585 | - | 4 | 2026-07-06 |
| FAD775 | Rog-Air | 3 | 2026-04-27 |
| FAD6710 | - | 3 | 2026-05-17 |
| FAD653 | Rog-Air | 3 | 2026-06-05 |
| FAD574 | Rog-Air | 3 | 2026-05-08 |
| FAD753 | - | 2 | 2026-06-23 |
| FAD614 | - | 2 | 2026-06-26 |
| 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 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | FAD592 | - | Jul 13, 20:25 UTC | Jul 13, 23:00 UTC | 2h 35m |
| 2026-07-13 | FAD591 | - | Jul 13, 00:01 UTC | Jul 13, 18:00 UTC | 18h 0m |
| 2026-07-12 | FAD591 | - | Jul 12, 20:50 UTC | Jul 13, 18:00 UTC | 21h 10m |
| 2026-07-12 | FAD591 | - | Jul 12, 16:50 UTC | Jul 13, 16:45 UTC | 23h 55m |
| 2026-07-12 | FAD584 | - | Jul 12, 13:20 UTC | Jul 13, 04:50 UTC | 15h 30m |
| 2026-07-12 | FAD583 | - | Jul 12, 07:05 UTC | Jul 12, 10:55 UTC | 3h 50m |
| 2026-07-11 | FAD583 | - | Jul 11, 10:50 UTC | Jul 12, 10:45 UTC | 23h 55m |
| 2026-07-11 | FAD583 | - | Jul 11, 09:45 UTC | Jul 12, 08:45 UTC | 23h 0m |
| 2026-07-10 | FAD584 | - | Jul 10, 12:50 UTC | Jul 11, 08:20 UTC | 19h 30m |
| 2026-07-10 | FAD584 | PRG → TZX | Jul 10, 12:05 UTC | Jul 11, 08:20 UTC | 20h 15m |
| 2026-07-09 | FAD583 | - | Jul 9, 18:15 UTC | Jul 10, 10:25 UTC | 16h 10m |
| 2026-07-09 | FAD573 | RUH → IST | Jul 9, 14:00 UTC | Jul 9, 16:00 UTC | 2h 0m |
| 2026-07-08 | FAD616 | - | Jul 8, 00:00 UTC | Jul 8, 00:20 UTC | 20m |
| 2026-07-07 | FAD586 | - | Jul 7, 12:05 UTC | Jul 7, 22:00 UTC | 9h 55m |
| 2026-07-06 | FAD585 | - | Jul 6, 20:15 UTC | Jul 7, 10:35 UTC | 14h 20m |
| 2026-07-06 | FAD591 | - | Jul 6, 15:20 UTC | Jul 6, 18:15 UTC | 2h 55m |
| 2026-07-05 | FAD584 | - | Jul 5, 13:00 UTC | Jul 5, 16:35 UTC | 3h 35m |
| 2026-07-05 | FAD583 | - | Jul 5, 06:55 UTC | Jul 5, 11:15 UTC | 4h 20m |
| 2026-07-04 | FAD583 | - | Jul 4, 15:00 UTC | Jul 5, 11:15 UTC | 20h 15m |
| 2026-07-04 | FAD583 | - | Jul 4, 12:50 UTC | Jul 5, 11:15 UTC | 22h 25m |
| 2026-07-04 | FAD583 | - | Jul 4, 12:15 UTC | Jul 5, 10:45 UTC | 22h 30m |
| 2026-07-03 | FAD585 | - | Jul 3, 14:50 UTC | Jul 4, 10:25 UTC | 19h 35m |
| 2026-07-03 | FAD585 | - | Jul 3, 12:50 UTC | Jul 4, 10:25 UTC | 21h 35m |
| 2026-07-03 | FAD584 | - | Jul 3, 11:55 UTC | Jul 4, 10:25 UTC | 22h 30m |
| 2026-07-02 | FAD583 | - | Jul 2, 14:50 UTC | Jul 3, 10:20 UTC | 19h 30m |
| 2026-07-02 | FAD583 | - | Jul 2, 12:50 UTC | Jul 3, 10:20 UTC | 21h 30m |
| 2026-07-02 | FAD583 | - | Jul 2, 12:20 UTC | Jul 3, 10:20 UTC | 22h 0m |
| 2026-07-02 | FAD585 | - | Jul 2, 00:15 UTC | Jul 2, 10:15 UTC | 10h 0m |
| 2026-07-01 | FAD615 | - | Jul 1, 21:50 UTC | Jul 1, 22:20 UTC | 30m |
| 2026-06-30 | FAD562 | DAM → RUH | Jun 30, 10:40 UTC | Jun 30, 10:55 UTC | 15m |
| 2026-06-28 | FAD186 | - | Jun 28, 18:25 UTC | Jun 28, 18:34 UTC | 10m |
| 2026-06-26 | FAD614 | - | Jun 26, 09:20 UTC | Jun 26, 09:35 UTC | 15m |
| 2026-06-26 | FAD613 | - | Jun 26, 07:24 UTC | Jun 26, 07:39 UTC | 15m |
| 2026-06-23 | FAD753 | - | Jun 23, 05:04 UTC | Jun 23, 05:24 UTC | 20m |
| 2026-06-19 | FAD754 | - | Jun 19, 07:04 UTC | Jun 19, 07:14 UTC | 10m |
| 2026-06-19 | FAD753 | - | Jun 19, 04:54 UTC | Jun 19, 05:14 UTC | 20m |
| 2026-06-05 | FAD653 | RUH → SKT | Jun 5, 21:50 UTC | Jun 6, 06:35 UTC | 8h 45m |
| 2026-06-05 | FAD653 | RUH → SKT | Jun 5, 06:50 UTC | Jun 6, 06:35 UTC | 23h 45m |
| 2026-06-05 | FAD653 | RUH → SKT | Jun 5, 06:30 UTC | Jun 6, 03:30 UTC | 21h 0m |
| 2026-05-30 | FAD651 | RUH → ISB | May 30, 21:35 UTC | May 31, 00:25 UTC | 2h 50m |
| 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 |
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 .