sensors Mode-S transponder
717FFE
ICAO 24-bit transponder address · allocated to Saudi Arabia
- Hex
- 717FFE
- Octal
- 34277776
- Decimal
- 7,438,334
- Country
- SA
- Flights observed
- 45
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 6d ago
Last known position
Country allocation
The ICAO 24-bit address 717FFE 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 |
|---|---|---|---|
| FAD807 | Rog-Air | 2 | 2026-05-03 |
| FAD6207 | - | 2 | 2026-05-18 |
| FAD6185 | Rog-Air | 2 | 2026-05-13 |
| FAD6165 | - | 2 | 2026-05-05 |
| FAD6127 | - | 2 | 2026-05-07 |
| FAD6039 | - | 2 | 2026-05-12 |
| FAD6032 | - | 2 | 2026-05-10 |
| FAD324 | Rog-Air | 2 | 2026-04-30 |
| FAD318 | Rog-Air | 2 | 2026-04-27 |
| FAD808 | Rog-Air | 1 | 2026-05-03 |
| FAD776 | Rog-Air | 1 | 2026-05-19 |
| FAD775 | Rog-Air | 1 | 2026-05-19 |
| FAD774 | Rog-Air | 1 | 2026-05-02 |
| FAD773 | Rog-Air | 1 | 2026-05-02 |
| FAD771 | Rog-Air | 1 | 2026-05-19 |
| FAD6859 | - | 1 | 2026-05-21 |
| FAD6858 | - | 1 | 2026-05-21 |
| FAD6842 | - | 1 | 2026-05-16 |
| FAD6801 | - | 1 | 2026-05-15 |
| FAD6800 | - | 1 | 2026-05-15 |
Recent flights last 45
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-07 | FAD652 | ISB → RUH | Jun 7, 03:05 UTC | Jun 7, 03:15 UTC | 10m |
| 2026-05-24 | FAD608 | CAI → RUH | May 24, 13:10 UTC | May 24, 13:20 UTC | 10m |
| 2026-05-24 | FAD607 | RUH → CAI | May 24, 11:05 UTC | May 24, 11:35 UTC | 30m |
| 2026-05-21 | FAD6859 | - | May 21, 07:55 UTC | May 21, 08:20 UTC | 25m |
| 2026-05-21 | FAD6858 | - | May 21, 05:20 UTC | May 21, 05:45 UTC | 25m |
| 2026-05-19 | FAD776 | CAI → MED | May 19, 20:00 UTC | May 19, 20:20 UTC | 20m |
| 2026-05-19 | FAD775 | MED → CAI | May 19, 17:45 UTC | May 19, 18:10 UTC | 25m |
| 2026-05-19 | FAD771 | MED → CAI | May 19, 05:05 UTC | May 19, 05:25 UTC | 20m |
| 2026-05-18 | FAD6207 | - | May 18, 09:00 UTC | May 19, 05:25 UTC | 20h 24m |
| 2026-05-17 | FAD6207 | - | May 17, 14:30 UTC | May 18, 07:30 UTC | 17h 0m |
| 2026-05-16 | FAD6842 | - | May 16, 01:50 UTC | May 16, 10:25 UTC | 8h 36m |
| 2026-05-15 | FAD6801 | - | May 15, 14:25 UTC | May 16, 10:25 UTC | 20h 0m |
| 2026-05-15 | FAD6800 | - | May 15, 06:05 UTC | May 15, 12:30 UTC | 6h 25m |
| 2026-05-15 | FAD5830 | - | May 15, 04:00 UTC | May 15, 04:25 UTC | 25m |
| 2026-05-13 | FAD6777 | - | May 13, 14:55 UTC | May 13, 15:20 UTC | 25m |
| 2026-05-13 | FAD6185 | KSQ → MED | May 13, 04:45 UTC | May 13, 12:55 UTC | 8h 10m |
| 2026-05-13 | FAD6185 | KSQ → MED | May 13, 03:00 UTC | May 13, 03:15 UTC | 15m |
| 2026-05-12 | FAD6039 | - | May 12, 07:35 UTC | May 12, 19:20 UTC | 11h 45m |
| 2026-05-12 | FAD6039 | - | May 12, 05:30 UTC | May 12, 05:45 UTC | 15m |
| 2026-05-11 | FAD6038 | - | May 11, 08:45 UTC | May 11, 21:30 UTC | 12h 46m |
| 2026-05-10 | FAD6032 | - | May 10, 21:25 UTC | May 11, 07:30 UTC | 10h 5m |
| 2026-05-10 | FAD6032 | TBS → TBS | May 10, 08:25 UTC | May 11, 07:30 UTC | 23h 5m |
| 2026-05-09 | FAD6224 | - | May 9, 14:40 UTC | May 10, 07:04 UTC | 16h 25m |
| 2026-05-09 | FAD6503 | CAI → MED | May 9, 07:10 UTC | May 9, 12:25 UTC | 5h 15m |
| 2026-05-08 | FAD6171 | - | May 8, 19:25 UTC | May 9, 05:15 UTC | 9h 50m |
| 2026-05-08 | FAD6170 | - | May 8, 06:50 UTC | May 8, 17:25 UTC | 10h 35m |
| 2026-05-07 | FAD6127 | TBS → TBS | May 7, 17:55 UTC | May 8, 17:25 UTC | 23h 30m |
| 2026-05-07 | FAD6127 | - | May 7, 16:05 UTC | May 7, 16:25 UTC | 20m |
| 2026-05-06 | FAD6125 | - | May 6, 16:55 UTC | May 7, 08:50 UTC | 15h 55m |
| 2026-05-06 | FAD6124 | - | May 6, 06:15 UTC | May 6, 15:15 UTC | 9h 0m |
| 2026-05-05 | FAD6165 | TBS → TBS | May 5, 18:10 UTC | May 6, 15:15 UTC | 21h 5m |
| 2026-05-05 | FAD6165 | - | May 5, 06:45 UTC | May 5, 16:10 UTC | 9h 25m |
| 2026-05-03 | FAD808 | IST → JED | May 3, 20:20 UTC | May 3, 22:09 UTC | 1h 50m |
| 2026-05-03 | FAD807 | JED → IST | May 3, 11:05 UTC | May 3, 18:45 UTC | 7h 40m |
| 2026-05-02 | FAD807 | JED → IST | May 2, 18:55 UTC | May 3, 17:29 UTC | 22h 34m |
| 2026-05-02 | FAD774 | ALY → JED | May 2, 06:05 UTC | May 2, 17:10 UTC | 11h 5m |
| 2026-05-02 | FAD773 | JED → ALY | May 2, 04:15 UTC | May 2, 05:00 UTC | 45m |
| 2026-04-30 | FAD324 | DMM → JED | Apr 30, 23:20 UTC | Apr 30, 23:30 UTC | 10m |
| 2026-04-30 | FAD323 | JED → DMM | Apr 30, 21:25 UTC | Apr 30, 21:55 UTC | 30m |
| 2026-04-30 | FAD308 | DMM → JED | Apr 30, 11:20 UTC | Apr 30, 11:30 UTC | 10m |
| 2026-04-28 | FAD324 | DMM → JED | Apr 28, 21:35 UTC | Apr 28, 23:35 UTC | 2h 0m |
| 2026-04-27 | FAD318 | DMM → JED | Apr 27, 18:35 UTC | Apr 27, 18:45 UTC | 10m |
| 2026-04-25 | FAD318 | DMM → JED | Apr 25, 19:10 UTC | Apr 25, 19:20 UTC | 10m |
| 2026-04-25 | FAD304 | DMM → JED | Apr 25, 08:10 UTC | Apr 25, 08:20 UTC | 10m |
| 2026-04-25 | FAD322 | DMM → JED | Apr 25, 00:20 UTC | Apr 25, 00:30 UTC | 10m |
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.