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
- 106
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 2d ago
Last known 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| SVA365 | - | 15 | 2026-07-10 |
| SVA774 | - | 14 | 2026-07-09 |
| SVA775 | Saudi Arabian Airlines | 12 | 2026-07-09 |
| SVA752 | Saudi Arabian Airlines | 9 | 2026-06-26 |
| SVA366 | Saudi Arabian Airlines | 8 | 2026-07-11 |
| SVA890 | - | 7 | 2026-06-22 |
| SVA784 | Saudi Arabian Airlines | 5 | 2026-06-07 |
| SVA764 | Saudi Arabian Airlines | 5 | 2026-06-19 |
| SVA763 | - | 5 | 2026-07-01 |
| SVA754 | - | 5 | 2026-07-12 |
| SVA892 | Saudi Arabian Airlines | 3 | 2026-05-20 |
| SVA722 | - | 3 | 2026-06-24 |
| SVA891 | - | 2 | 2026-06-22 |
| SVA772 | - | 2 | 2026-07-10 |
| SVA893 | Saudi Arabian Airlines | 1 | 2026-05-20 |
| SVA867 | - | 1 | 2026-06-29 |
| SVA866 | - | 1 | 2026-06-29 |
| SVA783 | Saudi Arabian Airlines | 1 | 2026-06-07 |
| SVA755 | Saudi Arabian Airlines | 1 | 2026-05-17 |
| SVA5742 | - | 1 | 2026-06-15 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-12 | SVA754 | - | Jul 12, 00:30 UTC | Jul 12, 09:05 UTC | 8h 35m |
| 2026-07-11 | SVA754 | - | Jul 11, 12:55 UTC | Jul 12, 09:05 UTC | 20h 10m |
| 2026-07-11 | SVA366 | TUN → JED | Jul 11, 11:05 UTC | Jul 11, 12:35 UTC | 1h 30m |
| 2026-07-10 | SVA365 | - | Jul 10, 21:20 UTC | Jul 11, 08:15 UTC | 10h 55m |
| 2026-07-10 | SVA772 | - | Jul 10, 15:55 UTC | Jul 10, 19:10 UTC | 3h 15m |
| 2026-07-09 | SVA772 | - | Jul 9, 18:20 UTC | Jul 10, 16:55 UTC | 22h 35m |
| 2026-07-09 | SVA775 | COK → RUH | Jul 9, 16:20 UTC | Jul 10, 16:15 UTC | 23h 55m |
| 2026-07-09 | SVA775 | COK → RUH | Jul 9, 15:00 UTC | Jul 9, 18:45 UTC | 3h 45m |
| 2026-07-09 | SVA774 | - | Jul 9, 08:55 UTC | Jul 9, 13:25 UTC | 4h 30m |
| 2026-07-07 | SVA775 | COK → RUH | Jul 7, 15:00 UTC | Jul 7, 18:40 UTC | 3h 40m |
| 2026-07-07 | SVA774 | - | Jul 7, 09:05 UTC | Jul 7, 13:10 UTC | 4h 5m |
| 2026-07-06 | SVA774 | - | Jul 6, 12:20 UTC | Jul 7, 11:45 UTC | 23h 25m |
| 2026-07-06 | SVA366 | TUN → JED | Jul 6, 10:55 UTC | Jul 7, 09:30 UTC | 22h 35m |
| 2026-07-06 | SVA365 | - | Jul 6, 06:25 UTC | Jul 6, 08:20 UTC | 1h 55m |
| 2026-07-01 | SVA763 | - | Jul 1, 21:25 UTC | Jul 2, 07:50 UTC | 10h 25m |
| 2026-07-01 | SVA754 | - | Jul 1, 00:20 UTC | Jul 1, 19:50 UTC | 19h 30m |
| 2026-06-29 | SVA867 | - | Jun 29, 06:09 UTC | Jun 29, 15:54 UTC | 9h 45m |
| 2026-06-29 | SVA866 | - | Jun 29, 00:24 UTC | Jun 29, 04:30 UTC | 4h 5m |
| 2026-06-27 | SVA1117 | DMM → JED | Jun 27, 15:34 UTC | Jun 27, 15:45 UTC | 10m |
| 2026-06-26 | SVA752 | JED → HYD | Jun 26, 06:19 UTC | Jun 27, 00:20 UTC | 18h 0m |
| 2026-06-26 | SVA752 | JED → HYD | Jun 26, 03:05 UTC | Jun 27, 00:20 UTC | 21h 15m |
| 2026-06-26 | SVA752 | JED → HYD | Jun 26, 00:20 UTC | Jun 27, 00:14 UTC | 23h 55m |
| 2026-06-24 | SVA722 | - | Jun 24, 00:15 UTC | Jun 24, 08:45 UTC | 8h 30m |
| 2026-06-22 | SVA891 | - | Jun 22, 07:49 UTC | Jun 22, 09:49 UTC | 2h 0m |
| 2026-06-22 | SVA890 | - | Jun 22, 00:44 UTC | Jun 22, 04:40 UTC | 3h 55m |
| 2026-06-21 | SVA890 | - | Jun 21, 08:20 UTC | Jun 22, 04:40 UTC | 20h 20m |
| 2026-06-21 | SVA890 | - | Jun 21, 07:40 UTC | Jun 22, 04:40 UTC | 21h 0m |
| 2026-06-20 | SVA890 | - | Jun 20, 10:39 UTC | Jun 21, 04:49 UTC | 18h 10m |
| 2026-06-19 | SVA763 | DEL → DMM | Jun 19, 21:30 UTC | Jun 20, 07:44 UTC | 10h 15m |
| 2026-06-19 | SVA764 | JED → COK | Jun 19, 15:19 UTC | Jun 19, 19:39 UTC | 4h 20m |
| 2026-06-18 | SVA366 | TUN → JED | Jun 18, 11:00 UTC | Jun 18, 13:00 UTC | 2h 0m |
| 2026-06-17 | SVA365 | - | Jun 17, 12:20 UTC | Jun 18, 08:05 UTC | 19h 45m |
| 2026-06-17 | SVA365 | - | Jun 17, 11:00 UTC | Jun 18, 08:05 UTC | 21h 5m |
| 2026-06-16 | SVA365 | - | Jun 16, 12:20 UTC | Jun 17, 08:10 UTC | 19h 51m |
| 2026-06-16 | SVA366 | TUN → JED | Jun 16, 10:49 UTC | Jun 17, 08:10 UTC | 21h 21m |
| 2026-06-15 | SVA365 | JED → TUN | Jun 15, 18:29 UTC | Jun 16, 08:10 UTC | 13h 40m |
| 2026-06-15 | SVA5742 | - | Jun 15, 00:29 UTC | Jun 15, 16:04 UTC | 15h 35m |
| 2026-06-12 | SVA763 | DEL → DMM | Jun 12, 21:30 UTC | Jun 13, 13:15 UTC | 15h 44m |
| 2026-06-12 | SVA764 | JED → COK | Jun 12, 15:25 UTC | Jun 12, 19:25 UTC | 4h 0m |
| 2026-06-11 | SVA764 | JED → COK | Jun 11, 18:40 UTC | Jun 12, 17:55 UTC | 23h 16m |
| 2026-06-11 | SVA775 | COK → RUH | Jun 11, 16:20 UTC | Jun 12, 15:45 UTC | 23h 25m |
| 2026-06-11 | SVA775 | COK → RUH | Jun 11, 15:05 UTC | Jun 11, 19:00 UTC | 3h 55m |
| 2026-06-11 | SVA774 | RUH → COK | Jun 11, 08:55 UTC | Jun 11, 13:10 UTC | 4h 15m |
| 2026-06-09 | SVA775 | COK → RUH | Jun 9, 15:05 UTC | Jun 9, 15:35 UTC | 30m |
| 2026-06-08 | SVA774 | RUH → COK | Jun 8, 18:55 UTC | Jun 9, 13:05 UTC | 18h 10m |
| 2026-06-08 | SVA774 | RUH → COK | Jun 8, 16:25 UTC | Jun 9, 13:05 UTC | 20h 40m |
| 2026-06-08 | SVA774 | RUH → COK | Jun 8, 15:04 UTC | Jun 9, 13:05 UTC | 22h 0m |
| 2026-06-08 | SVA774 | RUH → COK | Jun 8, 09:00 UTC | Jun 8, 13:05 UTC | 4h 5m |
| 2026-06-07 | SVA783 | COK → JED | Jun 7, 06:10 UTC | Jun 7, 07:40 UTC | 1h 30m |
| 2026-06-07 | SVA784 | JED → COK | Jun 7, 02:35 UTC | Jun 7, 04:10 UTC | 1h 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-AQH page for operator, model, and routing details .