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
- 204
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 50m ago
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 | - | 22 | 2026-07-14 |
| SVA992 | - | 19 | 2026-07-10 |
| SVA993 | - | 13 | 2026-07-02 |
| SVA982 | - | 12 | 2026-07-13 |
| SVA962 | Saudi Arabian Airlines | 11 | 2026-06-29 |
| SVA980 | Saudi Arabian Airlines | 9 | 2026-05-27 |
| SVA987 | Saudi Arabian Airlines | 7 | 2026-06-06 |
| SVA983 | - | 7 | 2026-07-14 |
| SVA979 | - | 7 | 2026-07-11 |
| SVA986 | Saudi Arabian Airlines | 6 | 2026-06-06 |
| SVA981 | Saudi Arabian Airlines | 6 | 2026-05-27 |
| SVA972 | - | 6 | 2026-07-04 |
| SVA969 | - | 5 | 2026-06-22 |
| SVA963 | Saudi Arabian Airlines | 5 | 2026-06-29 |
| SVA931 | Saudi Arabian Airlines | 5 | 2026-06-30 |
| SVA918 | Saudi Arabian Airlines | 5 | 2026-07-05 |
| SVA3048 | - | 5 | 2026-07-06 |
| SVA932 | Saudi Arabian Airlines | 4 | 2026-05-06 |
| SVA917 | Saudi Arabian Airlines | 4 | 2026-07-04 |
| SVA905 | - | 4 | 2026-06-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 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 |
| 2026-07-08 | SVA3049 | - | Jul 8, 17:55 UTC | Jul 9, 00:50 UTC | 6h 55m |
| 2026-07-06 | SVA3048 | - | Jul 6, 11:30 UTC | Jul 6, 17:25 UTC | 5h 55m |
| 2026-07-05 | SVA918 | BRU → JED | Jul 5, 12:35 UTC | Jul 6, 12:25 UTC | 23h 50m |
| 2026-07-05 | SVA918 | BRU → JED | Jul 5, 10:10 UTC | Jul 5, 13:50 UTC | 3h 40m |
| 2026-07-04 | SVA917 | JED → BRU | Jul 4, 14:40 UTC | Jul 5, 06:20 UTC | 15h 40m |
| 2026-07-04 | SVA973 | - | Jul 4, 12:35 UTC | Jul 4, 12:50 UTC | 15m |
| 2026-07-04 | SVA972 | - | Jul 4, 10:15 UTC | Jul 4, 10:20 UTC | 5m |
| 2026-07-04 | SVA972 | - | Jul 4, 09:25 UTC | Jul 4, 09:35 UTC | 10m |
| 2026-07-04 | SVA972 | - | Jul 4, 01:40 UTC | Jul 4, 08:40 UTC | 7h 0m |
| 2026-07-03 | SVA972 | - | Jul 3, 05:20 UTC | Jul 4, 04:30 UTC | 23h 10m |
| 2026-07-02 | SVA993 | - | Jul 2, 23:05 UTC | Jul 3, 05:35 UTC | 6h 30m |
| 2026-07-02 | SVA993 | - | Jul 2, 22:20 UTC | Jul 2, 22:30 UTC | 10m |
| 2026-07-01 | SVA992 | RUH → SZX | Jul 1, 22:40 UTC | Jul 2, 18:00 UTC | 19h 20m |
| 2026-07-01 | SVA992 | RUH → SZX | Jul 1, 18:55 UTC | Jul 2, 18:00 UTC | 23h 5m |
| 2026-07-01 | SVA992 | RUH → SZX | Jul 1, 16:35 UTC | Jul 2, 16:30 UTC | 23h 55m |
| 2026-07-01 | SVA979 | - | Jul 1, 14:35 UTC | Jul 2, 14:05 UTC | 23h 30m |
| 2026-07-01 | SVA978 | RUH → CAN | Jul 1, 12:35 UTC | Jul 2, 12:15 UTC | 23h 40m |
| 2026-07-01 | SVA978 | RUH → CAN | Jul 1, 12:05 UTC | Jul 2, 05:10 UTC | 17h 5m |
| 2026-07-01 | SVA978 | RUH → CAN | Jul 1, 00:35 UTC | Jul 2, 00:30 UTC | 23h 55m |
| 2026-06-30 | SVA978 | RUH → CAN | Jun 30, 22:40 UTC | Jul 1, 19:00 UTC | 20h 20m |
| 2026-06-30 | SVA931 | JED → LGG | Jun 30, 00:45 UTC | Jun 30, 16:15 UTC | 15h 31m |
| 2026-06-29 | SVA963 | HKG → RUH | Jun 29, 23:49 UTC | Jun 30, 00:00 UTC | 10m |
| 2026-06-29 | SVA962 | RUH → HKG | Jun 29, 20:09 UTC | Jun 29, 20:35 UTC | 25m |
| 2026-06-29 | SVA962 | RUH → HKG | Jun 29, 12:29 UTC | Jun 29, 19:24 UTC | 6h 55m |
| 2026-06-28 | SVA962 | RUH → HKG | Jun 28, 19:44 UTC | Jun 29, 18:30 UTC | 22h 45m |
| 2026-06-27 | SVA979 | - | Jun 27, 21:40 UTC | Jun 28, 15:49 UTC | 18h 10m |
| 2026-06-26 | SVA978 | RUH → CAN | Jun 26, 23:04 UTC | Jun 27, 16:35 UTC | 17h 30m |
| 2026-06-26 | SVA982 | RUH → HKG | Jun 26, 20:29 UTC | Jun 26, 21:04 UTC | 35m |
| 2026-06-26 | SVA982 | RUH → HKG | Jun 26, 12:59 UTC | Jun 26, 18:09 UTC | 5h 10m |
| 2026-06-26 | SVA3049 | - | Jun 26, 03:05 UTC | Jun 26, 08:50 UTC | 5h 45m |
| 2026-06-25 | SVA3048 | - | Jun 25, 04:14 UTC | Jun 25, 21:35 UTC | 17h 20m |
| 2026-06-24 | SVA978 | RUH → CAN | Jun 24, 04:34 UTC | Jun 24, 23:50 UTC | 19h 15m |
| 2026-06-24 | SVA978 | RUH → CAN | Jun 24, 03:35 UTC | Jun 24, 23:50 UTC | 20h 15m |
| 2026-06-24 | SVA978 | RUH → CAN | Jun 24, 01:14 UTC | Jun 24, 23:50 UTC | 22h 35m |
| 2026-06-23 | SVA3048 | - | Jun 23, 15:44 UTC | Jun 23, 21:59 UTC | 6h 15m |
| 2026-06-23 | SVA993 | - | Jun 23, 03:34 UTC | Jun 23, 15:40 UTC | 12h 5m |
| 2026-06-22 | SVA992 | RUH → SZX | Jun 22, 05:49 UTC | Jun 22, 20:39 UTC | 14h 50m |
| 2026-06-22 | SVA969 | - | Jun 22, 02:40 UTC | Jun 22, 03:05 UTC | 25m |
| 2026-06-21 | SVA969 | - | Jun 21, 22:34 UTC | Jun 22, 01:35 UTC | 3h 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-AK73 page for operator, model, and routing details .