sensors Mode-S transponder
710058
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AK16 · BOEING 777-300ER
- Hex
- 710058
- Octal
- 34200130
- Decimal
- 7,405,656
- Country
- SA
- Tail
- HZ-AK16
- Type
- B77W
- Flights observed
- 181
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 5h ago
Last known position
Country allocation
The ICAO 24-bit address 710058 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 |
|---|---|---|---|
| SVA760 | Saudi Arabian Airlines | 10 | 2026-05-21 |
| SVA826 | - | 9 | 2026-06-30 |
| SVA738 | Saudi Arabian Airlines | 8 | 2026-07-08 |
| SVA341 | - | 8 | 2026-07-03 |
| SVA802 | Saudi Arabian Airlines | 6 | 2026-07-11 |
| SVA761 | Saudi Arabian Airlines | 6 | 2026-05-09 |
| SVA734 | - | 6 | 2026-06-26 |
| SVA5726 | - | 6 | 2026-06-27 |
| SVA818 | - | 5 | 2026-06-25 |
| SVA811 | - | 5 | 2026-07-14 |
| SVA807 | Saudi Arabian Airlines | 5 | 2026-05-23 |
| SVA816 | - | 4 | 2026-07-12 |
| SVA803 | - | 4 | 2026-07-11 |
| SVA5561 | - | 4 | 2026-06-06 |
| SVA340 | Saudi Arabian Airlines | 4 | 2026-07-10 |
| SVA9652 | - | 3 | 2026-04-20 |
| SVA819 | Saudi Arabian Airlines | 3 | 2026-06-01 |
| SVA810 | - | 3 | 2026-07-13 |
| SVA806 | Saudi Arabian Airlines | 3 | 2026-05-22 |
| SVA804 | Saudi Arabian Airlines | 3 | 2026-05-24 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | SVA811 | - | Jul 14, 00:15 UTC | Jul 14, 04:05 UTC | 3h 50m |
| 2026-07-13 | SVA810 | - | Jul 13, 05:01 UTC | Jul 13, 22:15 UTC | 17h 15m |
| 2026-07-12 | SVA816 | - | Jul 12, 16:01 UTC | Jul 13, 00:05 UTC | 8h 5m |
| 2026-07-12 | SVA816 | - | Jul 12, 00:05 UTC | Jul 13, 00:01 UTC | 23h 55m |
| 2026-07-11 | SVA803 | - | Jul 11, 22:05 UTC | Jul 12, 19:35 UTC | 21h 30m |
| 2026-07-11 | SVA803 | - | Jul 11, 21:55 UTC | Jul 12, 19:35 UTC | 21h 40m |
| 2026-07-11 | SVA802 | JED → DAC | Jul 11, 00:05 UTC | Jul 11, 19:05 UTC | 19h 0m |
| 2026-07-10 | SVA700 | - | Jul 10, 16:05 UTC | Jul 11, 15:10 UTC | 23h 6m |
| 2026-07-10 | SVA340 | ALG → JED | Jul 10, 14:50 UTC | Jul 11, 05:55 UTC | 15h 5m |
| 2026-07-09 | SVA378 | - | Jul 9, 18:15 UTC | Jul 10, 11:55 UTC | 17h 40m |
| 2026-07-08 | SVA379 | - | Jul 8, 22:05 UTC | Jul 9, 16:10 UTC | 18h 5m |
| 2026-07-08 | SVA738 | JED → LHE | Jul 8, 17:10 UTC | Jul 8, 19:55 UTC | 2h 45m |
| 2026-07-06 | SVA726 | JED → ISB | Jul 6, 07:15 UTC | Jul 7, 00:35 UTC | 17h 20m |
| 2026-07-06 | SVA817 | - | Jul 6, 03:40 UTC | Jul 6, 03:50 UTC | 10m |
| 2026-07-06 | SVA816 | - | Jul 6, 00:25 UTC | Jul 6, 00:45 UTC | 20m |
| 2026-07-05 | SVA816 | - | Jul 5, 06:15 UTC | Jul 5, 23:35 UTC | 17h 20m |
| 2026-07-04 | SVA340 | ALG → JED | Jul 4, 14:45 UTC | Jul 5, 01:40 UTC | 10h 55m |
| 2026-07-03 | SVA341 | - | Jul 3, 16:10 UTC | Jul 4, 11:30 UTC | 19h 20m |
| 2026-07-03 | SVA372 | CMN → JED | Jul 3, 14:25 UTC | Jul 4, 11:30 UTC | 21h 5m |
| 2026-07-02 | SVA373 | - | Jul 2, 22:10 UTC | Jul 3, 11:10 UTC | 13h 0m |
| 2026-07-02 | SVA738 | JED → LHE | Jul 2, 16:55 UTC | Jul 2, 19:40 UTC | 2h 45m |
| 2026-07-01 | SVA738 | JED → LHE | Jul 1, 22:05 UTC | Jul 2, 19:40 UTC | 21h 35m |
| 2026-07-01 | SVA738 | JED → LHE | Jul 1, 21:30 UTC | Jul 2, 19:40 UTC | 22h 10m |
| 2026-07-01 | SVA738 | JED → LHE | Jul 1, 18:05 UTC | Jul 2, 17:55 UTC | 23h 50m |
| 2026-07-01 | SVA827 | - | Jul 1, 17:50 UTC | Jul 1, 22:05 UTC | 4h 15m |
| 2026-06-30 | SVA826 | - | Jun 30, 22:35 UTC | Jul 1, 15:25 UTC | 16h 50m |
| 2026-06-30 | SVA826 | - | Jun 30, 19:25 UTC | Jul 1, 15:25 UTC | 20h 0m |
| 2026-06-30 | SVA826 | - | Jun 30, 16:45 UTC | Jul 1, 15:25 UTC | 22h 40m |
| 2026-06-30 | SVA811 | DAC → JED | Jun 30, 02:05 UTC | Jul 1, 00:40 UTC | 22h 35m |
| 2026-06-30 | SVA811 | DAC → JED | Jun 30, 00:04 UTC | Jun 30, 22:35 UTC | 22h 30m |
| 2026-06-29 | SVA810 | - | Jun 29, 04:55 UTC | Jun 29, 22:05 UTC | 17h 10m |
| 2026-06-28 | SVA5966 | - | Jun 28, 08:05 UTC | Jun 29, 02:50 UTC | 18h 45m |
| 2026-06-28 | SVA5966 | - | Jun 28, 07:44 UTC | Jun 29, 02:50 UTC | 19h 5m |
| 2026-06-28 | SVA728 | - | Jun 28, 00:20 UTC | Jun 29, 00:00 UTC | 23h 40m |
| 2026-06-27 | SVA728 | - | Jun 27, 22:40 UTC | Jun 28, 15:49 UTC | 17h 10m |
| 2026-06-27 | SVA5726 | - | Jun 27, 16:35 UTC | Jun 28, 15:49 UTC | 23h 15m |
| 2026-06-27 | SVA5726 | - | Jun 27, 08:05 UTC | Jun 28, 08:00 UTC | 23h 55m |
| 2026-06-27 | SVA5726 | - | Jun 27, 06:05 UTC | Jun 28, 01:15 UTC | 19h 10m |
| 2026-06-27 | SVA5726 | - | Jun 27, 05:39 UTC | Jun 28, 01:15 UTC | 19h 35m |
| 2026-06-26 | SVA734 | - | Jun 26, 10:50 UTC | Jun 27, 03:09 UTC | 16h 20m |
| 2026-06-25 | SVA818 | - | Jun 25, 14:50 UTC | Jun 26, 08:50 UTC | 18h 0m |
| 2026-06-25 | SVA341 | - | Jun 25, 09:29 UTC | Jun 25, 12:30 UTC | 3h 0m |
| 2026-06-24 | SVA341 | - | Jun 24, 14:39 UTC | Jun 25, 12:30 UTC | 21h 50m |
| 2026-06-24 | SVA341 | - | Jun 24, 12:50 UTC | Jun 25, 11:59 UTC | 23h 10m |
| 2026-06-24 | SVA3832 | - | Jun 24, 07:24 UTC | Jun 24, 10:30 UTC | 3h 5m |
| 2026-06-22 | SVA9643 | - | Jun 22, 23:45 UTC | Jun 23, 02:04 UTC | 2h 20m |
| 2026-06-22 | SVA5930 | - | Jun 22, 04:59 UTC | Jun 22, 21:35 UTC | 16h 35m |
| 2026-06-21 | SVA9651 | - | Jun 21, 14:40 UTC | Jun 22, 02:59 UTC | 12h 20m |
| 2026-06-21 | SVA5922 | - | Jun 21, 09:24 UTC | Jun 21, 13:24 UTC | 4h 0m |
| 2026-06-20 | SVA5922 | - | Jun 20, 16:55 UTC | Jun 21, 13:24 UTC | 20h 30m |
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-AK16 page for operator, model, and routing details .