sensors Mode-S transponder
710060
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AK21 · BOEING 777-300ER
- Hex
- 710060
- Octal
- 34200140
- Decimal
- 7,405,664
- Country
- SA
- Tail
- HZ-AK21
- Type
- B77W
- Flights observed
- 193
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 710060 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 | 32 | 2026-06-09 |
| SVA827 | Saudi Arabian Airlines | 17 | 2026-06-04 |
| SVA802 | Saudi Arabian Airlines | 12 | 2026-06-24 |
| SVA818 | - | 8 | 2026-07-07 |
| SVA803 | - | 7 | 2026-06-26 |
| SVA734 | - | 7 | 2026-07-08 |
| SVA704 | Saudi Arabian Airlines | 7 | 2026-05-17 |
| SVA808 | - | 5 | 2026-07-10 |
| SVA341 | Saudi Arabian Airlines | 5 | 2026-05-16 |
| SVA736 | - | 4 | 2026-07-17 |
| SVA5801 | Saudi Arabian Airlines | 4 | 2026-04-26 |
| SVA5559 | - | 4 | 2026-06-16 |
| SVA862 | - | 3 | 2026-07-12 |
| SVA819 | - | 3 | 2026-07-07 |
| SVA809 | - | 3 | 2026-07-10 |
| SVA801 | Saudi Arabian Airlines | 3 | 2026-07-02 |
| SVA800 | - | 3 | 2026-07-05 |
| SVA758 | Saudi Arabian Airlines | 3 | 2026-07-03 |
| SVA5800 | - | 3 | 2026-06-11 |
| SVA5705 | - | 3 | 2026-04-30 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | SVA806 | - | Jul 17, 16:29 UTC | Jul 18, 01:34 UTC | 9h 5m |
| 2026-07-17 | SVA736 | - | Jul 17, 11:25 UTC | Jul 17, 14:10 UTC | 2h 45m |
| 2026-07-16 | SVA736 | - | Jul 16, 18:29 UTC | Jul 17, 14:10 UTC | 19h 40m |
| 2026-07-16 | SVA736 | - | Jul 16, 16:25 UTC | Jul 17, 14:10 UTC | 21h 45m |
| 2026-07-16 | SVA736 | - | Jul 16, 11:25 UTC | Jul 16, 14:10 UTC | 2h 45m |
| 2026-07-15 | SVA807 | - | Jul 15, 06:40 UTC | Jul 15, 11:10 UTC | 4h 30m |
| 2026-07-14 | SVA806 | - | Jul 14, 23:10 UTC | Jul 15, 04:25 UTC | 5h 15m |
| 2026-07-13 | SVA861 | - | Jul 13, 08:15 UTC | Jul 13, 16:25 UTC | 8h 10m |
| 2026-07-12 | SVA862 | - | Jul 12, 20:45 UTC | Jul 13, 05:55 UTC | 9h 10m |
| 2026-07-11 | SVA351 | JED → ALG | Jul 11, 06:40 UTC | Jul 11, 15:20 UTC | 8h 40m |
| 2026-07-10 | SVA351 | JED → ALG | Jul 10, 10:25 UTC | Jul 11, 08:40 UTC | 22h 15m |
| 2026-07-10 | SVA809 | - | Jul 10, 08:30 UTC | Jul 11, 08:01 UTC | 23h 30m |
| 2026-07-10 | SVA808 | - | Jul 10, 01:40 UTC | Jul 10, 06:25 UTC | 4h 45m |
| 2026-07-09 | SVA808 | - | Jul 9, 06:05 UTC | Jul 10, 01:35 UTC | 19h 30m |
| 2026-07-09 | SVA808 | - | Jul 9, 05:45 UTC | Jul 10, 01:35 UTC | 19h 50m |
| 2026-07-08 | SVA734 | - | Jul 8, 08:05 UTC | Jul 9, 03:20 UTC | 19h 15m |
| 2026-07-08 | SVA734 | - | Jul 8, 06:10 UTC | Jul 9, 03:20 UTC | 21h 10m |
| 2026-07-08 | SVA734 | - | Jul 8, 05:50 UTC | Jul 9, 03:20 UTC | 21h 30m |
| 2026-07-07 | SVA734 | - | Jul 7, 14:20 UTC | Jul 8, 03:30 UTC | 13h 10m |
| 2026-07-07 | SVA819 | - | Jul 7, 10:45 UTC | Jul 7, 10:55 UTC | 10m |
| 2026-07-07 | SVA818 | - | Jul 7, 08:30 UTC | Jul 7, 08:50 UTC | 20m |
| 2026-07-07 | SVA818 | - | Jul 7, 00:35 UTC | Jul 7, 08:00 UTC | 7h 25m |
| 2026-07-06 | SVA818 | - | Jul 6, 09:05 UTC | Jul 7, 08:00 UTC | 22h 55m |
| 2026-07-06 | SVA757 | - | Jul 6, 06:45 UTC | Jul 7, 04:05 UTC | 21h 20m |
| 2026-07-05 | SVA756 | - | Jul 5, 13:40 UTC | Jul 6, 04:35 UTC | 14h 55m |
| 2026-07-05 | SVA800 | - | Jul 5, 09:40 UTC | Jul 5, 09:55 UTC | 15m |
| 2026-07-04 | SVA800 | - | Jul 4, 15:05 UTC | Jul 5, 08:00 UTC | 16h 55m |
| 2026-07-03 | SVA758 | JED → DEL | Jul 3, 22:50 UTC | Jul 4, 13:05 UTC | 14h 15m |
| 2026-07-03 | SVA758 | JED → DEL | Jul 3, 16:50 UTC | Jul 4, 13:05 UTC | 20h 15m |
| 2026-07-03 | SVA726 | JED → ISB | Jul 3, 06:50 UTC | Jul 4, 01:00 UTC | 18h 10m |
| 2026-07-03 | SVA726 | JED → ISB | Jul 3, 02:05 UTC | Jul 4, 01:00 UTC | 22h 55m |
| 2026-07-03 | SVA722 | - | Jul 3, 01:10 UTC | Jul 3, 22:50 UTC | 21h 40m |
| 2026-07-02 | SVA722 | - | Jul 2, 14:05 UTC | Jul 3, 09:00 UTC | 18h 55m |
| 2026-07-02 | SVA801 | DAC → RUH | Jul 2, 12:05 UTC | Jul 2, 12:15 UTC | 10m |
| 2026-07-01 | SVA773 | BOM → JED | Jul 1, 21:15 UTC | Jul 1, 23:15 UTC | 2h 0m |
| 2026-07-01 | SVA772 | JED → BOM | Jul 1, 00:55 UTC | Jul 1, 19:00 UTC | 18h 5m |
| 2026-06-30 | SVA700 | - | Jun 30, 14:45 UTC | Jul 1, 06:20 UTC | 15h 35m |
| 2026-06-30 | SVA818 | - | Jun 30, 00:55 UTC | Jun 30, 09:15 UTC | 8h 21m |
| 2026-06-28 | SVA9649 | - | Jun 28, 22:49 UTC | Jun 29, 01:00 UTC | 2h 10m |
| 2026-06-28 | SVA5954 | - | Jun 28, 05:45 UTC | Jun 28, 20:59 UTC | 15h 15m |
| 2026-06-28 | SVA734 | - | Jun 28, 00:35 UTC | Jun 28, 03:19 UTC | 2h 45m |
| 2026-06-26 | SVA803 | - | Jun 26, 21:15 UTC | Jun 27, 01:15 UTC | 4h 0m |
| 2026-06-26 | SVA5802 | - | Jun 26, 14:39 UTC | Jun 26, 19:24 UTC | 4h 45m |
| 2026-06-24 | SVA803 | - | Jun 24, 20:44 UTC | Jun 25, 00:59 UTC | 4h 15m |
| 2026-06-24 | SVA802 | JED → DAC | Jun 24, 14:04 UTC | Jun 24, 18:44 UTC | 4h 40m |
| 2026-06-24 | SVA735 | - | Jun 24, 05:44 UTC | Jun 24, 08:14 UTC | 2h 30m |
| 2026-06-24 | SVA734 | - | Jun 24, 00:34 UTC | Jun 24, 03:19 UTC | 2h 45m |
| 2026-06-23 | SVA734 | - | Jun 23, 05:29 UTC | Jun 24, 03:19 UTC | 21h 50m |
| 2026-06-22 | SVA5700 | - | Jun 22, 13:44 UTC | Jun 23, 05:45 UTC | 16h 0m |
| 2026-06-21 | SVA5704 | - | Jun 21, 17:39 UTC | Jun 22, 07:45 UTC | 14h 5m |
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-AK21 page for operator, model, and routing details .