sensors Mode-S transponder
710063
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AK23 · BOEING 777-300ER
- Hex
- 710063
- Octal
- 34200143
- Decimal
- 7,405,667
- Country
- SA
- Tail
- HZ-AK23
- Type
- B77W
- Flights observed
- 87
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 14h ago
Last known position
Country allocation
The ICAO 24-bit address 710063 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 | Saudi Arabian Airlines | 8 | 2026-05-11 |
| SVA827 | Saudi Arabian Airlines | 7 | 2026-05-12 |
| SVA9650 | - | 5 | 2026-05-04 |
| SVA818 | Saudi Arabian Airlines | 5 | 2026-05-08 |
| SVA861 | Saudi Arabian Airlines | 4 | 2026-05-24 |
| SVA822 | - | 4 | 2026-04-14 |
| SVA798 | Saudi Arabian Airlines | 4 | 2026-04-22 |
| SVA819 | Saudi Arabian Airlines | 3 | 2026-05-09 |
| SVA808 | Saudi Arabian Airlines | 3 | 2026-04-16 |
| SVA9776 | Saudi Arabian Airlines | 2 | 2026-05-11 |
| SVA9642 | - | 2 | 2026-04-18 |
| SVA9625 | - | 2 | 2026-05-16 |
| SVA862 | Saudi Arabian Airlines | 2 | 2026-05-23 |
| SVA823 | - | 2 | 2026-04-15 |
| SVA700 | Saudi Arabian Airlines | 2 | 2026-04-18 |
| SVA5799 | - | 2 | 2026-04-23 |
| SVA5590 | - | 2 | 2026-05-16 |
| SVA111 | Saudi Arabian Airlines | 2 | 2026-05-29 |
| SVA110 | Saudi Arabian Airlines | 2 | 2026-05-29 |
| SVA9784 | Saudi Arabian Airlines | 1 | 2026-04-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | SVA110 | LHR → RUH | May 29, 09:45 UTC | May 29, 14:05 UTC | 4h 20m |
| 2026-05-29 | SVA111 | RUH → LHR | May 29, 02:00 UTC | May 29, 06:00 UTC | 4h 0m |
| 2026-05-26 | SVA761 | DEL → RUH | May 26, 14:05 UTC | May 26, 15:39 UTC | 1h 35m |
| 2026-05-26 | SVA760 | RUH → DEL | May 26, 08:45 UTC | May 26, 09:04 UTC | 20m |
| 2026-05-24 | SVA861 | MNL → RUH | May 24, 08:15 UTC | May 24, 16:40 UTC | 8h 25m |
| 2026-05-23 | SVA862 | RUH → MNL | May 23, 21:30 UTC | May 24, 06:00 UTC | 8h 30m |
| 2026-05-22 | SVA372 | CMN → JED | May 22, 14:15 UTC | May 22, 18:15 UTC | 4h 0m |
| 2026-05-21 | SVA373 | JED → CMN | May 21, 19:45 UTC | May 22, 11:35 UTC | 15h 49m |
| 2026-05-21 | SVA3814 | - | May 21, 00:40 UTC | May 21, 17:40 UTC | 17h 0m |
| 2026-05-20 | SVA772 | JED → BOM | May 20, 11:15 UTC | May 20, 22:35 UTC | 11h 20m |
| 2026-05-19 | SVA3806 | RUH → DAC | May 19, 21:50 UTC | May 20, 09:10 UTC | 11h 21m |
| 2026-05-17 | SVA5803 | - | May 17, 21:25 UTC | May 18, 00:20 UTC | 2h 55m |
| 2026-05-16 | SVA5590 | - | May 16, 22:50 UTC | May 17, 18:25 UTC | 19h 35m |
| 2026-05-16 | SVA5590 | - | May 16, 22:25 UTC | May 17, 18:25 UTC | 20h 0m |
| 2026-05-16 | SVA9625 | - | May 16, 16:55 UTC | May 16, 20:55 UTC | 4h 0m |
| 2026-05-16 | SVA9625 | - | May 16, 00:00 UTC | May 16, 20:55 UTC | 20h 55m |
| 2026-05-15 | SVA120 | LHR → RUH | May 15, 14:05 UTC | May 16, 00:20 UTC | 10h 14m |
| 2026-05-15 | SVA119 | JED → LHR | May 15, 07:05 UTC | May 15, 11:30 UTC | 4h 25m |
| 2026-05-13 | SVA726 | JED → ISB | May 13, 16:35 UTC | May 13, 22:45 UTC | 6h 10m |
| 2026-05-12 | SVA827 | CGK → JED | May 12, 21:45 UTC | May 13, 16:55 UTC | 19h 10m |
| 2026-05-12 | SVA827 | CGK → JED | May 12, 18:00 UTC | May 13, 16:45 UTC | 22h 45m |
| 2026-05-11 | SVA826 | JED → CGK | May 11, 21:50 UTC | May 12, 15:55 UTC | 18h 5m |
| 2026-05-11 | SVA9776 | CAI → JED | May 11, 15:50 UTC | May 11, 19:30 UTC | 3h 41m |
| 2026-05-10 | SVA9776 | CAI → JED | May 10, 21:54 UTC | May 11, 19:30 UTC | 21h 36m |
| 2026-05-10 | SVA827 | CGK → JED | May 10, 19:00 UTC | May 11, 16:10 UTC | 21h 10m |
| 2026-05-10 | SVA827 | CGK → JED | May 10, 18:05 UTC | May 11, 16:10 UTC | 22h 5m |
| 2026-05-10 | SVA826 | JED → CGK | May 10, 07:55 UTC | May 10, 16:04 UTC | 8h 10m |
| 2026-05-09 | SVA826 | JED → CGK | May 9, 14:50 UTC | May 10, 14:45 UTC | 23h 55m |
| 2026-05-09 | SVA826 | JED → CGK | May 9, 14:40 UTC | May 10, 11:45 UTC | 21h 5m |
| 2026-05-09 | SVA819 | CGK → JED | May 9, 10:50 UTC | May 10, 08:15 UTC | 21h 25m |
| 2026-05-08 | SVA818 | JED → CGK | May 8, 15:00 UTC | May 9, 08:10 UTC | 17h 10m |
| 2026-05-08 | SVA9734 | - | May 8, 11:40 UTC | May 8, 12:44 UTC | 1h 5m |
| 2026-05-07 | SVA5588 | - | May 7, 00:30 UTC | May 7, 03:15 UTC | 2h 45m |
| 2026-05-06 | SVA9623 | - | May 6, 17:30 UTC | May 6, 22:45 UTC | 5h 14m |
| 2026-05-05 | SVA3051 | BOM → JED | May 5, 03:00 UTC | May 5, 03:35 UTC | 35m |
| 2026-05-04 | SVA9650 | - | May 4, 07:20 UTC | May 5, 01:00 UTC | 17h 41m |
| 2026-05-04 | SVA9650 | - | May 4, 00:50 UTC | May 5, 00:45 UTC | 23h 56m |
| 2026-05-03 | SVA724 | RUH → ISB | May 3, 23:50 UTC | May 4, 22:30 UTC | 22h 41m |
| 2026-05-03 | SVA861 | MNL → RUH | May 3, 12:50 UTC | May 4, 08:15 UTC | 19h 25m |
| 2026-05-03 | SVA861 | MNL → RUH | May 3, 12:40 UTC | May 4, 08:15 UTC | 19h 35m |
| 2026-05-03 | SVA861 | MNL → RUH | May 3, 08:10 UTC | May 3, 11:35 UTC | 3h 25m |
| 2026-05-02 | SVA862 | RUH → MNL | May 2, 10:50 UTC | May 3, 05:15 UTC | 18h 24m |
| 2026-05-02 | SVA110 | LHR → RUH | May 2, 09:35 UTC | May 3, 05:15 UTC | 19h 39m |
| 2026-05-01 | SVA111 | RUH → LHR | May 1, 16:00 UTC | May 2, 06:30 UTC | 14h 30m |
| 2026-05-01 | SVA121 | RUH → LHR | May 1, 03:35 UTC | May 1, 12:40 UTC | 9h 5m |
| 2026-05-01 | SVA741 | BOM → RUH | May 1, 01:00 UTC | May 1, 01:10 UTC | 10m |
| 2026-04-30 | SVA740 | RUH → BOM | Apr 30, 19:25 UTC | Apr 30, 22:40 UTC | 3h 15m |
| 2026-04-25 | SVA5913 | - | Apr 25, 12:10 UTC | Apr 25, 15:50 UTC | 3h 40m |
| 2026-04-25 | SVA9650 | - | Apr 25, 06:50 UTC | Apr 25, 10:25 UTC | 3h 35m |
| 2026-04-23 | SVA5799 | - | Apr 23, 09:30 UTC | Apr 23, 14:30 UTC | 5h 0m |
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-AK23 page for operator, model, and routing details .