sensors Mode-S transponder
717C87
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-ASAD · AIRBUS A-321neo
- Hex
- 717C87
- Octal
- 34276207
- Decimal
- 7,437,447
- Country
- SA
- Tail
- HZ-ASAD
- Type
- A21N
- Flights observed
- 103
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 8h ago
Last known position
Country allocation
The ICAO 24-bit address 717C87 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 |
|---|---|---|---|
| SVA263 | - | 12 | 2026-07-01 |
| SVA712 | - | 10 | 2026-06-24 |
| SVA264 | Saudi Arabian Airlines | 8 | 2026-07-01 |
| SVA713 | - | 6 | 2026-06-15 |
| SVA554 | Saudi Arabian Airlines | 6 | 2026-06-25 |
| SVA275 | - | 6 | 2026-07-06 |
| SVA597 | - | 3 | 2026-07-08 |
| SVA268 | Saudi Arabian Airlines | 3 | 2026-05-28 |
| SVA589 | Saudi Arabian Airlines | 2 | 2026-04-14 |
| SVA550 | Saudi Arabian Airlines | 2 | 2026-06-01 |
| SVA334 | - | 2 | 2026-06-23 |
| SVA278 | Saudi Arabian Airlines | 2 | 2026-06-02 |
| SVA267 | Saudi Arabian Airlines | 2 | 2026-05-28 |
| SVA201 | - | 2 | 2026-07-07 |
| SVA596 | - | 1 | 2026-06-16 |
| SVA588 | Saudi Arabian Airlines | 1 | 2026-04-14 |
| SVA568 | Saudi Arabian Airlines | 1 | 2026-06-06 |
| SVA5631 | - | 1 | 2026-05-31 |
| SVA560 | - | 1 | 2026-06-29 |
| SVA555 | Saudi Arabian Airlines | 1 | 2026-06-25 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | SVA280 | - | Jul 14, 11:10 UTC | Jul 14, 12:25 UTC | 1h 15m |
| 2026-07-14 | SVA279 | - | Jul 14, 08:00 UTC | Jul 14, 09:35 UTC | 1h 35m |
| 2026-07-11 | SVA380 | - | Jul 11, 18:15 UTC | Jul 11, 18:30 UTC | 15m |
| 2026-07-11 | SVA258 | - | Jul 11, 10:45 UTC | Jul 11, 16:40 UTC | 5h 55m |
| 2026-07-11 | SVA259 | - | Jul 11, 03:01 UTC | Jul 11, 08:55 UTC | 5h 55m |
| 2026-07-11 | SVA391 | - | Jul 11, 00:45 UTC | Jul 11, 01:20 UTC | 35m |
| 2026-07-10 | SVA208 | FCO → RUH | Jul 10, 14:35 UTC | Jul 10, 17:30 UTC | 2h 55m |
| 2026-07-10 | SVA207 | - | Jul 10, 08:40 UTC | Jul 10, 12:20 UTC | 3h 40m |
| 2026-07-08 | SVA597 | - | Jul 8, 09:45 UTC | Jul 8, 10:35 UTC | 50m |
| 2026-07-07 | SVA202 | - | Jul 7, 14:40 UTC | Jul 8, 08:25 UTC | 17h 45m |
| 2026-07-07 | SVA201 | - | Jul 7, 10:30 UTC | Jul 7, 12:30 UTC | 2h 0m |
| 2026-07-06 | SVA201 | - | Jul 6, 15:50 UTC | Jul 7, 12:30 UTC | 20h 40m |
| 2026-07-06 | SVA275 | - | Jul 6, 11:45 UTC | Jul 6, 13:50 UTC | 2h 5m |
| 2026-07-03 | SVA206 | - | Jul 3, 07:20 UTC | Jul 3, 10:40 UTC | 3h 20m |
| 2026-07-03 | SVA209 | - | Jul 3, 01:35 UTC | Jul 3, 04:50 UTC | 3h 15m |
| 2026-07-01 | SVA264 | IST → RUH | Jul 1, 13:50 UTC | Jul 1, 15:45 UTC | 1h 55m |
| 2026-07-01 | SVA263 | - | Jul 1, 09:35 UTC | Jul 1, 11:35 UTC | 2h 0m |
| 2026-06-30 | SVA264 | IST → RUH | Jun 30, 13:40 UTC | Jun 30, 15:25 UTC | 1h 45m |
| 2026-06-29 | SVA263 | - | Jun 29, 16:44 UTC | Jun 30, 11:05 UTC | 18h 21m |
| 2026-06-29 | SVA560 | - | Jun 29, 09:40 UTC | Jun 29, 15:00 UTC | 5h 20m |
| 2026-06-28 | SVA264 | IST → RUH | Jun 28, 13:59 UTC | Jun 29, 08:09 UTC | 18h 10m |
| 2026-06-28 | SVA263 | - | Jun 28, 09:45 UTC | Jun 28, 11:25 UTC | 1h 40m |
| 2026-06-26 | SVA597 | - | Jun 26, 09:39 UTC | Jun 26, 10:30 UTC | 50m |
| 2026-06-25 | SVA555 | DXB → RUH | Jun 25, 14:59 UTC | Jun 26, 08:05 UTC | 17h 5m |
| 2026-06-25 | SVA554 | RUH → DXB | Jun 25, 05:55 UTC | Jun 25, 13:40 UTC | 7h 45m |
| 2026-06-24 | SVA712 | - | Jun 24, 14:04 UTC | Jun 25, 02:30 UTC | 12h 25m |
| 2026-06-24 | SVA263 | - | Jun 24, 09:34 UTC | Jun 24, 11:09 UTC | 1h 35m |
| 2026-06-23 | SVA334 | - | Jun 23, 19:50 UTC | Jun 23, 20:24 UTC | 35m |
| 2026-06-23 | SVA333 | RUH → HBE | Jun 23, 06:04 UTC | Jun 23, 18:25 UTC | 12h 20m |
| 2026-06-22 | SVA712 | - | Jun 22, 13:59 UTC | Jun 23, 02:40 UTC | 12h 40m |
| 2026-06-22 | SVA263 | - | Jun 22, 09:34 UTC | Jun 22, 11:04 UTC | 1h 30m |
| 2026-06-21 | SVA263 | - | Jun 21, 14:19 UTC | Jun 22, 11:04 UTC | 20h 45m |
| 2026-06-21 | SVA554 | RUH → DXB | Jun 21, 05:44 UTC | Jun 21, 12:44 UTC | 7h 0m |
| 2026-06-20 | SVA712 | - | Jun 20, 14:44 UTC | Jun 21, 02:45 UTC | 12h 0m |
| 2026-06-20 | SVA554 | RUH → DXB | Jun 20, 05:44 UTC | Jun 20, 12:39 UTC | 6h 55m |
| 2026-06-19 | SVA264 | IST → RUH | Jun 19, 14:04 UTC | Jun 20, 01:34 UTC | 11h 30m |
| 2026-06-19 | SVA263 | - | Jun 19, 09:59 UTC | Jun 19, 11:39 UTC | 1h 40m |
| 2026-06-17 | SVA334 | HBE → RUH | Jun 17, 20:00 UTC | Jun 17, 20:40 UTC | 40m |
| 2026-06-17 | SVA597 | - | Jun 17, 09:35 UTC | Jun 17, 18:40 UTC | 9h 5m |
| 2026-06-16 | SVA596 | - | Jun 16, 11:49 UTC | Jun 17, 07:20 UTC | 19h 31m |
| 2026-06-16 | SVA554 | RUH → DXB | Jun 16, 11:15 UTC | Jun 17, 07:20 UTC | 20h 6m |
| 2026-06-16 | SVA554 | RUH → DXB | Jun 16, 08:05 UTC | Jun 17, 07:20 UTC | 23h 16m |
| 2026-06-16 | SVA554 | RUH → DXB | Jun 16, 05:50 UTC | Jun 16, 15:24 UTC | 9h 35m |
| 2026-06-15 | SVA712 | - | Jun 15, 05:50 UTC | Jun 16, 01:30 UTC | 19h 40m |
| 2026-06-15 | SVA713 | - | Jun 15, 04:45 UTC | Jun 16, 01:30 UTC | 20h 45m |
| 2026-06-14 | SVA264 | IST → RUH | Jun 14, 13:45 UTC | Jun 15, 02:24 UTC | 12h 39m |
| 2026-06-14 | SVA263 | - | Jun 14, 09:50 UTC | Jun 14, 11:20 UTC | 1h 30m |
| 2026-06-13 | - | - | Jun 13, 18:45 UTC | Jun 13, 18:55 UTC | 10m |
| 2026-06-13 | SVA713 | - | Jun 13, 04:55 UTC | Jun 13, 06:05 UTC | 1h 10m |
| 2026-06-12 | SVA264 | IST → RUH | Jun 12, 13:45 UTC | Jun 13, 01:40 UTC | 11h 55m |
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-ASAD page for operator, model, and routing details .