sensors Mode-S transponder
710062
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AQL · AIRBUS A-330-300
- Hex
- 710062
- Octal
- 34200142
- Decimal
- 7,405,666
- Country
- SA
- Tail
- HZ-AQL
- Type
- A333
- Flights observed
- 61
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 8d ago
Last known position
Country allocation
The ICAO 24-bit address 710062 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 |
|---|---|---|---|
| SVA893 | Saudi Arabian Airlines | 8 | 2026-07-22 |
| SVA892 | Saudi Arabian Airlines | 8 | 2026-07-22 |
| SVA770 | Saudi Arabian Airlines | 5 | 2026-07-20 |
| SVA784 | - | 4 | 2026-07-01 |
| SVA772 | Saudi Arabian Airlines | 4 | 2026-07-04 |
| SVA754 | Saudi Arabian Airlines | 4 | 2026-07-22 |
| SVA891 | Saudi Arabian Airlines | 3 | 2026-07-26 |
| SVA890 | Saudi Arabian Airlines | 3 | 2026-07-25 |
| SVA866 | Saudi Arabian Airlines | 3 | 2026-07-18 |
| SVA867 | - | 2 | 2026-07-18 |
| SVA755 | Saudi Arabian Airlines | 2 | 2026-06-28 |
| SVA588 | - | 2 | 2026-07-24 |
| TEST | - | 1 | 2026-06-08 |
| SVA9052 | - | 1 | 2026-06-15 |
| SVA814 | - | 1 | 2026-07-24 |
| SVA796 | - | 1 | 2026-06-26 |
| SVA775 | Saudi Arabian Airlines | 1 | 2026-06-19 |
| SVA774 | - | 1 | 2026-06-19 |
| SVA771 | Saudi Arabian Airlines | 1 | 2026-07-20 |
| SVA763 | - | 1 | 2026-07-15 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | SVA891 | LKO → JED | Jul 26, 06:50 UTC | Jul 26, 07:35 UTC | 45m |
| 2026-07-25 | SVA890 | JED → LKO | Jul 25, 18:15 UTC | Jul 26, 03:35 UTC | 9h 20m |
| 2026-07-24 | SVA588 | - | Jul 24, 22:35 UTC | Jul 25, 16:50 UTC | 18h 15m |
| 2026-07-24 | SVA588 | - | Jul 24, 22:25 UTC | Jul 25, 16:50 UTC | 18h 25m |
| 2026-07-24 | SVA814 | - | Jul 24, 19:20 UTC | Jul 24, 20:15 UTC | 55m |
| 2026-07-24 | SVA891 | LKO → JED | Jul 24, 06:55 UTC | Jul 24, 17:00 UTC | 10h 5m |
| 2026-07-24 | SVA890 | JED → LKO | Jul 24, 01:10 UTC | Jul 24, 04:35 UTC | 3h 25m |
| 2026-07-22 | SVA893 | LKO → JED | Jul 22, 22:25 UTC | Jul 23, 00:20 UTC | 1h 55m |
| 2026-07-22 | SVA892 | JED → LKO | Jul 22, 00:35 UTC | Jul 22, 19:00 UTC | 18h 25m |
| 2026-07-22 | SVA754 | JED → HYD | Jul 22, 00:00 UTC | Jul 22, 19:00 UTC | 19h 0m |
| 2026-07-20 | SVA771 | MAA → JED | Jul 20, 06:10 UTC | Jul 20, 08:20 UTC | 2h 10m |
| 2026-07-20 | SVA770 | JED → BOM | Jul 20, 00:45 UTC | Jul 20, 04:10 UTC | 3h 25m |
| 2026-07-18 | SVA867 | - | Jul 18, 06:15 UTC | Jul 18, 15:55 UTC | 9h 40m |
| 2026-07-18 | SVA866 | JED → BLR | Jul 18, 02:55 UTC | Jul 18, 04:25 UTC | 1h 30m |
| 2026-07-16 | SVA302 | - | Jul 16, 18:10 UTC | Jul 16, 18:25 UTC | 15m |
| 2026-07-16 | SVA303 | - | Jul 16, 15:45 UTC | Jul 16, 16:05 UTC | 20m |
| 2026-07-16 | SVA300 | - | Jul 16, 09:50 UTC | Jul 16, 10:00 UTC | 10m |
| 2026-07-15 | SVA763 | - | Jul 15, 21:25 UTC | Jul 16, 08:05 UTC | 10h 40m |
| 2026-07-15 | SVA867 | - | Jul 15, 06:10 UTC | Jul 15, 19:35 UTC | 13h 25m |
| 2026-07-15 | SVA866 | - | Jul 15, 00:20 UTC | Jul 15, 04:20 UTC | 4h 0m |
| 2026-07-13 | SVA893 | LKO → JED | Jul 13, 22:15 UTC | Jul 14, 00:30 UTC | 2h 15m |
| 2026-07-13 | SVA892 | JED → LKO | Jul 13, 06:01 UTC | Jul 13, 19:05 UTC | 13h 5m |
| 2026-07-13 | SVA770 | - | Jul 13, 00:35 UTC | Jul 13, 03:55 UTC | 3h 20m |
| 2026-07-12 | SVA770 | - | Jul 12, 07:45 UTC | Jul 13, 03:55 UTC | 20h 10m |
| 2026-07-12 | SVA770 | - | Jul 12, 05:50 UTC | Jul 13, 03:55 UTC | 22h 5m |
| 2026-07-12 | SVA770 | - | Jul 12, 00:40 UTC | Jul 12, 03:45 UTC | 3h 5m |
| 2026-07-08 | SVA893 | LKO → JED | Jul 8, 22:25 UTC | Jul 9, 00:35 UTC | 2h 10m |
| 2026-07-08 | SVA892 | JED → LKO | Jul 8, 00:35 UTC | Jul 8, 19:10 UTC | 18h 35m |
| 2026-07-08 | SVA754 | - | Jul 8, 00:10 UTC | Jul 8, 19:10 UTC | 19h 0m |
| 2026-07-06 | SVA893 | LKO → JED | Jul 6, 21:30 UTC | Jul 6, 22:20 UTC | 50m |
| 2026-07-06 | SVA892 | JED → LKO | Jul 6, 06:05 UTC | Jul 6, 18:15 UTC | 12h 10m |
| 2026-07-05 | SVA866 | - | Jul 5, 10:55 UTC | Jul 6, 04:20 UTC | 17h 25m |
| 2026-07-04 | SVA365 | - | Jul 4, 21:15 UTC | Jul 5, 08:20 UTC | 11h 5m |
| 2026-07-04 | SVA772 | JED → BOM | Jul 4, 15:55 UTC | Jul 4, 19:20 UTC | 3h 25m |
| 2026-07-03 | SVA772 | JED → BOM | Jul 3, 23:25 UTC | Jul 4, 19:20 UTC | 19h 55m |
| 2026-07-03 | SVA772 | JED → BOM | Jul 3, 21:25 UTC | Jul 4, 19:20 UTC | 21h 55m |
| 2026-07-03 | SVA772 | JED → BOM | Jul 3, 09:40 UTC | Jul 3, 19:10 UTC | 9h 30m |
| 2026-07-03 | SVA891 | - | Jul 3, 06:55 UTC | Jul 3, 07:40 UTC | 45m |
| 2026-07-03 | SVA890 | - | Jul 3, 00:50 UTC | Jul 3, 04:30 UTC | 3h 40m |
| 2026-07-01 | SVA893 | LKO → JED | Jul 1, 22:30 UTC | Jul 2, 00:40 UTC | 2h 10m |
| 2026-07-01 | SVA892 | JED → LKO | Jul 1, 06:35 UTC | Jul 1, 18:45 UTC | 12h 10m |
| 2026-07-01 | SVA784 | - | Jul 1, 00:45 UTC | Jul 1, 05:00 UTC | 4h 15m |
| 2026-06-29 | SVA893 | LKO → JED | Jun 29, 21:19 UTC | Jun 30, 00:35 UTC | 3h 15m |
| 2026-06-29 | SVA892 | JED → LKO | Jun 29, 06:09 UTC | Jun 29, 19:05 UTC | 12h 55m |
| 2026-06-29 | SVA784 | - | Jun 29, 00:14 UTC | Jun 29, 04:39 UTC | 4h 25m |
| 2026-06-28 | SVA784 | - | Jun 28, 08:44 UTC | Jun 29, 04:39 UTC | 19h 55m |
| 2026-06-28 | SVA784 | - | Jun 28, 06:55 UTC | Jun 29, 04:39 UTC | 21h 45m |
| 2026-06-28 | SVA755 | HYD → JED | Jun 28, 02:34 UTC | Jun 29, 01:05 UTC | 22h 30m |
| 2026-06-28 | SVA755 | HYD → JED | Jun 28, 00:35 UTC | Jun 29, 00:29 UTC | 23h 55m |
| 2026-06-28 | SVA754 | - | Jun 28, 00:00 UTC | Jun 28, 09:10 UTC | 9h 10m |
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-AQL page for operator, model, and routing details .