sensors Mode-S transponder
710106
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AK28 · BOEING 777-300ER
- Hex
- 710106
- Octal
- 34200406
- Decimal
- 7,405,830
- Country
- SA
- Tail
- HZ-AK28
- Type
- B77W
- Flights observed
- 194
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 21h ago
Last known position
Country allocation
The ICAO 24-bit address 710106 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 |
|---|---|---|---|
| SVA111 | Saudi Arabian Airlines | 12 | 2026-06-09 |
| SVA862 | - | 11 | 2026-06-20 |
| SVA110 | Saudi Arabian Airlines | 10 | 2026-06-10 |
| SVA798 | - | 9 | 2026-07-05 |
| SVA861 | - | 8 | 2026-06-21 |
| SVA144 | - | 8 | 2026-06-17 |
| SVA818 | - | 7 | 2026-07-07 |
| SVA756 | - | 6 | 2026-07-10 |
| SVA724 | - | 6 | 2026-06-23 |
| SVA341 | - | 6 | 2026-07-07 |
| SVA143 | - | 6 | 2026-06-18 |
| SVA373 | - | 5 | 2026-07-11 |
| SVA757 | - | 4 | 2026-07-10 |
| SVA736 | - | 4 | 2026-06-23 |
| SVA728 | Saudi Arabian Airlines | 4 | 2026-04-19 |
| SVA5729 | - | 4 | 2026-04-28 |
| SVA5727 | - | 4 | 2026-04-29 |
| SVA372 | Saudi Arabian Airlines | 4 | 2026-07-11 |
| SVA804 | Saudi Arabian Airlines | 3 | 2026-06-13 |
| SVA799 | Saudi Arabian Airlines | 3 | 2026-07-06 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | SVA802 | JED → DAC | Jul 13, 07:55 UTC | Jul 13, 15:00 UTC | 7h 5m |
| 2026-07-13 | SVA735 | - | Jul 13, 05:45 UTC | Jul 13, 06:20 UTC | 35m |
| 2026-07-12 | SVA734 | - | Jul 12, 13:40 UTC | Jul 13, 03:25 UTC | 13h 45m |
| 2026-07-12 | SVA801 | DAC → RUH | Jul 12, 11:50 UTC | Jul 12, 12:01 UTC | 10m |
| 2026-07-12 | SVA800 | - | Jul 12, 09:45 UTC | Jul 12, 10:01 UTC | 15m |
| 2026-07-11 | SVA372 | CMN → JED | Jul 11, 14:30 UTC | Jul 12, 08:05 UTC | 17h 35m |
| 2026-07-11 | SVA373 | - | Jul 11, 07:25 UTC | Jul 11, 11:15 UTC | 3h 50m |
| 2026-07-10 | SVA373 | - | Jul 10, 09:50 UTC | Jul 11, 09:25 UTC | 23h 35m |
| 2026-07-10 | SVA757 | - | Jul 10, 07:35 UTC | Jul 11, 07:25 UTC | 23h 50m |
| 2026-07-10 | SVA756 | - | Jul 10, 02:20 UTC | Jul 10, 05:40 UTC | 3h 20m |
| 2026-07-09 | SVA595 | - | Jul 9, 19:45 UTC | Jul 9, 20:35 UTC | 50m |
| 2026-07-09 | SVA594 | - | Jul 9, 01:00 UTC | Jul 9, 18:00 UTC | 17h 0m |
| 2026-07-08 | SVA722 | - | Jul 8, 14:45 UTC | Jul 9, 08:25 UTC | 17h 40m |
| 2026-07-08 | SVA819 | - | Jul 8, 11:10 UTC | Jul 8, 11:20 UTC | 10m |
| 2026-07-07 | SVA818 | - | Jul 7, 15:35 UTC | Jul 8, 09:05 UTC | 17h 30m |
| 2026-07-07 | SVA341 | - | Jul 7, 10:35 UTC | Jul 7, 13:05 UTC | 2h 30m |
| 2026-07-06 | SVA341 | - | Jul 6, 13:40 UTC | Jul 7, 13:05 UTC | 23h 25m |
| 2026-07-06 | SVA799 | DAC → MED | Jul 6, 12:00 UTC | Jul 7, 11:30 UTC | 23h 30m |
| 2026-07-06 | SVA799 | DAC → MED | Jul 6, 09:55 UTC | Jul 6, 14:30 UTC | 4h 35m |
| 2026-07-05 | SVA798 | - | Jul 5, 13:35 UTC | Jul 6, 07:35 UTC | 18h 0m |
| 2026-07-05 | SVA798 | - | Jul 5, 11:50 UTC | Jul 6, 07:35 UTC | 19h 45m |
| 2026-07-05 | SVA798 | DAC → DAC | Jul 5, 09:45 UTC | Jul 6, 07:35 UTC | 21h 50m |
| 2026-07-04 | SVA798 | - | Jul 4, 13:40 UTC | Jul 5, 07:40 UTC | 18h 0m |
| 2026-07-04 | SVA798 | DAC → DAC | Jul 4, 09:50 UTC | Jul 5, 07:40 UTC | 21h 50m |
| 2026-07-04 | SVA798 | - | Jul 4, 02:40 UTC | Jul 4, 07:35 UTC | 4h 55m |
| 2026-07-02 | SVA799 | DAC → MED | Jul 2, 09:55 UTC | Jul 2, 14:35 UTC | 4h 40m |
| 2026-07-01 | SVA798 | - | Jul 1, 11:35 UTC | Jul 2, 07:25 UTC | 19h 50m |
| 2026-07-01 | SVA798 | DAC → DAC | Jul 1, 11:20 UTC | Jul 2, 07:25 UTC | 20h 5m |
| 2026-06-30 | SVA798 | - | Jun 30, 14:35 UTC | Jul 1, 08:35 UTC | 18h 0m |
| 2026-06-29 | SVA341 | - | Jun 29, 23:25 UTC | Jun 30, 12:10 UTC | 12h 46m |
| 2026-06-29 | SVA5900 | - | Jun 29, 17:59 UTC | Jun 29, 21:50 UTC | 3h 50m |
| 2026-06-29 | SVA757 | - | Jun 29, 06:29 UTC | Jun 29, 09:10 UTC | 2h 40m |
| 2026-06-28 | SVA756 | - | Jun 28, 11:55 UTC | Jun 29, 04:30 UTC | 16h 35m |
| 2026-06-27 | SVA3658 | - | Jun 27, 21:25 UTC | Jun 28, 09:20 UTC | 11h 55m |
| 2026-06-27 | SVA5948 | - | Jun 27, 05:15 UTC | Jun 27, 19:49 UTC | 14h 35m |
| 2026-06-26 | SVA9651 | DEL → BOM | Jun 26, 14:59 UTC | Jun 27, 03:20 UTC | 12h 20m |
| 2026-06-25 | SVA9663 | DEL → DEL | Jun 25, 22:29 UTC | Jun 26, 12:59 UTC | 14h 30m |
| 2026-06-25 | SVA5914 | DEL → DEL | Jun 25, 07:59 UTC | Jun 25, 20:34 UTC | 12h 35m |
| 2026-06-25 | SVA5902 | - | Jun 25, 02:25 UTC | Jun 25, 06:25 UTC | 4h 0m |
| 2026-06-24 | SVA5902 | - | Jun 24, 07:34 UTC | Jun 25, 06:25 UTC | 22h 50m |
| 2026-06-24 | SVA5902 | - | Jun 24, 05:34 UTC | Jun 25, 05:29 UTC | 23h 55m |
| 2026-06-24 | SVA725 | - | Jun 24, 00:55 UTC | Jun 24, 08:14 UTC | 7h 20m |
| 2026-06-23 | SVA724 | - | Jun 23, 16:20 UTC | Jun 24, 00:49 UTC | 8h 30m |
| 2026-06-23 | SVA736 | - | Jun 23, 11:19 UTC | Jun 23, 14:10 UTC | 2h 50m |
| 2026-06-21 | SVA861 | - | Jun 21, 08:20 UTC | Jun 21, 16:34 UTC | 8h 15m |
| 2026-06-20 | SVA862 | - | Jun 20, 12:19 UTC | Jun 21, 06:04 UTC | 17h 45m |
| 2026-06-20 | SVA861 | - | Jun 20, 10:20 UTC | Jun 21, 06:04 UTC | 19h 45m |
| 2026-06-20 | SVA861 | - | Jun 20, 08:09 UTC | Jun 21, 06:04 UTC | 21h 55m |
| 2026-06-19 | SVA862 | - | Jun 19, 11:34 UTC | Jun 20, 05:44 UTC | 18h 10m |
| 2026-06-19 | SVA862 | - | Jun 19, 10:39 UTC | Jun 20, 05:44 UTC | 19h 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-AK28 page for operator, model, and routing details .