sensors Mode-S transponder
710053
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AK11 · BOEING 777-300ER
- Hex
- 710053
- Octal
- 34200123
- Decimal
- 7,405,651
- Country
- SA
- Tail
- HZ-AK11
- Type
- B77W
- Flights observed
- 156
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 710053 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 |
|---|---|---|---|
| SVA804 | Saudi Arabian Airlines | 7 | 2026-07-03 |
| SVA9327 | - | 5 | 2026-04-24 |
| SVA9695 | - | 4 | 2026-06-21 |
| SVA9517 | - | 4 | 2026-06-06 |
| SVA818 | Saudi Arabian Airlines | 4 | 2026-06-10 |
| SVA808 | Saudi Arabian Airlines | 4 | 2026-05-26 |
| SVA726 | Saudi Arabian Airlines | 4 | 2026-07-14 |
| SVA341 | Saudi Arabian Airlines | 4 | 2026-04-19 |
| SVA9445 | - | 3 | 2026-05-05 |
| SVA9396 | - | 3 | 2026-05-02 |
| SVA9328 | - | 3 | 2026-04-26 |
| SVA9322 | - | 3 | 2026-05-20 |
| SVA805 | - | 3 | 2026-07-04 |
| SVA802 | Saudi Arabian Airlines | 3 | 2026-05-14 |
| SVA770 | Saudi Arabian Airlines | 3 | 2026-05-21 |
| SVA736 | - | 3 | 2026-06-24 |
| SVA5434 | - | 3 | 2026-06-11 |
| SVA5256 | - | 3 | 2026-06-05 |
| SVA340 | Saudi Arabian Airlines | 3 | 2026-05-31 |
| SVA9524 | - | 2 | 2026-05-15 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | SVA726 | JED → ISB | Jul 14, 05:45 UTC | Jul 14, 17:50 UTC | 12h 5m |
| 2026-07-13 | SVA759 | DEL → JED | Jul 13, 15:00 UTC | Jul 14, 03:25 UTC | 12h 25m |
| 2026-07-12 | SVA338 | - | Jul 12, 19:10 UTC | Jul 13, 13:00 UTC | 17h 50m |
| 2026-07-12 | SVA9639 | JED → CAI | Jul 12, 12:45 UTC | Jul 12, 16:35 UTC | 3h 50m |
| 2026-07-08 | SVA871D | - | Jul 8, 21:20 UTC | Jul 9, 04:50 UTC | 7h 30m |
| 2026-07-08 | SVA870 | - | Jul 8, 03:35 UTC | Jul 8, 12:40 UTC | 9h 5m |
| 2026-07-06 | SVA827 | - | Jul 6, 17:55 UTC | Jul 6, 22:05 UTC | 4h 10m |
| 2026-07-06 | SVA826 | - | Jul 6, 07:15 UTC | Jul 6, 15:25 UTC | 8h 10m |
| 2026-07-04 | SVA805 | - | Jul 4, 19:05 UTC | Jul 4, 23:50 UTC | 4h 45m |
| 2026-07-03 | SVA804 | JED → DAC | Jul 3, 23:30 UTC | Jul 4, 16:55 UTC | 17h 25m |
| 2026-07-03 | SVA724 | - | Jul 3, 01:15 UTC | Jul 4, 00:35 UTC | 23h 20m |
| 2026-07-02 | SVA726 | JED → ISB | Jul 2, 06:51 UTC | Jul 3, 02:20 UTC | 19h 29m |
| 2026-07-02 | SVA726 | JED → ISB | Jul 2, 06:35 UTC | Jul 3, 02:20 UTC | 19h 45m |
| 2026-07-02 | SVA817 | - | Jul 2, 03:00 UTC | Jul 3, 02:20 UTC | 23h 20m |
| 2026-07-01 | SVA816 | - | Jul 1, 17:05 UTC | Jul 2, 00:35 UTC | 7h 30m |
| 2026-06-29 | SVA807 | - | Jun 29, 05:40 UTC | Jun 29, 10:15 UTC | 4h 35m |
| 2026-06-28 | SVA806 | - | Jun 28, 22:49 UTC | Jun 29, 03:49 UTC | 5h 0m |
| 2026-06-25 | SVA724 | - | Jun 25, 16:20 UTC | Jun 26, 08:20 UTC | 16h 0m |
| 2026-06-24 | SVA736 | - | Jun 24, 18:50 UTC | Jun 25, 13:59 UTC | 19h 10m |
| 2026-06-24 | SVA736 | - | Jun 24, 18:34 UTC | Jun 25, 13:59 UTC | 19h 25m |
| 2026-06-22 | SVA805 | - | Jun 22, 19:05 UTC | Jun 22, 23:45 UTC | 4h 40m |
| 2026-06-21 | SVA804 | JED → DAC | Jun 21, 23:40 UTC | Jun 22, 16:45 UTC | 17h 5m |
| 2026-06-21 | SVA804 | JED → DAC | Jun 21, 17:35 UTC | Jun 22, 16:45 UTC | 23h 10m |
| 2026-06-21 | SVA804 | JED → DAC | Jun 21, 14:50 UTC | Jun 22, 14:45 UTC | 23h 55m |
| 2026-06-21 | SVA9695 | - | Jun 21, 14:30 UTC | Jun 22, 12:30 UTC | 22h 0m |
| 2026-06-21 | SVA9695 | - | Jun 21, 10:49 UTC | Jun 22, 08:19 UTC | 21h 30m |
| 2026-06-21 | SVA9695 | - | Jun 21, 08:49 UTC | Jun 22, 08:19 UTC | 23h 30m |
| 2026-06-21 | SVA9695 | - | Jun 21, 08:30 UTC | Jun 22, 05:44 UTC | 21h 15m |
| 2026-06-20 | SVA5952 | - | Jun 20, 18:10 UTC | Jun 21, 15:54 UTC | 21h 45m |
| 2026-06-20 | SVA826 | - | Jun 20, 09:59 UTC | Jun 20, 15:49 UTC | 5h 50m |
| 2026-06-18 | SVA801 | DAC → RUH | Jun 18, 15:25 UTC | Jun 18, 15:30 UTC | 5m |
| 2026-06-18 | SVA800 | - | Jun 18, 12:50 UTC | Jun 18, 13:55 UTC | 1h 5m |
| 2026-06-18 | SVA800 | - | Jun 18, 10:10 UTC | Jun 18, 10:45 UTC | 35m |
| 2026-06-17 | SVA9679 | - | Jun 17, 01:35 UTC | Jun 17, 02:05 UTC | 30m |
| 2026-06-16 | SVA5710 | - | Jun 16, 20:10 UTC | Jun 16, 23:30 UTC | 3h 20m |
| 2026-06-16 | SVA5710 | - | Jun 16, 00:10 UTC | Jun 16, 20:35 UTC | 20h 26m |
| 2026-06-15 | SVA801 | DAC → RUH | Jun 15, 11:54 UTC | Jun 15, 12:05 UTC | 10m |
| 2026-06-15 | SVA5800 | - | Jun 15, 09:35 UTC | Jun 15, 09:49 UTC | 15m |
| 2026-06-14 | SVA9747 | - | Jun 14, 21:40 UTC | Jun 15, 07:50 UTC | 10h 10m |
| 2026-06-14 | SVA5954 | - | Jun 14, 17:05 UTC | Jun 14, 20:10 UTC | 3h 5m |
| 2026-06-13 | SVA5954 | - | Jun 13, 23:30 UTC | Jun 14, 20:10 UTC | 20h 40m |
| 2026-06-13 | SVA805 | - | Jun 13, 19:00 UTC | Jun 14, 17:25 UTC | 22h 25m |
| 2026-06-13 | SVA804 | JED → DAC | Jun 13, 16:40 UTC | Jun 13, 17:00 UTC | 20m |
| 2026-06-13 | SVA804 | JED → DAC | Jun 13, 12:10 UTC | Jun 13, 15:55 UTC | 3h 45m |
| 2026-06-12 | SVA804 | JED → DAC | Jun 12, 17:15 UTC | Jun 13, 15:55 UTC | 22h 39m |
| 2026-06-12 | SVA9480 | - | Jun 12, 16:10 UTC | Jun 13, 14:45 UTC | 22h 34m |
| 2026-06-12 | SVA9480 | - | Jun 12, 12:05 UTC | Jun 12, 17:25 UTC | 5h 20m |
| 2026-06-11 | SVA5434 | - | Jun 11, 14:50 UTC | Jun 12, 10:00 UTC | 19h 11m |
| 2026-06-11 | SVA5434 | - | Jun 11, 14:40 UTC | Jun 12, 10:00 UTC | 19h 21m |
| 2026-06-11 | SVA5434 | - | Jun 11, 11:00 UTC | Jun 12, 10:00 UTC | 23h 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-AK11 page for operator, model, and routing details .