sensors Mode-S transponder
717CA4
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-ASAB · AIRBUS A-321neo
- Hex
- 717CA4
- Octal
- 34276244
- Decimal
- 7,437,476
- Country
- SA
- Tail
- HZ-ASAB
- Type
- A21N
- Flights observed
- 109
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 48m ago
Current position
Country allocation
The ICAO 24-bit address 717CA4 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 |
|---|---|---|---|
| SVA259 | Saudi Arabian Airlines | 10 | 2026-05-30 |
| SVA258 | Saudi Arabian Airlines | 9 | 2026-05-31 |
| SVA315 | Saudi Arabian Airlines | 7 | 2026-07-05 |
| SVA380 | Saudi Arabian Airlines | 6 | 2026-05-31 |
| SVA3712 | Saudi Arabian Airlines | 6 | 2026-04-28 |
| SVA264 | Saudi Arabian Airlines | 6 | 2026-07-08 |
| SVA252 | - | 6 | 2026-07-05 |
| SVA251 | Saudi Arabian Airlines | 6 | 2026-07-05 |
| SVA263 | - | 5 | 2026-07-07 |
| SVA712 | - | 4 | 2026-07-11 |
| SVA713 | Saudi Arabian Airlines | 3 | 2026-05-14 |
| SVA319 | Saudi Arabian Airlines | 3 | 2026-06-10 |
| SVA268 | - | 3 | 2026-07-12 |
| SVA265 | - | 3 | 2026-06-30 |
| SVA260 | - | 3 | 2026-06-30 |
| SVA568 | Saudi Arabian Airlines | 2 | 2026-06-09 |
| SVA335 | Saudi Arabian Airlines | 2 | 2026-06-03 |
| SVA317 | Saudi Arabian Airlines | 2 | 2026-06-04 |
| SVA278 | - | 2 | 2026-04-16 |
| SVA275 | Saudi Arabian Airlines | 2 | 2026-04-16 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | SVA207 | - | Jul 14, 08:55 UTC | Jul 14, 11:00 UTC | 2h 5m |
| 2026-07-12 | SVA268 | - | Jul 12, 16:45 UTC | Jul 12, 18:45 UTC | 2h 0m |
| 2026-07-12 | SVA267 | RUH → IST | Jul 12, 05:40 UTC | Jul 12, 14:20 UTC | 8h 40m |
| 2026-07-11 | SVA712 | - | Jul 11, 22:50 UTC | Jul 12, 01:40 UTC | 2h 50m |
| 2026-07-08 | SVA264 | IST → RUH | Jul 8, 13:50 UTC | Jul 8, 15:40 UTC | 1h 50m |
| 2026-07-07 | SVA263 | - | Jul 7, 19:55 UTC | Jul 8, 11:25 UTC | 15h 30m |
| 2026-07-07 | SVA333 | RUH → HBE | Jul 7, 12:15 UTC | Jul 7, 18:25 UTC | 6h 10m |
| 2026-07-07 | SVA540 | RUH → DOH | Jul 7, 10:15 UTC | Jul 7, 10:55 UTC | 40m |
| 2026-07-06 | SVA520 | - | Jul 6, 13:30 UTC | Jul 6, 13:45 UTC | 15m |
| 2026-07-06 | SVA597 | - | Jul 6, 09:35 UTC | Jul 6, 10:25 UTC | 50m |
| 2026-07-05 | SVA252 | - | Jul 5, 22:50 UTC | Jul 6, 08:05 UTC | 9h 15m |
| 2026-07-05 | SVA251 | JED → BHX | Jul 5, 14:05 UTC | Jul 5, 21:25 UTC | 7h 20m |
| 2026-07-05 | SVA315 | RUH → CAI | Jul 5, 08:30 UTC | Jul 5, 12:20 UTC | 3h 50m |
| 2026-07-04 | SVA252 | - | Jul 4, 21:40 UTC | Jul 5, 06:20 UTC | 8h 40m |
| 2026-07-04 | SVA251 | JED → BHX | Jul 4, 14:15 UTC | Jul 4, 20:10 UTC | 5h 55m |
| 2026-07-04 | SVA315 | RUH → CAI | Jul 4, 08:20 UTC | Jul 4, 12:20 UTC | 4h 0m |
| 2026-07-03 | SVA252 | - | Jul 3, 22:10 UTC | Jul 4, 06:05 UTC | 7h 55m |
| 2026-07-03 | SVA251 | JED → BHX | Jul 3, 14:40 UTC | Jul 3, 20:40 UTC | 6h 0m |
| 2026-07-03 | SVA315 | RUH → CAI | Jul 3, 12:00 UTC | Jul 3, 12:15 UTC | 15m |
| 2026-07-02 | SVA252 | IST → MED | Jul 2, 21:20 UTC | Jul 3, 06:10 UTC | 8h 50m |
| 2026-07-02 | SVA251 | JED → BHX | Jul 2, 17:55 UTC | Jul 2, 19:55 UTC | 2h 0m |
| 2026-07-02 | SVA315 | RUH → CAI | Jul 2, 11:55 UTC | Jul 2, 12:15 UTC | 20m |
| 2026-07-01 | SVA252 | IST → MED | Jul 1, 21:25 UTC | Jul 2, 06:15 UTC | 8h 50m |
| 2026-07-01 | SVA251 | JED → BHX | Jul 1, 13:55 UTC | Jul 1, 19:55 UTC | 6h 0m |
| 2026-07-01 | SVA315 | RUH → CAI | Jul 1, 06:55 UTC | Jul 1, 12:00 UTC | 5h 5m |
| 2026-06-30 | SVA260 | - | Jun 30, 19:45 UTC | Jul 1, 04:30 UTC | 8h 45m |
| 2026-06-30 | SVA266 | - | Jun 30, 09:40 UTC | Jun 30, 17:40 UTC | 8h 0m |
| 2026-06-30 | SVA265 | - | Jun 30, 06:10 UTC | Jun 30, 08:10 UTC | 2h 0m |
| 2026-06-10 | SVA319 | MED → CAI | Jun 10, 06:55 UTC | Jun 10, 12:40 UTC | 5h 45m |
| 2026-06-09 | SVA568 | JED → DXB | Jun 9, 08:55 UTC | Jun 9, 09:25 UTC | 30m |
| 2026-06-08 | SVA568 | JED → DXB | Jun 8, 12:25 UTC | Jun 9, 09:25 UTC | 21h 0m |
| 2026-06-06 | SVA168 | FRA → JED | Jun 6, 14:40 UTC | Jun 6, 17:40 UTC | 3h 0m |
| 2026-06-06 | SVA167 | JED → FRA | Jun 6, 08:40 UTC | Jun 6, 13:00 UTC | 4h 20m |
| 2026-06-05 | SVA319 | MED → CAI | Jun 5, 12:20 UTC | Jun 5, 12:35 UTC | 15m |
| 2026-06-04 | SVA317 | MED → CAI | Jun 4, 12:15 UTC | Jun 5, 06:30 UTC | 18h 15m |
| 2026-06-04 | SVA317 | MED → CAI | Jun 4, 08:25 UTC | Jun 5, 06:30 UTC | 22h 5m |
| 2026-06-03 | SVA252 | IST → MED | Jun 3, 21:15 UTC | Jun 4, 06:25 UTC | 9h 10m |
| 2026-06-03 | SVA251 | JED → BHX | Jun 3, 17:50 UTC | Jun 3, 19:55 UTC | 2h 5m |
| 2026-06-03 | SVA315 | RUH → CAI | Jun 3, 06:50 UTC | Jun 3, 12:00 UTC | 5h 10m |
| 2026-06-03 | SVA335 | JED → CAI | Jun 3, 04:20 UTC | Jun 3, 04:35 UTC | 15m |
| 2026-05-31 | SVA380 | CAI → MED | May 31, 18:40 UTC | May 31, 18:50 UTC | 10m |
| 2026-05-31 | SVA258 | IST → MED | May 31, 11:05 UTC | May 31, 16:55 UTC | 5h 50m |
| 2026-05-30 | SVA259 | MED → IST | May 30, 18:10 UTC | May 31, 09:15 UTC | 15h 5m |
| 2026-05-30 | SVA258 | IST → MED | May 30, 10:55 UTC | May 30, 16:30 UTC | 5h 35m |
| 2026-05-29 | SVA259 | MED → IST | May 29, 18:15 UTC | May 30, 09:15 UTC | 15h 0m |
| 2026-05-29 | SVA258 | IST → MED | May 29, 10:50 UTC | May 29, 16:30 UTC | 5h 41m |
| 2026-05-28 | SVA259 | MED → IST | May 28, 18:20 UTC | May 29, 09:05 UTC | 14h 45m |
| 2026-05-28 | SVA258 | IST → MED | May 28, 10:45 UTC | May 28, 16:45 UTC | 6h 0m |
| 2026-05-28 | SVA259 | MED → IST | May 28, 03:00 UTC | May 28, 08:55 UTC | 5h 55m |
| 2026-05-27 | SVA380 | CAI → MED | May 27, 18:30 UTC | May 28, 01:05 UTC | 6h 35m |
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-ASAB page for operator, model, and routing details .