sensors Mode-S transponder
717C83
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-ASAG · AIRBUS A-321neo
- Hex
- 717C83
- Octal
- 34276203
- Decimal
- 7,437,443
- Country
- SA
- Tail
- HZ-ASAG
- Type
- A21N
- Flights observed
- 115
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 1h ago
Current position
Country allocation
The ICAO 24-bit address 717C83 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 |
|---|---|---|---|
| SVA712 | - | 8 | 2026-07-04 |
| SVA588 | - | 6 | 2026-06-29 |
| SVA335 | - | 6 | 2026-07-10 |
| SVA263 | - | 6 | 2026-07-07 |
| SVA319 | - | 5 | 2026-07-13 |
| SVA318 | - | 4 | 2026-06-30 |
| SVA317 | Saudi Arabian Airlines | 4 | 2026-06-13 |
| SVA314 | Saudi Arabian Airlines | 4 | 2026-06-01 |
| SVA264 | Saudi Arabian Airlines | 4 | 2026-07-07 |
| SVA261 | - | 4 | 2026-07-11 |
| SVA209 | - | 4 | 2026-06-19 |
| SVA713 | - | 3 | 2026-06-27 |
| SVA589 | Saudi Arabian Airlines | 3 | 2026-06-29 |
| SVA316 | Saudi Arabian Airlines | 3 | 2026-06-14 |
| SVA260 | Saudi Arabian Airlines | 3 | 2026-05-09 |
| SVA151 | Saudi Arabian Airlines | 3 | 2026-04-20 |
| SVA1165 | Saudi Arabian Airlines | 3 | 2026-05-25 |
| SVA596 | - | 2 | 2026-07-14 |
| SVA554 | Saudi Arabian Airlines | 2 | 2026-06-26 |
| SVA330 | Saudi Arabian Airlines | 2 | 2026-06-30 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | SVA597 | - | Jul 14, 09:30 UTC | Jul 14, 18:25 UTC | 8h 55m |
| 2026-07-14 | SVA596 | - | Jul 14, 07:40 UTC | Jul 14, 08:10 UTC | 30m |
| 2026-07-13 | SVA596 | - | Jul 13, 15:05 UTC | Jul 14, 07:35 UTC | 16h 30m |
| 2026-07-13 | SVA319 | - | Jul 13, 06:55 UTC | Jul 13, 12:30 UTC | 5h 35m |
| 2026-07-12 | SVA202 | - | Jul 12, 14:30 UTC | Jul 13, 04:45 UTC | 14h 15m |
| 2026-07-11 | SVA201 | - | Jul 11, 19:35 UTC | Jul 12, 11:55 UTC | 16h 20m |
| 2026-07-11 | SVA261 | - | Jul 11, 16:05 UTC | Jul 11, 18:00 UTC | 1h 55m |
| 2026-07-10 | SVA319 | - | Jul 10, 06:45 UTC | Jul 10, 12:30 UTC | 5h 45m |
| 2026-07-10 | SVA335 | - | Jul 10, 04:20 UTC | Jul 10, 04:50 UTC | 30m |
| 2026-07-07 | SVA264 | IST → RUH | Jul 7, 13:45 UTC | Jul 7, 15:35 UTC | 1h 50m |
| 2026-07-07 | SVA263 | - | Jul 7, 09:05 UTC | Jul 7, 11:10 UTC | 2h 5m |
| 2026-07-07 | - | - | Jul 7, 04:10 UTC | Jul 7, 04:20 UTC | 10m |
| 2026-07-06 | SVA264 | IST → RUH | Jul 6, 13:50 UTC | Jul 6, 15:45 UTC | 1h 55m |
| 2026-07-05 | SVA263 | - | Jul 5, 16:50 UTC | Jul 6, 11:15 UTC | 18h 25m |
| 2026-07-05 | SVA263 | - | Jul 5, 16:40 UTC | Jul 6, 11:15 UTC | 18h 35m |
| 2026-07-05 | SVA267 | RUH → IST | Jul 5, 05:50 UTC | Jul 5, 14:40 UTC | 8h 50m |
| 2026-07-04 | SVA712 | - | Jul 4, 22:45 UTC | Jul 5, 01:40 UTC | 2h 55m |
| 2026-07-04 | SVA1167 | - | Jul 4, 02:20 UTC | Jul 4, 02:30 UTC | 10m |
| 2026-07-03 | SVA268 | IST → JED | Jul 3, 16:45 UTC | Jul 3, 18:40 UTC | 1h 55m |
| 2026-07-03 | SVA267 | RUH → IST | Jul 3, 05:50 UTC | Jul 3, 14:45 UTC | 8h 55m |
| 2026-07-02 | SVA712 | - | Jul 2, 23:15 UTC | Jul 3, 01:50 UTC | 2h 35m |
| 2026-07-02 | SVA593 | - | Jul 2, 01:25 UTC | Jul 3, 00:05 UTC | 22h 40m |
| 2026-07-01 | SVA592 | - | Jul 1, 21:20 UTC | Jul 1, 22:30 UTC | 1h 10m |
| 2026-06-30 | SVA1131 | - | Jun 30, 22:35 UTC | Jun 30, 22:45 UTC | 10m |
| 2026-06-30 | SVA330 | CAI → JED | Jun 30, 14:55 UTC | Jun 30, 15:05 UTC | 10m |
| 2026-06-30 | SVA318 | - | Jun 30, 06:45 UTC | Jun 30, 12:30 UTC | 5h 45m |
| 2026-06-29 | SVA589 | DXB → JED | Jun 29, 13:44 UTC | Jun 29, 14:34 UTC | 50m |
| 2026-06-29 | SVA588 | - | Jun 29, 10:34 UTC | Jun 29, 11:50 UTC | 1h 15m |
| 2026-06-27 | SVA713 | - | Jun 27, 05:44 UTC | Jun 27, 08:20 UTC | 2h 35m |
| 2026-06-26 | SVA712 | - | Jun 26, 14:29 UTC | Jun 27, 01:39 UTC | 11h 10m |
| 2026-06-26 | SVA554 | RUH → DXB | Jun 26, 11:45 UTC | Jun 26, 12:50 UTC | 1h 5m |
| 2026-06-25 | SVA1105 | - | Jun 25, 03:20 UTC | Jun 25, 03:29 UTC | 10m |
| 2026-06-24 | SVA589 | DXB → JED | Jun 24, 13:44 UTC | Jun 25, 01:59 UTC | 12h 15m |
| 2026-06-24 | SVA588 | - | Jun 24, 10:49 UTC | Jun 24, 11:54 UTC | 1h 5m |
| 2026-06-22 | SVA589 | DXB → JED | Jun 22, 13:39 UTC | Jun 22, 14:34 UTC | 55m |
| 2026-06-22 | SVA588 | - | Jun 22, 10:40 UTC | Jun 22, 11:50 UTC | 1h 10m |
| 2026-06-20 | SVA1163 | DMM → RUH | Jun 20, 16:14 UTC | Jun 20, 16:24 UTC | 10m |
| 2026-06-19 | SVA334 | - | Jun 19, 19:59 UTC | Jun 19, 20:40 UTC | 40m |
| 2026-06-19 | SVA206 | - | Jun 19, 07:25 UTC | Jun 19, 18:25 UTC | 11h 0m |
| 2026-06-19 | SVA209 | - | Jun 19, 01:39 UTC | Jun 19, 05:00 UTC | 3h 20m |
| 2026-06-18 | SVA209 | - | Jun 18, 08:50 UTC | Jun 19, 05:00 UTC | 20h 9m |
| 2026-06-18 | SVA209 | - | Jun 18, 07:45 UTC | Jun 19, 04:44 UTC | 20h 59m |
| 2026-06-17 | SVA209 | - | Jun 17, 14:20 UTC | Jun 18, 04:45 UTC | 14h 25m |
| 2026-06-17 | SVA554 | RUH → DXB | Jun 17, 05:45 UTC | Jun 17, 12:00 UTC | 6h 15m |
| 2026-06-16 | SVA712 | - | Jun 16, 22:45 UTC | Jun 17, 01:35 UTC | 2h 50m |
| 2026-06-15 | SVA588 | - | Jun 15, 10:45 UTC | Jun 15, 11:15 UTC | 30m |
| 2026-06-14 | SVA588 | - | Jun 14, 15:00 UTC | Jun 15, 11:15 UTC | 20h 15m |
| 2026-06-14 | SVA316 | CAI → MED | Jun 14, 08:40 UTC | Jun 14, 12:40 UTC | 4h 0m |
| 2026-06-13 | SVA317 | MED → CAI | Jun 13, 18:30 UTC | Jun 14, 06:35 UTC | 12h 5m |
| 2026-06-13 | SVA381 | MED → CAI | Jun 13, 16:10 UTC | Jun 13, 16:30 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-ASAG page for operator, model, and routing details .