sensors Mode-S transponder
710059
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AK17 · BOEING 777-300ER
- Hex
- 710059
- Octal
- 34200131
- Decimal
- 7,405,657
- Country
- SA
- Tail
- HZ-AK17
- Type
- B77W
- Flights observed
- 169
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address 710059 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 |
|---|---|---|---|
| SVA826 | - | 13 | 2026-07-01 |
| SVA827 | - | 12 | 2026-07-04 |
| SVA818 | - | 12 | 2026-07-12 |
| SVA819 | - | 9 | 2026-07-12 |
| SVA802 | Saudi Arabian Airlines | 8 | 2026-07-03 |
| SVA805 | - | 5 | 2026-06-17 |
| SVA803 | - | 5 | 2026-07-03 |
| SVA724 | - | 5 | 2026-06-19 |
| SVA862 | Saudi Arabian Airlines | 4 | 2026-05-26 |
| SVA807 | Saudi Arabian Airlines | 4 | 2026-06-01 |
| SVA9646 | - | 3 | 2026-05-15 |
| SVA861 | Saudi Arabian Airlines | 3 | 2026-05-27 |
| SVA806 | Saudi Arabian Airlines | 3 | 2026-06-09 |
| SVA804 | Saudi Arabian Airlines | 3 | 2026-06-16 |
| SVA758 | Saudi Arabian Airlines | 3 | 2026-07-09 |
| SVA756 | Saudi Arabian Airlines | 3 | 2026-05-18 |
| SVA722 | - | 3 | 2026-07-14 |
| SVA5804 | - | 3 | 2026-06-03 |
| SVA340 | Saudi Arabian Airlines | 3 | 2026-07-08 |
| SVA9648 | - | 2 | 2026-05-08 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | SVA722 | - | Jul 14, 00:30 UTC | Jul 14, 08:45 UTC | 8h 15m |
| 2026-07-13 | SVA722 | - | Jul 13, 05:35 UTC | Jul 14, 01:25 UTC | 19h 50m |
| 2026-07-12 | SVA700 | - | Jul 12, 14:25 UTC | Jul 13, 05:55 UTC | 15h 30m |
| 2026-07-12 | SVA819 | - | Jul 12, 10:50 UTC | Jul 12, 11:01 UTC | 10m |
| 2026-07-12 | SVA818 | - | Jul 12, 00:35 UTC | Jul 12, 08:50 UTC | 8h 15m |
| 2026-07-11 | SVA818 | - | Jul 11, 07:55 UTC | Jul 12, 04:10 UTC | 20h 15m |
| 2026-07-11 | SVA818 | - | Jul 11, 06:10 UTC | Jul 12, 04:10 UTC | 22h 0m |
| 2026-07-11 | SVA723 | - | Jul 11, 03:05 UTC | Jul 12, 01:00 UTC | 21h 55m |
| 2026-07-10 | SVA722 | - | Jul 10, 15:00 UTC | Jul 11, 08:10 UTC | 17h 11m |
| 2026-07-09 | SVA758 | JED → DEL | Jul 9, 22:30 UTC | Jul 10, 12:55 UTC | 14h 25m |
| 2026-07-09 | SVA343 | JED → ALG | Jul 9, 00:40 UTC | Jul 9, 19:45 UTC | 19h 5m |
| 2026-07-08 | SVA340 | ALG → JED | Jul 8, 14:40 UTC | Jul 9, 05:55 UTC | 15h 15m |
| 2026-07-07 | SVA341 | - | Jul 7, 17:50 UTC | Jul 8, 12:00 UTC | 18h 10m |
| 2026-07-07 | SVA704 | JED → KHI | Jul 7, 10:20 UTC | Jul 8, 10:15 UTC | 23h 55m |
| 2026-07-07 | SVA809 | - | Jul 7, 07:50 UTC | Jul 7, 23:55 UTC | 16h 5m |
| 2026-07-07 | SVA808 | - | Jul 7, 03:25 UTC | Jul 7, 05:55 UTC | 2h 30m |
| 2026-07-06 | SVA808 | - | Jul 6, 06:45 UTC | Jul 7, 01:45 UTC | 19h 0m |
| 2026-07-05 | SVA340 | ALG → JED | Jul 5, 14:35 UTC | Jul 6, 08:55 UTC | 18h 20m |
| 2026-07-04 | SVA341 | - | Jul 4, 21:35 UTC | Jul 5, 12:05 UTC | 14h 30m |
| 2026-07-04 | SVA827 | - | Jul 4, 17:55 UTC | Jul 4, 18:10 UTC | 15m |
| 2026-07-03 | SVA803 | - | Jul 3, 21:00 UTC | Jul 4, 15:40 UTC | 18h 40m |
| 2026-07-03 | SVA802 | JED → DAC | Jul 3, 13:55 UTC | Jul 3, 18:50 UTC | 4h 55m |
| 2026-07-02 | SVA802 | JED → DAC | Jul 2, 21:30 UTC | Jul 3, 18:50 UTC | 21h 20m |
| 2026-07-02 | SVA802 | JED → DAC | Jul 2, 18:45 UTC | Jul 3, 18:15 UTC | 23h 30m |
| 2026-07-02 | SVA827 | - | Jul 2, 18:00 UTC | Jul 2, 18:10 UTC | 10m |
| 2026-07-01 | SVA826 | - | Jul 1, 21:05 UTC | Jul 2, 15:45 UTC | 18h 40m |
| 2026-07-01 | SVA802 | JED → DAC | Jul 1, 14:15 UTC | Jul 1, 19:10 UTC | 4h 55m |
| 2026-06-30 | SVA802 | JED → DAC | Jun 30, 23:00 UTC | Jul 1, 19:10 UTC | 20h 10m |
| 2026-06-30 | SVA802 | JED → DAC | Jun 30, 21:00 UTC | Jul 1, 19:10 UTC | 22h 10m |
| 2026-06-30 | SVA802 | JED → DAC | Jun 30, 05:45 UTC | Jun 30, 18:55 UTC | 13h 10m |
| 2026-06-29 | SVA734 | - | Jun 29, 13:34 UTC | Jun 30, 03:00 UTC | 13h 26m |
| 2026-06-29 | SVA732 | - | Jun 29, 08:04 UTC | Jun 29, 11:14 UTC | 3h 10m |
| 2026-06-27 | SVA761 | DEL → RUH | Jun 27, 13:30 UTC | Jun 28, 08:00 UTC | 18h 30m |
| 2026-06-26 | SVA760 | - | Jun 26, 18:49 UTC | Jun 27, 11:39 UTC | 16h 50m |
| 2026-06-26 | SVA3656 | JED → BKK | Jun 26, 02:30 UTC | Jun 26, 16:54 UTC | 14h 25m |
| 2026-06-25 | SVA5916 | - | Jun 25, 21:15 UTC | Jun 26, 00:45 UTC | 3h 30m |
| 2026-06-24 | SVA9661 | - | Jun 24, 14:09 UTC | Jun 24, 15:44 UTC | 1h 35m |
| 2026-06-23 | SVA5910 | - | Jun 23, 20:10 UTC | Jun 24, 11:54 UTC | 15h 45m |
| 2026-06-23 | SVA5960 | - | Jun 23, 14:10 UTC | Jun 23, 17:50 UTC | 3h 40m |
| 2026-06-22 | SVA5960 | - | Jun 22, 18:40 UTC | Jun 23, 17:50 UTC | 23h 10m |
| 2026-06-22 | SVA9693 | - | Jun 22, 17:25 UTC | Jun 23, 15:09 UTC | 21h 45m |
| 2026-06-21 | SVA5956 | - | Jun 21, 21:49 UTC | Jun 22, 12:49 UTC | 15h 0m |
| 2026-06-21 | SVA5738 | - | Jun 21, 00:19 UTC | Jun 21, 19:45 UTC | 19h 25m |
| 2026-06-21 | SVA5738 | - | Jun 21, 00:04 UTC | Jun 21, 19:45 UTC | 19h 40m |
| 2026-06-20 | SVA5700 | - | Jun 20, 05:24 UTC | Jun 21, 00:29 UTC | 19h 5m |
| 2026-06-19 | SVA724 | - | Jun 19, 23:44 UTC | Jun 20, 08:05 UTC | 8h 20m |
| 2026-06-19 | SVA724 | - | Jun 19, 07:49 UTC | Jun 20, 05:29 UTC | 21h 40m |
| 2026-06-19 | SVA724 | - | Jun 19, 05:34 UTC | Jun 20, 00:44 UTC | 19h 10m |
| 2026-06-18 | SVA761 | DEL → RUH | Jun 18, 13:30 UTC | Jun 19, 08:09 UTC | 18h 39m |
| 2026-06-17 | SVA760 | - | Jun 17, 20:55 UTC | Jun 18, 11:45 UTC | 14h 50m |
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-AK17 page for operator, model, and routing details .