sensors Mode-S transponder
710064
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AK24 · BOEING 777-300ER
- Hex
- 710064
- Octal
- 34200144
- Decimal
- 7,405,668
- Country
- SA
- Tail
- HZ-AK24
- Type
- B77W
- Flights observed
- 189
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 710064 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 |
|---|---|---|---|
| SVA862 | - | 17 | 2026-07-13 |
| SVA804 | Saudi Arabian Airlines | 17 | 2026-07-09 |
| SVA121 | - | 10 | 2026-06-18 |
| SVA861 | - | 7 | 2026-07-05 |
| SVA800 | Saudi Arabian Airlines | 7 | 2026-05-27 |
| SVA110 | - | 7 | 2026-06-19 |
| SVA111 | - | 6 | 2026-06-28 |
| SVA827 | - | 5 | 2026-06-24 |
| SVA826 | - | 5 | 2026-06-23 |
| SVA818 | - | 5 | 2026-06-16 |
| SVA805 | - | 5 | 2026-07-02 |
| SVA724 | - | 5 | 2026-07-09 |
| SVA143 | - | 5 | 2026-07-08 |
| SVA373 | Saudi Arabian Airlines | 4 | 2026-05-23 |
| SVA828 | - | 3 | 2026-07-06 |
| SVA819 | - | 3 | 2026-06-17 |
| SVA801 | Saudi Arabian Airlines | 3 | 2026-06-06 |
| SVA770 | Saudi Arabian Airlines | 3 | 2026-04-23 |
| SVA741 | Saudi Arabian Airlines | 3 | 2026-04-29 |
| SVA740 | Saudi Arabian Airlines | 3 | 2026-04-29 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | SVA862 | - | Jul 13, 20:30 UTC | Jul 14, 05:00 UTC | 8h 30m |
| 2026-07-11 | SVA114 | - | Jul 11, 16:25 UTC | Jul 11, 20:40 UTC | 4h 15m |
| 2026-07-10 | SVA115 | - | Jul 10, 19:05 UTC | Jul 11, 13:05 UTC | 18h 0m |
| 2026-07-09 | SVA804 | JED → DAC | Jul 9, 23:45 UTC | Jul 10, 16:55 UTC | 17h 10m |
| 2026-07-09 | SVA724 | - | Jul 9, 13:05 UTC | Jul 10, 13:00 UTC | 23h 55m |
| 2026-07-09 | SVA144 | - | Jul 9, 11:05 UTC | Jul 10, 08:15 UTC | 21h 10m |
| 2026-07-09 | SVA144 | - | Jul 9, 10:10 UTC | Jul 10, 08:15 UTC | 22h 5m |
| 2026-07-08 | SVA143 | - | Jul 8, 11:05 UTC | Jul 9, 05:15 UTC | 18h 10m |
| 2026-07-08 | SVA143 | - | Jul 8, 10:00 UTC | Jul 9, 05:15 UTC | 19h 15m |
| 2026-07-08 | SVA143 | - | Jul 8, 07:55 UTC | Jul 9, 05:15 UTC | 21h 20m |
| 2026-07-07 | SVA862 | - | Jul 7, 11:05 UTC | Jul 8, 05:45 UTC | 18h 40m |
| 2026-07-07 | SVA862 | - | Jul 7, 09:20 UTC | Jul 8, 05:45 UTC | 20h 25m |
| 2026-07-07 | SVA862 | - | Jul 7, 08:15 UTC | Jul 8, 05:45 UTC | 21h 30m |
| 2026-07-07 | SVA862 | - | Jul 7, 05:15 UTC | Jul 8, 03:20 UTC | 22h 5m |
| 2026-07-06 | SVA828 | - | Jul 6, 08:20 UTC | Jul 7, 03:00 UTC | 18h 40m |
| 2026-07-06 | SVA828 | - | Jul 6, 05:25 UTC | Jul 7, 03:00 UTC | 21h 35m |
| 2026-07-05 | SVA828 | - | Jul 5, 22:50 UTC | Jul 6, 03:45 UTC | 4h 55m |
| 2026-07-05 | SVA861 | - | Jul 5, 08:00 UTC | Jul 5, 21:15 UTC | 13h 15m |
| 2026-07-04 | SVA862 | - | Jul 4, 20:50 UTC | Jul 5, 06:00 UTC | 9h 10m |
| 2026-07-03 | SVA737 | - | Jul 3, 21:15 UTC | Jul 4, 00:30 UTC | 3h 15m |
| 2026-07-03 | SVA736 | - | Jul 3, 18:35 UTC | Jul 3, 18:45 UTC | 10m |
| 2026-07-03 | SVA736 | - | Jul 3, 12:30 UTC | Jul 3, 17:05 UTC | 4h 35m |
| 2026-07-02 | SVA558 | - | Jul 2, 23:30 UTC | Jul 3, 10:35 UTC | 11h 5m |
| 2026-07-02 | SVA805 | - | Jul 2, 19:45 UTC | Jul 2, 20:35 UTC | 50m |
| 2026-07-01 | SVA804 | JED → DAC | Jul 1, 23:10 UTC | Jul 2, 17:20 UTC | 18h 10m |
| 2026-07-01 | SVA804 | JED → DAC | Jul 1, 21:05 UTC | Jul 2, 17:20 UTC | 20h 15m |
| 2026-07-01 | SVA804 | JED → DAC | Jul 1, 19:05 UTC | Jul 2, 17:20 UTC | 22h 15m |
| 2026-06-30 | SVA804 | JED → DAC | Jun 30, 23:05 UTC | Jul 1, 17:25 UTC | 18h 20m |
| 2026-06-30 | SVA804 | JED → DAC | Jun 30, 21:05 UTC | Jul 1, 17:25 UTC | 20h 20m |
| 2026-06-30 | SVA804 | JED → DAC | Jun 30, 19:10 UTC | Jul 1, 17:25 UTC | 22h 15m |
| 2026-06-29 | SVA804 | JED → DAC | Jun 29, 23:25 UTC | Jun 30, 17:15 UTC | 17h 51m |
| 2026-06-29 | SVA724 | - | Jun 29, 15:30 UTC | Jun 30, 13:00 UTC | 21h 31m |
| 2026-06-29 | SVA861 | - | Jun 29, 07:59 UTC | Jun 29, 14:29 UTC | 6h 30m |
| 2026-06-28 | SVA862 | - | Jun 28, 11:04 UTC | Jun 29, 06:05 UTC | 19h 0m |
| 2026-06-28 | SVA862 | - | Jun 28, 09:34 UTC | Jun 29, 06:05 UTC | 20h 30m |
| 2026-06-28 | SVA111 | - | Jun 28, 01:04 UTC | Jun 28, 05:49 UTC | 4h 45m |
| 2026-06-26 | SVA805 | - | Jun 26, 19:20 UTC | Jun 26, 23:55 UTC | 4h 35m |
| 2026-06-26 | SVA804 | JED → DAC | Jun 26, 00:30 UTC | Jun 26, 17:35 UTC | 17h 5m |
| 2026-06-25 | SVA804 | JED → DAC | Jun 25, 22:39 UTC | Jun 26, 17:35 UTC | 18h 55m |
| 2026-06-25 | SVA804 | JED → DAC | Jun 25, 17:05 UTC | Jun 26, 17:00 UTC | 23h 55m |
| 2026-06-25 | SVA804 | JED → DAC | Jun 25, 16:24 UTC | Jun 26, 14:59 UTC | 22h 35m |
| 2026-06-24 | SVA5726 | - | Jun 24, 21:29 UTC | Jun 25, 17:25 UTC | 19h 55m |
| 2026-06-24 | SVA827 | - | Jun 24, 17:55 UTC | Jun 24, 18:09 UTC | 15m |
| 2026-06-23 | SVA826 | - | Jun 23, 21:29 UTC | Jun 24, 14:55 UTC | 17h 25m |
| 2026-06-23 | SVA826 | - | Jun 23, 18:39 UTC | Jun 24, 14:55 UTC | 20h 15m |
| 2026-06-23 | SVA827 | - | Jun 23, 17:54 UTC | Jun 23, 18:04 UTC | 10m |
| 2026-06-23 | SVA826 | - | Jun 23, 07:25 UTC | Jun 23, 15:24 UTC | 8h 0m |
| 2026-06-21 | SVA5726 | - | Jun 21, 05:40 UTC | Jun 21, 23:55 UTC | 18h 15m |
| 2026-06-21 | SVA734 | - | Jun 21, 00:45 UTC | Jun 21, 03:30 UTC | 2h 45m |
| 2026-06-19 | SVA110 | - | Jun 19, 09:49 UTC | Jun 19, 13:44 UTC | 3h 55m |
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-AK24 page for operator, model, and routing details .