sensors Mode-S transponder
710056
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AK14 · BOEING 777-300ER
- Hex
- 710056
- Octal
- 34200126
- Decimal
- 7,405,654
- Country
- SA
- Tail
- HZ-AK14
- Type
- B77W
- Flights observed
- 95
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 710056 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 |
|---|---|---|---|
| SVA805 | Saudi Arabian Airlines | 7 | 2026-05-28 |
| SVA9419 | - | 4 | 2026-05-04 |
| SVA804 | Saudi Arabian Airlines | 4 | 2026-05-28 |
| SVA9412 | - | 3 | 2026-05-01 |
| SVA9337 | - | 3 | 2026-04-27 |
| SVA738 | Saudi Arabian Airlines | 3 | 2026-05-11 |
| SVA9539 | - | 2 | 2026-05-15 |
| SVA9515 | - | 2 | 2026-05-14 |
| SVA9470 | - | 2 | 2026-05-10 |
| SVA9460 | - | 2 | 2026-05-08 |
| SVA9439 | - | 2 | 2026-05-06 |
| SVA9408 | - | 2 | 2026-05-02 |
| SVA9369 | - | 2 | 2026-04-29 |
| SVA9353 | - | 2 | 2026-04-25 |
| SVA9330 | - | 2 | 2026-04-26 |
| SVA9320 | - | 2 | 2026-05-18 |
| SVA9312 | - | 2 | 2026-05-17 |
| SVA807 | Saudi Arabian Airlines | 2 | 2026-05-25 |
| SVA806 | Saudi Arabian Airlines | 2 | 2026-05-24 |
| SVA800 | Saudi Arabian Airlines | 2 | 2026-05-12 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | SVA5806 | - | May 30, 00:15 UTC | May 30, 02:45 UTC | 2h 30m |
| 2026-05-28 | SVA805 | DAC → JED | May 28, 18:50 UTC | May 28, 21:55 UTC | 3h 5m |
| 2026-05-28 | SVA804 | JED → DAC | May 28, 05:25 UTC | May 28, 16:50 UTC | 11h 25m |
| 2026-05-26 | SVA805 | DAC → JED | May 26, 18:40 UTC | May 26, 23:39 UTC | 5h 0m |
| 2026-05-25 | SVA804 | JED → DAC | May 25, 23:35 UTC | May 26, 16:55 UTC | 17h 20m |
| 2026-05-25 | SVA724 | RUH → ISB | May 25, 10:35 UTC | May 26, 08:10 UTC | 21h 35m |
| 2026-05-25 | SVA807 | DAC → RUH | May 25, 07:50 UTC | May 26, 05:25 UTC | 21h 34m |
| 2026-05-25 | SVA807 | DAC → RUH | May 25, 05:45 UTC | May 26, 02:15 UTC | 20h 29m |
| 2026-05-24 | SVA806 | RUH → DAC | May 24, 23:00 UTC | May 25, 03:25 UTC | 4h 25m |
| 2026-05-23 | SVA761 | DEL → RUH | May 23, 13:45 UTC | May 23, 14:15 UTC | 30m |
| 2026-05-22 | SVA805 | DAC → JED | May 22, 18:45 UTC | May 23, 11:55 UTC | 17h 9m |
| 2026-05-21 | SVA804 | JED → DAC | May 21, 23:45 UTC | May 22, 16:45 UTC | 17h 0m |
| 2026-05-20 | SVA805 | DAC → JED | May 20, 19:45 UTC | May 21, 13:40 UTC | 17h 55m |
| 2026-05-20 | SVA805 | DAC → JED | May 20, 18:55 UTC | May 21, 13:40 UTC | 18h 45m |
| 2026-05-20 | SVA804 | JED → DAC | May 20, 13:50 UTC | May 20, 16:45 UTC | 2h 55m |
| 2026-05-19 | SVA5403 | - | May 19, 09:05 UTC | May 19, 13:20 UTC | 4h 15m |
| 2026-05-18 | SVA9320 | - | May 18, 11:50 UTC | May 19, 06:55 UTC | 19h 4m |
| 2026-05-18 | SVA9320 | - | May 18, 08:01 UTC | May 19, 06:55 UTC | 22h 54m |
| 2026-05-17 | SVA9312 | - | May 17, 11:35 UTC | May 18, 05:05 UTC | 17h 30m |
| 2026-05-17 | SVA9312 | - | May 17, 07:50 UTC | May 18, 05:05 UTC | 21h 15m |
| 2026-05-16 | SVA9549 | - | May 16, 10:11 UTC | May 17, 05:20 UTC | 19h 10m |
| 2026-05-16 | SVA5109 | - | May 16, 06:20 UTC | May 16, 06:31 UTC | 10m |
| 2026-05-15 | SVA9539 | - | May 15, 22:25 UTC | May 16, 03:30 UTC | 5h 5m |
| 2026-05-15 | SVA9539 | - | May 15, 04:40 UTC | May 16, 03:30 UTC | 22h 49m |
| 2026-05-15 | SVA5105 | - | May 15, 01:05 UTC | May 15, 23:30 UTC | 22h 24m |
| 2026-05-14 | SVA9515 | - | May 14, 17:25 UTC | May 14, 21:45 UTC | 4h 20m |
| 2026-05-14 | SVA9515 | - | May 14, 00:50 UTC | May 14, 21:45 UTC | 20h 55m |
| 2026-05-13 | SVA5421 | - | May 13, 21:10 UTC | May 13, 21:25 UTC | 15m |
| 2026-05-13 | SVA9502 | - | May 13, 11:55 UTC | May 13, 16:40 UTC | 4h 45m |
| 2026-05-12 | SVA801 | DAC → RUH | May 12, 11:55 UTC | May 12, 12:00 UTC | 5m |
| 2026-05-12 | SVA800 | JED → DAC | May 12, 09:30 UTC | May 12, 09:40 UTC | 10m |
| 2026-05-11 | SVA739 | LHE → JED | May 11, 22:00 UTC | May 11, 22:35 UTC | 34m |
| 2026-05-11 | SVA738 | JED → LHE | May 11, 16:50 UTC | May 11, 19:30 UTC | 2h 41m |
| 2026-05-10 | SVA738 | JED → LHE | May 10, 17:34 UTC | May 11, 17:10 UTC | 23h 36m |
| 2026-05-10 | SVA5317 | - | May 10, 13:44 UTC | May 10, 17:34 UTC | 3h 50m |
| 2026-05-10 | SVA5317 | - | May 10, 12:59 UTC | May 10, 13:10 UTC | 10m |
| 2026-05-10 | SVA9470 | - | May 10, 03:20 UTC | May 10, 08:40 UTC | 5h 20m |
| 2026-05-09 | SVA9470 | - | May 9, 11:55 UTC | May 10, 08:40 UTC | 20h 45m |
| 2026-05-09 | SVA5269 | - | May 9, 07:50 UTC | May 9, 08:05 UTC | 15m |
| 2026-05-08 | SVA9460 | - | May 8, 10:25 UTC | May 9, 05:10 UTC | 18h 45m |
| 2026-05-08 | SVA9460 | - | May 8, 06:14 UTC | May 9, 05:10 UTC | 22h 55m |
| 2026-05-07 | SVA9456 | - | May 7, 20:50 UTC | May 8, 01:49 UTC | 5h 0m |
| 2026-05-06 | SVA5173 | - | May 6, 10:25 UTC | May 6, 13:45 UTC | 3h 20m |
| 2026-05-06 | SVA5173 | - | May 6, 09:25 UTC | May 6, 09:35 UTC | 10m |
| 2026-05-06 | SVA9439 | - | May 6, 06:10 UTC | May 6, 06:25 UTC | 15m |
| 2026-05-05 | SVA9439 | - | May 5, 22:20 UTC | May 6, 05:15 UTC | 6h 55m |
| 2026-05-04 | SVA5199 | - | May 4, 14:50 UTC | May 4, 16:00 UTC | 1h 10m |
| 2026-05-04 | SVA5199 | - | May 4, 10:45 UTC | May 4, 10:55 UTC | 10m |
| 2026-05-04 | SVA9419 | - | May 4, 07:40 UTC | May 4, 08:00 UTC | 20m |
| 2026-05-03 | SVA9419 | - | May 3, 13:20 UTC | May 4, 07:10 UTC | 17h 50m |
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-AK14 page for operator, model, and routing details .