sensors Mode-S transponder
710052
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AQF · AIRBUS A-330-300
- Hex
- 710052
- Octal
- 34200122
- Decimal
- 7,405,650
- Country
- SA
- Tail
- HZ-AQF
- Type
- A333
- Flights observed
- 102
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 3d ago
Current position
Country allocation
The ICAO 24-bit address 710052 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 |
|---|---|---|---|
| SVA365 | Saudi Arabian Airlines | 18 | 2026-07-22 |
| SVA366 | Saudi Arabian Airlines | 9 | 2026-07-23 |
| SVA774 | Saudi Arabian Airlines | 7 | 2026-07-18 |
| SVA891 | - | 5 | 2026-06-26 |
| SVA784 | - | 4 | 2026-06-27 |
| SVA775 | Saudi Arabian Airlines | 4 | 2026-07-11 |
| SVA764 | Saudi Arabian Airlines | 4 | 2026-07-24 |
| SVA754 | - | 4 | 2026-06-24 |
| SVA722 | - | 4 | 2026-06-29 |
| SVA890 | - | 3 | 2026-06-25 |
| SVA783 | - | 3 | 2026-06-28 |
| SVA866 | - | 2 | 2026-06-20 |
| SVA772 | - | 2 | 2026-07-13 |
| SVA763 | Saudi Arabian Airlines | 2 | 2026-07-24 |
| SVA752 | Saudi Arabian Airlines | 2 | 2026-07-01 |
| SVA723 | - | 2 | 2026-06-27 |
| SVA588 | - | 2 | 2026-07-20 |
| SVA5723 | - | 2 | 2026-05-12 |
| SVA417 | Saudi Arabian Airlines | 2 | 2026-05-29 |
| SVA257 | - | 2 | 2026-07-02 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | SVA580 | JED → DXB | Jul 26, 06:00 UTC | Jul 26, 07:00 UTC | 1h 1m |
| 2026-07-24 | SVA763 | DEL → DMM | Jul 24, 21:20 UTC | Jul 25, 00:25 UTC | 3h 5m |
| 2026-07-24 | SVA764 | JED → COK | Jul 24, 15:30 UTC | Jul 24, 19:35 UTC | 4h 5m |
| 2026-07-24 | SVA383 | JED → CAI | Jul 24, 01:45 UTC | Jul 24, 02:10 UTC | 25m |
| 2026-07-23 | SVA388 | - | Jul 23, 20:40 UTC | Jul 23, 20:50 UTC | 10m |
| 2026-07-23 | SVA366 | TUN → JED | Jul 23, 11:15 UTC | Jul 23, 18:30 UTC | 7h 15m |
| 2026-07-22 | SVA365 | JED → TUN | Jul 22, 12:35 UTC | Jul 23, 08:10 UTC | 19h 35m |
| 2026-07-22 | SVA365 | JED → TUN | Jul 22, 11:10 UTC | Jul 23, 08:10 UTC | 21h 0m |
| 2026-07-21 | SVA366 | TUN → JED | Jul 21, 11:15 UTC | Jul 21, 12:40 UTC | 1h 25m |
| 2026-07-20 | SVA365 | JED → TUN | Jul 20, 14:15 UTC | Jul 21, 08:00 UTC | 17h 44m |
| 2026-07-20 | SVA588 | - | Jul 20, 10:55 UTC | Jul 20, 12:20 UTC | 1h 25m |
| 2026-07-19 | SVA366 | TUN → JED | Jul 19, 11:10 UTC | Jul 19, 12:30 UTC | 1h 20m |
| 2026-07-18 | SVA365 | JED → TUN | Jul 18, 15:00 UTC | Jul 19, 08:00 UTC | 17h 0m |
| 2026-07-18 | SVA774 | RUH → COK | Jul 18, 09:20 UTC | Jul 18, 13:30 UTC | 4h 10m |
| 2026-07-15 | SVA366 | TUN → JED | Jul 15, 11:00 UTC | Jul 15, 13:10 UTC | 2h 10m |
| 2026-07-14 | SVA365 | - | Jul 14, 12:45 UTC | Jul 15, 08:25 UTC | 19h 39m |
| 2026-07-14 | SVA365 | - | Jul 14, 10:55 UTC | Jul 15, 08:25 UTC | 21h 29m |
| 2026-07-13 | SVA365 | - | Jul 13, 21:25 UTC | Jul 14, 08:20 UTC | 10h 55m |
| 2026-07-13 | SVA772 | - | Jul 13, 15:55 UTC | Jul 13, 19:15 UTC | 3h 20m |
| 2026-07-11 | SVA775 | COK → RUH | Jul 11, 15:05 UTC | Jul 11, 18:40 UTC | 3h 35m |
| 2026-07-10 | SVA774 | - | Jul 10, 23:05 UTC | Jul 11, 13:00 UTC | 13h 55m |
| 2026-07-10 | SVA366 | TUN → JED | Jul 10, 11:10 UTC | Jul 10, 21:20 UTC | 10h 10m |
| 2026-07-10 | SVA365 | - | Jul 10, 06:25 UTC | Jul 10, 07:55 UTC | 1h 30m |
| 2026-07-08 | SVA773 | - | Jul 8, 21:15 UTC | Jul 8, 23:35 UTC | 2h 20m |
| 2026-07-08 | SVA772 | - | Jul 8, 16:20 UTC | Jul 8, 19:30 UTC | 3h 10m |
| 2026-07-03 | SVA256 | IST → JED | Jul 3, 12:45 UTC | Jul 3, 14:35 UTC | 1h 50m |
| 2026-07-02 | SVA257 | - | Jul 2, 15:10 UTC | Jul 3, 10:15 UTC | 19h 5m |
| 2026-07-01 | SVA774 | - | Jul 1, 18:35 UTC | Jul 2, 13:10 UTC | 18h 35m |
| 2026-07-01 | SVA774 | - | Jul 1, 16:35 UTC | Jul 2, 13:10 UTC | 20h 35m |
| 2026-07-01 | SVA752 | JED → HYD | Jul 1, 15:40 UTC | Jul 2, 13:10 UTC | 21h 30m |
| 2026-06-29 | SVA722 | - | Jun 29, 00:20 UTC | Jun 29, 08:29 UTC | 8h 10m |
| 2026-06-28 | SVA783 | - | Jun 28, 07:29 UTC | Jun 28, 16:00 UTC | 8h 30m |
| 2026-06-28 | SVA783 | - | Jun 28, 06:10 UTC | Jun 28, 06:20 UTC | 10m |
| 2026-06-27 | SVA784 | - | Jun 27, 08:35 UTC | Jun 28, 04:29 UTC | 19h 55m |
| 2026-06-27 | SVA784 | - | Jun 27, 07:59 UTC | Jun 28, 04:29 UTC | 20h 30m |
| 2026-06-27 | SVA784 | - | Jun 27, 06:19 UTC | Jun 28, 04:29 UTC | 22h 10m |
| 2026-06-27 | SVA723 | - | Jun 27, 02:45 UTC | Jun 28, 00:59 UTC | 22h 15m |
| 2026-06-27 | SVA723 | - | Jun 27, 00:34 UTC | Jun 28, 00:30 UTC | 23h 55m |
| 2026-06-27 | SVA722 | - | Jun 27, 00:05 UTC | Jun 27, 08:35 UTC | 8h 30m |
| 2026-06-26 | SVA722 | - | Jun 26, 08:34 UTC | Jun 27, 08:29 UTC | 23h 55m |
| 2026-06-26 | SVA891 | - | Jun 26, 07:45 UTC | Jun 27, 06:25 UTC | 22h 40m |
| 2026-06-26 | SVA891 | - | Jun 26, 06:39 UTC | Jun 26, 06:50 UTC | 10m |
| 2026-06-25 | SVA890 | - | Jun 25, 13:45 UTC | Jun 26, 04:20 UTC | 14h 35m |
| 2026-06-24 | SVA588 | - | Jun 24, 21:29 UTC | Jun 25, 12:04 UTC | 14h 35m |
| 2026-06-24 | SVA754 | - | Jun 24, 00:34 UTC | Jun 24, 19:34 UTC | 19h 0m |
| 2026-06-21 | SVA5722 | - | Jun 21, 00:25 UTC | Jun 21, 08:15 UTC | 7h 50m |
| 2026-06-20 | SVA867 | - | Jun 20, 06:10 UTC | Jun 21, 00:55 UTC | 18h 45m |
| 2026-06-20 | SVA866 | - | Jun 20, 00:14 UTC | Jun 20, 04:24 UTC | 4h 10m |
| 2026-06-15 | SVA891 | LKO → JED | Jun 15, 09:25 UTC | Jun 15, 10:05 UTC | 40m |
| 2026-06-15 | SVA890 | JED → LKO | Jun 15, 04:25 UTC | Jun 15, 04:45 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-AQF page for operator, model, and routing details .