sensors Mode-S transponder
710102
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AK73 · BOEING 777-200LR
- Hex
- 710102
- Octal
- 34200402
- Decimal
- 7,405,826
- Country
- SA
- Tail
- HZ-AK73
- Type
- B77L
- Flights observed
- 243
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- Jul 26, 19:35 UTC
Last known position
Country allocation
The ICAO 24-bit address 710102 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 |
|---|---|---|---|
| SVA978 | - | 26 | 2026-07-15 |
| SVA992 | - | 19 | 2026-07-10 |
| SVA982 | - | 14 | 2026-07-23 |
| SVA993 | - | 13 | 2026-07-02 |
| SVA962 | Saudi Arabian Airlines | 11 | 2026-06-29 |
| SVA980 | Saudi Arabian Airlines | 9 | 2026-05-27 |
| SVA979 | - | 9 | 2026-07-15 |
| SVA972 | Saudi Arabian Airlines | 9 | 2026-07-24 |
| SVA969 | Saudi Arabian Airlines | 9 | 2026-07-20 |
| SVA987 | - | 8 | 2026-07-23 |
| SVA983 | Saudi Arabian Airlines | 8 | 2026-07-24 |
| SVA986 | Saudi Arabian Airlines | 7 | 2026-07-23 |
| SVA3045 | - | 7 | 2026-07-17 |
| SVA981 | Saudi Arabian Airlines | 6 | 2026-05-27 |
| SVA968 | - | 6 | 2026-07-19 |
| SVA918 | Saudi Arabian Airlines | 6 | 2026-07-26 |
| SVA3046 | - | 6 | 2026-07-18 |
| SVA963 | Saudi Arabian Airlines | 5 | 2026-06-29 |
| SVA931 | Saudi Arabian Airlines | 5 | 2026-06-30 |
| SVA917 | Saudi Arabian Airlines | 5 | 2026-07-25 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | SVA918 | BRU → JED | Jul 26, 16:00 UTC | Jul 26, 19:35 UTC | 3h 35m |
| 2026-07-25 | SVA917 | JED → BRU | Jul 25, 22:20 UTC | Jul 26, 12:30 UTC | 14h 11m |
| 2026-07-25 | SVA973 | HKG → HKG | Jul 25, 20:05 UTC | Jul 25, 20:15 UTC | 10m |
| 2026-07-24 | SVA972 | RUH → HKG | Jul 24, 22:35 UTC | Jul 25, 17:20 UTC | 18h 45m |
| 2026-07-24 | SVA972 | RUH → HKG | Jul 24, 21:10 UTC | Jul 25, 17:20 UTC | 20h 10m |
| 2026-07-24 | SVA972 | RUH → HKG | Jul 24, 19:55 UTC | Jul 25, 17:20 UTC | 21h 25m |
| 2026-07-24 | SVA983 | HKG → RUH | Jul 24, 19:00 UTC | Jul 24, 19:10 UTC | 10m |
| 2026-07-23 | SVA982 | - | Jul 23, 21:30 UTC | Jul 24, 16:30 UTC | 19h 0m |
| 2026-07-23 | SVA982 | - | Jul 23, 19:00 UTC | Jul 24, 16:30 UTC | 21h 30m |
| 2026-07-23 | SVA987 | - | Jul 23, 16:45 UTC | Jul 23, 17:00 UTC | 15m |
| 2026-07-23 | SVA986 | RUH → HKG | Jul 23, 06:30 UTC | Jul 23, 14:40 UTC | 8h 10m |
| 2026-07-21 | SVA934 | - | Jul 21, 14:45 UTC | Jul 21, 17:40 UTC | 2h 55m |
| 2026-07-21 | SVA933 | - | Jul 21, 07:40 UTC | Jul 21, 11:10 UTC | 3h 30m |
| 2026-07-20 | SVA947 | - | Jul 20, 18:20 UTC | Jul 20, 18:35 UTC | 15m |
| 2026-07-20 | SVA969 | BOM → JED | Jul 20, 04:50 UTC | Jul 20, 07:25 UTC | 2h 35m |
| 2026-07-20 | SVA969 | BOM → JED | Jul 20, 02:05 UTC | Jul 20, 02:15 UTC | 10m |
| 2026-07-19 | SVA969 | BOM → JED | Jul 19, 23:15 UTC | Jul 20, 00:50 UTC | 1h 35m |
| 2026-07-19 | SVA969 | BOM → JED | Jul 19, 21:10 UTC | Jul 19, 21:25 UTC | 15m |
| 2026-07-19 | SVA968 | - | Jul 19, 00:35 UTC | Jul 19, 19:15 UTC | 18h 40m |
| 2026-07-18 | SVA968 | - | Jul 18, 23:35 UTC | Jul 19, 19:15 UTC | 19h 40m |
| 2026-07-18 | SVA968 | - | Jul 18, 17:20 UTC | Jul 19, 16:30 UTC | 23h 10m |
| 2026-07-18 | SVA3047 | RUH → LGG | Jul 18, 12:35 UTC | Jul 19, 11:30 UTC | 22h 55m |
| 2026-07-18 | SVA3047 | RUH → LGG | Jul 18, 11:50 UTC | Jul 19, 02:50 UTC | 15h 0m |
| 2026-07-18 | SVA3046 | - | Jul 18, 01:34 UTC | Jul 19, 00:30 UTC | 22h 56m |
| 2026-07-17 | SVA3045 | - | Jul 17, 23:05 UTC | Jul 18, 18:05 UTC | 19h 1m |
| 2026-07-17 | SVA3045 | - | Jul 17, 21:50 UTC | Jul 18, 18:05 UTC | 20h 16m |
| 2026-07-17 | SVA3045 | - | Jul 17, 16:34 UTC | Jul 18, 12:55 UTC | 20h 21m |
| 2026-07-17 | SVA3045 | - | Jul 17, 14:55 UTC | Jul 18, 12:55 UTC | 22h 1m |
| 2026-07-17 | SVA3044 | - | Jul 17, 12:45 UTC | Jul 18, 12:30 UTC | 23h 46m |
| 2026-07-16 | SVA3046 | - | Jul 16, 11:25 UTC | Jul 17, 05:10 UTC | 17h 45m |
| 2026-07-16 | SVA3046 | - | Jul 16, 02:35 UTC | Jul 17, 02:30 UTC | 23h 55m |
| 2026-07-16 | SVA3046 | - | Jul 16, 00:35 UTC | Jul 17, 00:30 UTC | 23h 55m |
| 2026-07-15 | SVA3046 | - | Jul 15, 23:30 UTC | Jul 16, 17:35 UTC | 18h 5m |
| 2026-07-15 | SVA979 | - | Jul 15, 15:25 UTC | Jul 16, 14:25 UTC | 23h 0m |
| 2026-07-15 | SVA979 | - | Jul 15, 13:20 UTC | Jul 16, 12:30 UTC | 23h 10m |
| 2026-07-15 | SVA978 | - | Jul 15, 11:10 UTC | Jul 16, 04:25 UTC | 17h 15m |
| 2026-07-14 | SVA978 | - | Jul 14, 22:45 UTC | Jul 15, 16:55 UTC | 18h 10m |
| 2026-07-14 | SVA978 | - | Jul 14, 21:00 UTC | Jul 15, 16:55 UTC | 19h 54m |
| 2026-07-14 | SVA978 | - | Jul 14, 18:35 UTC | Jul 15, 16:55 UTC | 22h 19m |
| 2026-07-14 | SVA978 | - | Jul 14, 18:25 UTC | Jul 15, 16:30 UTC | 22h 4m |
| 2026-07-14 | SVA983 | - | Jul 14, 16:20 UTC | Jul 14, 16:30 UTC | 10m |
| 2026-07-13 | SVA982 | - | Jul 13, 18:35 UTC | Jul 14, 14:20 UTC | 19h 45m |
| 2026-07-13 | SVA923 | JED → BRU | Jul 13, 00:10 UTC | Jul 13, 15:10 UTC | 15h 0m |
| 2026-07-12 | SVA983 | - | Jul 12, 22:05 UTC | Jul 12, 22:20 UTC | 15m |
| 2026-07-12 | SVA982 | - | Jul 12, 00:35 UTC | Jul 12, 19:40 UTC | 19h 5m |
| 2026-07-11 | SVA982 | - | Jul 11, 23:40 UTC | Jul 12, 19:40 UTC | 20h 0m |
| 2026-07-11 | SVA979 | - | Jul 11, 21:40 UTC | Jul 11, 22:01 UTC | 20m |
| 2026-07-11 | SVA978 | - | Jul 11, 01:50 UTC | Jul 11, 17:35 UTC | 15h 45m |
| 2026-07-10 | SVA992 | - | Jul 10, 10:55 UTC | Jul 10, 17:05 UTC | 6h 10m |
| 2026-07-09 | SVA3044 | - | Jul 9, 04:55 UTC | Jul 9, 23:05 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-AK73 page for operator, model, and routing details .