sensors Mode-S transponder
717CA2
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-ASAA · AIRBUS A-321neo
- Hex
- 717CA2
- Octal
- 34276242
- Decimal
- 7,437,474
- Country
- SA
- Tail
- HZ-ASAA
- Type
- A21N
- Flights observed
- 46
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address 717CA2 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 | Saudi Arabian Airlines | 4 | 2026-06-01 |
| SVA317 | Saudi Arabian Airlines | 4 | 2026-06-15 |
| SVA381 | Saudi Arabian Airlines | 3 | 2026-06-16 |
| SVA261 | Saudi Arabian Airlines | 3 | 2026-05-29 |
| SVA260 | Saudi Arabian Airlines | 3 | 2026-05-29 |
| SVA259 | - | 3 | 2026-06-16 |
| SVA713 | Saudi Arabian Airlines | 2 | 2026-05-19 |
| SVA380 | Saudi Arabian Airlines | 2 | 2026-06-17 |
| SVA318 | Saudi Arabian Airlines | 2 | 2026-06-09 |
| SVA275 | Saudi Arabian Airlines | 2 | 2026-06-05 |
| SVA258 | Saudi Arabian Airlines | 2 | 2026-06-17 |
| SVA9820 | - | 1 | 2026-06-04 |
| SVA568 | Saudi Arabian Airlines | 1 | 2026-06-14 |
| SVA5509 | - | 1 | 2026-06-03 |
| SVA527 | Saudi Arabian Airlines | 1 | 2026-05-03 |
| SVA526 | Saudi Arabian Airlines | 1 | 2026-05-03 |
| SVA411 | Saudi Arabian Airlines | 1 | 2026-06-08 |
| SVA410 | Saudi Arabian Airlines | 1 | 2026-06-08 |
| SVA330 | Saudi Arabian Airlines | 1 | 2026-05-27 |
| SVA319 | Saudi Arabian Airlines | 1 | 2026-06-12 |
Recent flights last 46
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-17 | SVA380 | CAI → MED | Jun 17, 18:35 UTC | Jun 17, 18:56 UTC | 20m |
| 2026-06-17 | SVA258 | IST → MED | Jun 17, 10:50 UTC | Jun 17, 16:45 UTC | 5h 55m |
| 2026-06-16 | SVA259 | - | Jun 16, 18:09 UTC | Jun 17, 09:10 UTC | 15h 1m |
| 2026-06-16 | SVA381 | MED → CAI | Jun 16, 08:35 UTC | Jun 16, 16:10 UTC | 7h 35m |
| 2026-06-15 | SVA317 | MED → CAI | Jun 15, 18:20 UTC | Jun 16, 06:30 UTC | 12h 10m |
| 2026-06-15 | SVA381 | MED → CAI | Jun 15, 06:49 UTC | Jun 15, 16:30 UTC | 9h 40m |
| 2026-06-14 | SVA568 | JED → DXB | Jun 14, 08:45 UTC | Jun 15, 04:30 UTC | 19h 44m |
| 2026-06-12 | SVA319 | MED → CAI | Jun 12, 08:20 UTC | Jun 12, 12:35 UTC | 4h 15m |
| 2026-06-12 | SVA317 | MED → CAI | Jun 12, 06:10 UTC | Jun 12, 06:20 UTC | 10m |
| 2026-06-11 | SVA317 | MED → CAI | Jun 11, 08:35 UTC | Jun 12, 06:20 UTC | 21h 46m |
| 2026-06-10 | SVA380 | CAI → MED | Jun 10, 18:55 UTC | Jun 11, 06:35 UTC | 11h 40m |
| 2026-06-10 | SVA381 | MED → CAI | Jun 10, 08:40 UTC | Jun 10, 16:55 UTC | 8h 15m |
| 2026-06-10 | SVA317 | MED → CAI | Jun 10, 06:20 UTC | Jun 10, 06:40 UTC | 20m |
| 2026-06-09 | SVA318 | CAI → MED | Jun 9, 06:55 UTC | Jun 10, 06:30 UTC | 23h 35m |
| 2026-06-08 | SVA410 | HBE → JED | Jun 8, 18:05 UTC | Jun 9, 04:35 UTC | 10h 30m |
| 2026-06-08 | SVA411 | JED → HBE | Jun 8, 16:25 UTC | Jun 8, 16:50 UTC | 25m |
| 2026-06-05 | SVA278 | IST → JED | Jun 5, 15:55 UTC | Jun 5, 17:45 UTC | 1h 50m |
| 2026-06-05 | SVA275 | JED → IST | Jun 5, 12:00 UTC | Jun 5, 14:05 UTC | 2h 5m |
| 2026-06-04 | SVA275 | JED → IST | Jun 4, 17:40 UTC | Jun 5, 14:05 UTC | 20h 25m |
| 2026-06-04 | SVA9820 | - | Jun 4, 01:25 UTC | Jun 4, 17:45 UTC | 16h 20m |
| 2026-06-03 | SVA5509 | - | Jun 3, 22:15 UTC | Jun 3, 23:15 UTC | 1h 0m |
| 2026-06-01 | SVA268 | IST → JED | Jun 1, 16:40 UTC | Jun 2, 10:30 UTC | 17h 50m |
| 2026-06-01 | SVA267 | RUH → IST | Jun 1, 06:00 UTC | Jun 1, 14:30 UTC | 8h 30m |
| 2026-06-01 | SVA712 | MED → KHI | Jun 1, 01:20 UTC | Jun 1, 01:30 UTC | 10m |
| 2026-05-29 | SVA260 | IST → JED | May 29, 20:00 UTC | May 30, 11:30 UTC | 15h 30m |
| 2026-05-29 | SVA261 | JED → IST | May 29, 09:25 UTC | May 29, 18:05 UTC | 8h 40m |
| 2026-05-29 | SVA265 | JED → IST | May 29, 05:30 UTC | May 29, 07:35 UTC | 2h 5m |
| 2026-05-27 | SVA330 | CAI → JED | May 27, 14:45 UTC | May 27, 14:55 UTC | 10m |
| 2026-05-27 | SVA318 | CAI → MED | May 27, 06:44 UTC | May 27, 12:30 UTC | 5h 45m |
| 2026-05-25 | SVA260 | IST → JED | May 25, 20:04 UTC | May 25, 21:49 UTC | 1h 45m |
| 2026-05-25 | SVA261 | JED → IST | May 25, 16:15 UTC | May 25, 18:25 UTC | 2h 10m |
| 2026-05-22 | SVA258 | IST → MED | May 22, 10:55 UTC | May 22, 12:45 UTC | 1h 50m |
| 2026-05-22 | SVA259 | MED → IST | May 22, 08:45 UTC | May 22, 08:55 UTC | 10m |
| 2026-05-22 | SVA259 | MED → IST | May 22, 03:10 UTC | May 22, 08:15 UTC | 5h 5m |
| 2026-05-19 | SVA713 | CCJ → RUH | May 19, 07:55 UTC | May 19, 08:25 UTC | 30m |
| 2026-05-19 | SVA712 | MED → KHI | May 19, 05:00 UTC | May 19, 05:10 UTC | 10m |
| 2026-05-19 | SVA712 | MED → KHI | May 19, 01:30 UTC | May 19, 03:00 UTC | 1h 30m |
| 2026-05-07 | SVA1113 | DMM → JED | May 7, 11:25 UTC | May 7, 11:40 UTC | 15m |
| 2026-05-05 | SVA264 | IST → RUH | May 5, 10:05 UTC | May 5, 15:15 UTC | 5h 10m |
| 2026-05-04 | SVA1109 | DMM → JED | May 4, 09:40 UTC | May 4, 09:50 UTC | 10m |
| 2026-05-03 | SVA527 | BAH → JED | May 3, 17:24 UTC | May 3, 17:45 UTC | 20m |
| 2026-05-03 | SVA526 | JED → BAH | May 3, 15:50 UTC | May 3, 16:15 UTC | 25m |
| 2026-05-01 | SVA713 | CCJ → RUH | May 1, 04:45 UTC | May 1, 08:45 UTC | 4h 0m |
| 2026-04-30 | SVA712 | MED → KHI | Apr 30, 22:55 UTC | May 1, 01:25 UTC | 2h 30m |
| 2026-04-29 | SVA260 | IST → JED | Apr 29, 20:15 UTC | Apr 29, 22:00 UTC | 1h 45m |
| 2026-04-29 | SVA261 | JED → IST | Apr 29, 16:20 UTC | Apr 29, 17:45 UTC | 1h 25m |
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-ASAA page for operator, model, and routing details .