sensors Mode-S transponder
710055
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AK13 · BOEING 777-300ER
- Hex
- 710055
- Octal
- 34200125
- Decimal
- 7,405,653
- Country
- SA
- Tail
- HZ-AK13
- Type
- B77W
- Flights observed
- 170
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 10h ago
Last known position
Country allocation
The ICAO 24-bit address 710055 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 |
|---|---|---|---|
| SVA818 | - | 11 | 2026-06-30 |
| SVA804 | Saudi Arabian Airlines | 8 | 2026-07-12 |
| SVA861 | - | 7 | 2026-07-06 |
| SVA803 | - | 7 | 2026-06-27 |
| SVA800 | - | 7 | 2026-06-30 |
| SVA760 | Saudi Arabian Airlines | 6 | 2026-05-01 |
| SVA724 | - | 6 | 2026-07-11 |
| SVA805 | - | 5 | 2026-07-12 |
| SVA802 | Saudi Arabian Airlines | 5 | 2026-05-27 |
| SVA738 | Saudi Arabian Airlines | 4 | 2026-05-21 |
| SVA5802 | - | 4 | 2026-06-26 |
| SVA862 | - | 3 | 2026-07-05 |
| SVA826 | - | 3 | 2026-07-09 |
| SVA819 | - | 3 | 2026-07-01 |
| SVA810 | Saudi Arabian Airlines | 3 | 2026-04-27 |
| SVA809 | Saudi Arabian Airlines | 3 | 2026-04-13 |
| SVA808 | Saudi Arabian Airlines | 3 | 2026-05-11 |
| SVA761 | Saudi Arabian Airlines | 3 | 2026-06-13 |
| SVA735 | - | 3 | 2026-06-29 |
| SVA568 | Saudi Arabian Airlines | 3 | 2026-05-23 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | SVA743 | LHE → RUH | Jul 13, 16:40 UTC | Jul 13, 19:50 UTC | 3h 10m |
| 2026-07-12 | SVA805 | - | Jul 12, 19:20 UTC | Jul 13, 13:55 UTC | 18h 35m |
| 2026-07-12 | SVA804 | JED → DAC | Jul 12, 14:10 UTC | Jul 12, 17:15 UTC | 3h 5m |
| 2026-07-11 | SVA724 | - | Jul 11, 23:40 UTC | Jul 12, 13:15 UTC | 13h 35m |
| 2026-07-11 | SVA724 | - | Jul 11, 08:15 UTC | Jul 12, 05:45 UTC | 21h 30m |
| 2026-07-11 | SVA724 | - | Jul 11, 06:05 UTC | Jul 12, 00:50 UTC | 18h 45m |
| 2026-07-10 | SVA372 | CMN → JED | Jul 10, 14:35 UTC | Jul 11, 03:40 UTC | 13h 5m |
| 2026-07-09 | SVA373 | - | Jul 9, 18:00 UTC | Jul 10, 11:25 UTC | 17h 25m |
| 2026-07-09 | SVA826 | - | Jul 9, 07:25 UTC | Jul 9, 15:35 UTC | 8h 10m |
| 2026-07-08 | SVA700 | - | Jul 8, 00:00 UTC | Jul 8, 05:55 UTC | 5h 55m |
| 2026-07-06 | SVA861 | - | Jul 6, 08:05 UTC | Jul 6, 16:25 UTC | 8h 20m |
| 2026-07-05 | SVA862 | - | Jul 5, 20:50 UTC | Jul 6, 05:45 UTC | 8h 55m |
| 2026-07-04 | SVA114 | - | Jul 4, 16:40 UTC | Jul 4, 20:50 UTC | 4h 10m |
| 2026-07-03 | SVA115 | DAC → LHR | Jul 3, 19:35 UTC | Jul 4, 13:15 UTC | 17h 40m |
| 2026-07-02 | SVA804 | JED → DAC | Jul 2, 23:30 UTC | Jul 3, 17:25 UTC | 17h 55m |
| 2026-07-02 | SVA804 | JED → DAC | Jul 2, 19:20 UTC | Jul 3, 17:25 UTC | 22h 5m |
| 2026-07-02 | SVA804 | JED → DAC | Jul 2, 18:40 UTC | Jul 3, 17:15 UTC | 22h 35m |
| 2026-07-02 | SVA724 | - | Jul 2, 16:30 UTC | Jul 3, 13:35 UTC | 21h 5m |
| 2026-07-02 | SVA736 | - | Jul 2, 11:10 UTC | Jul 2, 13:55 UTC | 2h 45m |
| 2026-07-01 | SVA736 | - | Jul 1, 14:30 UTC | Jul 2, 12:05 UTC | 21h 35m |
| 2026-07-01 | SVA819 | - | Jul 1, 10:50 UTC | Jul 1, 11:05 UTC | 15m |
| 2026-06-30 | SVA818 | - | Jun 30, 13:45 UTC | Jul 1, 08:50 UTC | 19h 5m |
| 2026-06-30 | SVA800 | - | Jun 30, 09:40 UTC | Jun 30, 09:55 UTC | 15m |
| 2026-06-30 | SVA800 | - | Jun 30, 07:05 UTC | Jun 30, 08:00 UTC | 55m |
| 2026-06-29 | SVA735 | - | Jun 29, 07:55 UTC | Jun 30, 07:15 UTC | 23h 21m |
| 2026-06-29 | SVA735 | - | Jun 29, 05:45 UTC | Jun 29, 08:14 UTC | 2h 30m |
| 2026-06-28 | SVA340 | ALG → JED | Jun 28, 15:24 UTC | Jun 29, 01:39 UTC | 10h 15m |
| 2026-06-28 | SVA340 | ALG → JED | Jun 28, 14:39 UTC | Jun 28, 14:50 UTC | 10m |
| 2026-06-27 | SVA803 | - | Jun 27, 21:15 UTC | Jun 28, 11:19 UTC | 14h 5m |
| 2026-06-26 | SVA5802 | - | Jun 26, 23:30 UTC | Jun 27, 18:09 UTC | 18h 40m |
| 2026-06-26 | SVA5700 | - | Jun 26, 15:25 UTC | Jun 27, 15:14 UTC | 23h 50m |
| 2026-06-26 | SVA5700 | - | Jun 26, 13:10 UTC | Jun 27, 05:59 UTC | 16h 50m |
| 2026-06-25 | SVA732 | - | Jun 25, 17:54 UTC | Jun 26, 11:05 UTC | 17h 10m |
| 2026-06-24 | SVA826 | - | Jun 24, 21:19 UTC | Jun 25, 15:24 UTC | 18h 5m |
| 2026-06-24 | SVA826 | - | Jun 24, 21:09 UTC | Jun 25, 15:24 UTC | 18h 15m |
| 2026-06-24 | SVA5938 | - | Jun 24, 07:34 UTC | Jun 24, 19:04 UTC | 11h 30m |
| 2026-06-24 | SVA5936 | - | Jun 24, 02:15 UTC | Jun 24, 05:40 UTC | 3h 25m |
| 2026-06-22 | SVA9653 | - | Jun 22, 08:25 UTC | Jun 22, 23:50 UTC | 15h 25m |
| 2026-06-21 | SVA5902 | - | Jun 21, 11:20 UTC | Jun 22, 06:45 UTC | 19h 25m |
| 2026-06-21 | SVA5902 | - | Jun 21, 11:00 UTC | Jun 22, 06:45 UTC | 19h 45m |
| 2026-06-21 | SVA818 | - | Jun 21, 08:30 UTC | Jun 21, 08:49 UTC | 20m |
| 2026-06-21 | SVA818 | - | Jun 21, 00:40 UTC | Jun 21, 07:59 UTC | 7h 20m |
| 2026-06-20 | SVA818 | - | Jun 20, 10:44 UTC | Jun 21, 07:59 UTC | 21h 15m |
| 2026-06-20 | SVA807 | - | Jun 20, 07:19 UTC | Jun 21, 07:14 UTC | 23h 55m |
| 2026-06-20 | SVA807 | - | Jun 20, 06:24 UTC | Jun 21, 04:14 UTC | 21h 50m |
| 2026-06-19 | SVA806 | - | Jun 19, 22:39 UTC | Jun 20, 03:34 UTC | 4h 55m |
| 2026-06-18 | SVA735 | - | Jun 18, 05:40 UTC | Jun 18, 06:05 UTC | 25m |
| 2026-06-18 | SVA5734 | - | Jun 18, 00:20 UTC | Jun 18, 03:00 UTC | 2h 40m |
| 2026-06-16 | SVA805 | - | Jun 16, 19:00 UTC | Jun 16, 23:45 UTC | 4h 46m |
| 2026-06-15 | SVA804 | JED → DAC | Jun 15, 23:54 UTC | Jun 16, 17:10 UTC | 17h 15m |
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-AK13 page for operator, model, and routing details .