sensors Mode-S transponder
710051
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AQH · AIRBUS A-330-300
- Hex
- 710051
- Octal
- 34200121
- Decimal
- 7,405,649
- Country
- SA
- Tail
- HZ-AQH
- Type
- A333
- Flights observed
- 49
- Distinct callsigns
- 18
- Country
- SA
- Last broadcast
- 3d ago
Current position
Country allocation
The ICAO 24-bit address 710051 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 18 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| SVA365 | Saudi Arabian Airlines | 7 | 2026-05-12 |
| SVA775 | Saudi Arabian Airlines | 6 | 2026-05-26 |
| SVA774 | Saudi Arabian Airlines | 6 | 2026-05-26 |
| SVA752 | Saudi Arabian Airlines | 5 | 2026-05-18 |
| SVA892 | Saudi Arabian Airlines | 3 | 2026-05-20 |
| SVA890 | Saudi Arabian Airlines | 3 | 2026-05-03 |
| SVA366 | Saudi Arabian Airlines | 3 | 2026-04-30 |
| SVA784 | Saudi Arabian Airlines | 2 | 2026-05-20 |
| SVA764 | Saudi Arabian Airlines | 2 | 2026-05-08 |
| SVA763 | Saudi Arabian Airlines | 2 | 2026-05-08 |
| SVA754 | Saudi Arabian Airlines | 2 | 2026-05-17 |
| SVA722 | Saudi Arabian Airlines | 2 | 2026-05-01 |
| SVA893 | Saudi Arabian Airlines | 1 | 2026-05-20 |
| SVA891 | - | 1 | 2026-04-13 |
| SVA755 | Saudi Arabian Airlines | 1 | 2026-05-17 |
| SVA5536 | - | 1 | 2026-05-12 |
| SVA389 | Saudi Arabian Airlines | 1 | 2026-05-24 |
| SVA388 | Saudi Arabian Airlines | 1 | 2026-05-24 |
Recent flights last 49
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-26 | SVA775 | COK → RUH | May 26, 15:00 UTC | May 26, 16:40 UTC | 1h 40m |
| 2026-05-26 | SVA774 | RUH → COK | May 26, 09:15 UTC | May 26, 13:15 UTC | 4h 0m |
| 2026-05-25 | SVA774 | RUH → COK | May 25, 13:00 UTC | May 26, 11:50 UTC | 22h 49m |
| 2026-05-24 | SVA388 | CAI → JED | May 24, 20:35 UTC | May 24, 20:50 UTC | 15m |
| 2026-05-24 | SVA389 | JED → CAI | May 24, 18:45 UTC | May 24, 18:55 UTC | 10m |
| 2026-05-21 | SVA775 | COK → RUH | May 21, 15:10 UTC | May 21, 16:30 UTC | 1h 20m |
| 2026-05-20 | SVA893 | LKO → JED | May 20, 22:20 UTC | May 21, 13:10 UTC | 14h 50m |
| 2026-05-20 | SVA892 | JED → LKO | May 20, 06:05 UTC | May 20, 17:30 UTC | 11h 25m |
| 2026-05-20 | SVA784 | JED → COK | May 20, 02:20 UTC | May 20, 03:55 UTC | 1h 35m |
| 2026-05-18 | SVA752 | JED → HYD | May 18, 06:35 UTC | May 18, 22:30 UTC | 15h 54m |
| 2026-05-18 | SVA752 | JED → HYD | May 18, 02:50 UTC | May 18, 22:30 UTC | 19h 39m |
| 2026-05-17 | SVA755 | HYD → JED | May 17, 06:55 UTC | May 18, 02:50 UTC | 19h 55m |
| 2026-05-17 | SVA754 | JED → HYD | May 17, 00:05 UTC | May 17, 07:35 UTC | 7h 30m |
| 2026-05-15 | SVA752 | JED → HYD | May 15, 15:15 UTC | May 15, 23:00 UTC | 7h 45m |
| 2026-05-13 | SVA752 | JED → HYD | May 13, 06:30 UTC | May 13, 22:50 UTC | 16h 20m |
| 2026-05-12 | SVA5536 | - | May 12, 11:25 UTC | May 13, 04:00 UTC | 16h 35m |
| 2026-05-12 | SVA365 | JED → TUN | May 12, 06:55 UTC | May 12, 08:55 UTC | 2h 0m |
| 2026-05-11 | SVA365 | JED → TUN | May 11, 12:20 UTC | May 12, 08:55 UTC | 20h 36m |
| 2026-05-11 | SVA365 | JED → TUN | May 11, 11:05 UTC | May 12, 08:55 UTC | 21h 51m |
| 2026-05-11 | SVA365 | JED → TUN | May 11, 05:30 UTC | May 11, 08:20 UTC | 2h 50m |
| 2026-05-08 | SVA763 | DEL → DMM | May 8, 21:30 UTC | May 8, 22:15 UTC | 45m |
| 2026-05-08 | SVA764 | JED → COK | May 8, 18:00 UTC | May 8, 19:35 UTC | 1h 35m |
| 2026-05-05 | SVA775 | COK → RUH | May 5, 18:40 UTC | May 5, 19:10 UTC | 30m |
| 2026-05-05 | SVA775 | COK → RUH | May 5, 15:01 UTC | May 5, 15:10 UTC | 10m |
| 2026-05-05 | SVA774 | RUH → COK | May 5, 12:45 UTC | May 5, 13:00 UTC | 15m |
| 2026-05-04 | SVA774 | RUH → COK | May 4, 21:15 UTC | May 5, 09:30 UTC | 12h 15m |
| 2026-05-04 | SVA754 | JED → HYD | May 4, 00:25 UTC | May 4, 15:55 UTC | 15h 30m |
| 2026-05-03 | SVA890 | JED → LKO | May 3, 00:35 UTC | May 3, 01:35 UTC | 1h 0m |
| 2026-05-01 | SVA722 | JED → ISB | May 1, 00:10 UTC | May 1, 09:35 UTC | 9h 25m |
| 2026-04-30 | SVA722 | JED → ISB | Apr 30, 12:20 UTC | May 1, 09:35 UTC | 21h 15m |
| 2026-04-30 | SVA366 | TUN → JED | Apr 30, 11:10 UTC | May 1, 09:35 UTC | 22h 25m |
| 2026-04-30 | SVA365 | JED → TUN | Apr 30, 06:45 UTC | Apr 30, 08:35 UTC | 1h 50m |
| 2026-04-26 | SVA366 | TUN → JED | Apr 26, 11:10 UTC | Apr 27, 01:05 UTC | 13h 55m |
| 2026-04-26 | SVA365 | JED → TUN | Apr 26, 06:35 UTC | Apr 26, 08:20 UTC | 1h 45m |
| 2026-04-24 | SVA763 | DEL → DMM | Apr 24, 21:20 UTC | Apr 24, 22:55 UTC | 1h 35m |
| 2026-04-24 | SVA764 | JED → COK | Apr 24, 01:10 UTC | Apr 24, 18:50 UTC | 17h 40m |
| 2026-04-22 | SVA752 | - | Apr 22, 06:01 UTC | Apr 22, 22:30 UTC | 16h 30m |
| 2026-04-22 | SVA784 | JED → COK | Apr 22, 00:10 UTC | Apr 22, 04:00 UTC | 3h 50m |
| 2026-04-20 | SVA892 | JED → LKO | Apr 20, 18:35 UTC | Apr 20, 18:45 UTC | 10m |
| 2026-04-20 | SVA892 | JED → LKO | Apr 20, 14:45 UTC | Apr 20, 15:45 UTC | 1h 0m |
| 2026-04-15 | SVA366 | - | Apr 15, 11:05 UTC | Apr 15, 12:45 UTC | 1h 40m |
| 2026-04-15 | SVA365 | JED → TUN | Apr 15, 07:01 UTC | Apr 15, 08:30 UTC | 1h 30m |
| 2026-04-14 | SVA775 | COK → RUH | Apr 14, 18:35 UTC | Apr 14, 18:45 UTC | 10m |
| 2026-04-14 | SVA775 | COK → RUH | Apr 14, 14:55 UTC | Apr 14, 15:15 UTC | 20m |
| 2026-04-14 | SVA774 | RUH → COK | Apr 14, 12:15 UTC | Apr 14, 12:45 UTC | 30m |
| 2026-04-14 | SVA774 | RUH → COK | Apr 14, 09:10 UTC | Apr 14, 09:25 UTC | 15m |
| 2026-04-13 | SVA891 | - | Apr 13, 06:50 UTC | Apr 13, 07:35 UTC | 45m |
| 2026-04-13 | SVA890 | - | Apr 13, 04:20 UTC | Apr 13, 05:05 UTC | 45m |
| 2026-04-13 | SVA890 | - | Apr 13, 00:50 UTC | Apr 13, 04:15 UTC | 3h 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-AQH page for operator, model, and routing details .