sensors Mode-S transponder
710107
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AK29 · BOEING 777-300ER
- Hex
- 710107
- Octal
- 34200407
- Decimal
- 7,405,831
- Country
- SA
- Tail
- HZ-AK29
- Type
- B77W
- Flights observed
- 175
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 5h ago
Current position
Country allocation
The ICAO 24-bit address 710107 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 | - | 10 | 2026-06-22 |
| SVA804 | Saudi Arabian Airlines | 9 | 2026-06-08 |
| SVA143 | - | 8 | 2026-07-02 |
| SVA827 | Saudi Arabian Airlines | 7 | 2026-05-27 |
| SVA818 | - | 7 | 2026-06-18 |
| SVA861 | - | 6 | 2026-07-04 |
| SVA802 | Saudi Arabian Airlines | 6 | 2026-07-08 |
| SVA726 | Saudi Arabian Airlines | 6 | 2026-07-05 |
| SVA803 | - | 5 | 2026-07-08 |
| SVA144 | - | 5 | 2026-07-02 |
| SVA819 | - | 4 | 2026-06-18 |
| SVA805 | Saudi Arabian Airlines | 4 | 2026-06-08 |
| SVA5804 | - | 4 | 2026-06-04 |
| SVA3811 | - | 4 | 2026-04-13 |
| SVA3190 | - | 4 | 2026-04-13 |
| SVA9650 | - | 3 | 2026-04-18 |
| SVA862 | - | 3 | 2026-07-03 |
| SVA807 | - | 3 | 2026-07-12 |
| SVA772 | Saudi Arabian Airlines | 3 | 2026-05-24 |
| SVA736 | - | 3 | 2026-06-29 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | SVA342 | ALG → JED | Jul 13, 22:50 UTC | Jul 14, 01:40 UTC | 2h 50m |
| 2026-07-13 | SVA343 | JED → ALG | Jul 13, 16:50 UTC | Jul 13, 19:20 UTC | 2h 30m |
| 2026-07-12 | SVA807 | - | Jul 12, 06:45 UTC | Jul 12, 11:15 UTC | 4h 30m |
| 2026-07-11 | SVA806 | - | Jul 11, 22:40 UTC | Jul 12, 03:50 UTC | 5h 10m |
| 2026-07-09 | SVA340 | ALG → JED | Jul 9, 15:20 UTC | Jul 10, 05:45 UTC | 14h 25m |
| 2026-07-09 | SVA341 | - | Jul 9, 09:50 UTC | Jul 9, 12:40 UTC | 2h 50m |
| 2026-07-08 | SVA803 | - | Jul 8, 22:05 UTC | Jul 9, 02:05 UTC | 4h 0m |
| 2026-07-08 | SVA802 | JED → DAC | Jul 8, 14:40 UTC | Jul 8, 19:35 UTC | 4h 55m |
| 2026-07-06 | SVA551 | - | Jul 6, 17:20 UTC | Jul 6, 18:10 UTC | 50m |
| 2026-07-05 | SVA550 | - | Jul 5, 22:25 UTC | Jul 6, 15:35 UTC | 17h 10m |
| 2026-07-05 | SVA550 | - | Jul 5, 17:50 UTC | Jul 6, 15:35 UTC | 21h 45m |
| 2026-07-05 | SVA550 | - | Jul 5, 16:50 UTC | Jul 6, 15:35 UTC | 22h 45m |
| 2026-07-05 | SVA726 | JED → ISB | Jul 5, 07:15 UTC | Jul 6, 00:35 UTC | 17h 20m |
| 2026-07-05 | SVA726 | JED → ISB | Jul 5, 05:30 UTC | Jul 6, 00:35 UTC | 19h 5m |
| 2026-07-04 | SVA726 | JED → ISB | Jul 4, 23:50 UTC | Jul 5, 22:30 UTC | 22h 40m |
| 2026-07-04 | SVA724 | - | Jul 4, 23:40 UTC | Jul 5, 17:50 UTC | 18h 10m |
| 2026-07-04 | SVA861 | - | Jul 4, 12:20 UTC | Jul 5, 08:05 UTC | 19h 45m |
| 2026-07-04 | SVA861 | - | Jul 4, 10:00 UTC | Jul 5, 08:05 UTC | 22h 5m |
| 2026-07-04 | SVA861 | - | Jul 4, 07:50 UTC | Jul 5, 07:45 UTC | 23h 55m |
| 2026-07-03 | SVA862 | - | Jul 3, 10:55 UTC | Jul 4, 05:45 UTC | 18h 50m |
| 2026-07-02 | SVA143 | - | Jul 2, 11:50 UTC | Jul 3, 06:00 UTC | 18h 10m |
| 2026-07-02 | SVA144 | - | Jul 2, 10:25 UTC | Jul 3, 06:00 UTC | 19h 35m |
| 2026-07-01 | SVA143 | - | Jul 1, 11:20 UTC | Jul 2, 04:55 UTC | 17h 35m |
| 2026-06-30 | SVA143 | - | Jun 30, 11:20 UTC | Jul 1, 05:00 UTC | 17h 40m |
| 2026-06-29 | SVA736 | - | Jun 29, 14:29 UTC | Jun 30, 12:20 UTC | 21h 51m |
| 2026-06-28 | SVA5964 | - | Jun 28, 18:29 UTC | Jun 29, 12:00 UTC | 17h 30m |
| 2026-06-28 | SVA5964 | - | Jun 28, 16:05 UTC | Jun 29, 12:00 UTC | 19h 55m |
| 2026-06-28 | SVA372 | CMN → JED | Jun 28, 14:14 UTC | Jun 29, 12:00 UTC | 21h 45m |
| 2026-06-28 | SVA373 | - | Jun 28, 08:25 UTC | Jun 28, 12:05 UTC | 3h 40m |
| 2026-06-26 | SVA726 | JED → ISB | Jun 26, 05:55 UTC | Jun 27, 01:44 UTC | 19h 50m |
| 2026-06-26 | SVA5928 | - | Jun 26, 01:10 UTC | Jun 26, 04:20 UTC | 3h 10m |
| 2026-06-25 | SVA5928 | - | Jun 25, 03:54 UTC | Jun 26, 03:45 UTC | 23h 50m |
| 2026-06-25 | SVA811 | DAC → JED | Jun 25, 02:05 UTC | Jun 26, 01:45 UTC | 23h 40m |
| 2026-06-25 | SVA811 | DAC → JED | Jun 25, 00:09 UTC | Jun 25, 04:10 UTC | 4h 0m |
| 2026-06-24 | SVA810 | - | Jun 24, 17:40 UTC | Jun 24, 22:19 UTC | 4h 40m |
| 2026-06-22 | SVA728 | - | Jun 22, 21:49 UTC | Jun 23, 16:09 UTC | 18h 20m |
| 2026-06-22 | SVA728 | - | Jun 22, 21:35 UTC | Jun 23, 16:09 UTC | 18h 35m |
| 2026-06-22 | SVA826 | - | Jun 22, 15:10 UTC | Jun 22, 15:29 UTC | 20m |
| 2026-06-22 | SVA826 | - | Jun 22, 07:19 UTC | Jun 22, 14:40 UTC | 7h 20m |
| 2026-06-20 | SVA9739 | - | Jun 20, 21:05 UTC | Jun 21, 07:34 UTC | 10h 30m |
| 2026-06-20 | SVA5948 | - | Jun 20, 15:49 UTC | Jun 20, 19:04 UTC | 3h 15m |
| 2026-06-19 | SVA5948 | - | Jun 19, 22:34 UTC | Jun 20, 19:04 UTC | 20h 30m |
| 2026-06-19 | SVA9747 | - | Jun 19, 06:04 UTC | Jun 19, 22:39 UTC | 16h 35m |
| 2026-06-18 | SVA5926 | - | Jun 18, 14:15 UTC | Jun 19, 04:34 UTC | 14h 19m |
| 2026-06-18 | SVA819 | - | Jun 18, 10:40 UTC | Jun 18, 10:55 UTC | 15m |
| 2026-06-18 | SVA818 | - | Jun 18, 08:25 UTC | Jun 18, 08:40 UTC | 15m |
| 2026-06-17 | SVA818 | - | Jun 17, 14:55 UTC | Jun 18, 07:40 UTC | 16h 45m |
| 2026-06-16 | SVA5814 | - | Jun 16, 18:05 UTC | Jun 17, 13:00 UTC | 18h 56m |
| 2026-06-16 | SVA826 | - | Jun 16, 15:45 UTC | Jun 16, 16:00 UTC | 15m |
| 2026-06-15 | SVA826 | - | Jun 15, 20:59 UTC | Jun 16, 15:09 UTC | 18h 10m |
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-AK29 page for operator, model, and routing details .