sensors Mode-S transponder
710101
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AK72 · BOEING 777-200LR
- Hex
- 710101
- Octal
- 34200401
- Decimal
- 7,405,825
- Country
- SA
- Tail
- HZ-AK72
- Type
- B77L
- Flights observed
- 192
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 710101 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 |
|---|---|---|---|
| SVA992 | Saudi Arabian Airlines | 16 | 2026-07-05 |
| SVA986 | - | 14 | 2026-07-10 |
| SVA987 | - | 13 | 2026-07-11 |
| SVA982 | - | 12 | 2026-07-09 |
| SVA969 | - | 12 | 2026-07-12 |
| SVA993 | - | 11 | 2026-07-07 |
| SVA978 | Saudi Arabian Airlines | 10 | 2026-06-20 |
| SVA962 | - | 9 | 2026-07-15 |
| SVA985 | Saudi Arabian Airlines | 7 | 2026-05-27 |
| SVA983 | - | 7 | 2026-07-10 |
| SVA979 | - | 7 | 2026-06-20 |
| SVA968 | - | 7 | 2026-07-12 |
| SVA984 | Saudi Arabian Airlines | 5 | 2026-05-26 |
| SVA932 | Saudi Arabian Airlines | 5 | 2026-06-24 |
| SVA931 | Saudi Arabian Airlines | 5 | 2026-06-23 |
| SVA3960 | - | 5 | 2026-06-29 |
| SVA963 | - | 4 | 2026-07-15 |
| SVA3961 | Saudi Arabian Airlines | 4 | 2026-06-29 |
| SVA980 | Saudi Arabian Airlines | 3 | 2026-05-20 |
| SVA972 | - | 3 | 2026-06-27 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-16 | SVA904 | - | Jul 16, 18:29 UTC | Jul 16, 21:45 UTC | 3h 15m |
| 2026-07-16 | SVA905 | - | Jul 16, 00:35 UTC | Jul 16, 13:45 UTC | 13h 10m |
| 2026-07-15 | SVA963 | - | Jul 15, 22:20 UTC | Jul 15, 22:35 UTC | 15m |
| 2026-07-15 | SVA962 | - | Jul 15, 19:15 UTC | Jul 15, 19:50 UTC | 35m |
| 2026-07-15 | SVA962 | - | Jul 15, 05:05 UTC | Jul 15, 17:10 UTC | 12h 5m |
| 2026-07-14 | SVA3045 | - | Jul 14, 22:55 UTC | Jul 15, 04:05 UTC | 5h 10m |
| 2026-07-14 | SVA3044 | - | Jul 14, 11:50 UTC | Jul 14, 18:10 UTC | 6h 20m |
| 2026-07-13 | SVA3049 | - | Jul 13, 21:15 UTC | Jul 14, 04:40 UTC | 7h 25m |
| 2026-07-13 | SVA3048 | - | Jul 13, 01:10 UTC | Jul 13, 17:30 UTC | 16h 20m |
| 2026-07-12 | SVA969 | - | Jul 12, 22:20 UTC | Jul 12, 22:45 UTC | 25m |
| 2026-07-12 | SVA969 | - | Jul 12, 19:25 UTC | Jul 12, 21:05 UTC | 1h 40m |
| 2026-07-12 | SVA969 | - | Jul 12, 17:25 UTC | Jul 12, 17:35 UTC | 10m |
| 2026-07-12 | SVA968 | - | Jul 12, 14:40 UTC | Jul 12, 15:10 UTC | 30m |
| 2026-07-11 | SVA968 | - | Jul 11, 20:55 UTC | Jul 12, 13:01 UTC | 16h 5m |
| 2026-07-11 | SVA987 | - | Jul 11, 18:45 UTC | Jul 11, 18:55 UTC | 10m |
| 2026-07-10 | SVA986 | - | Jul 10, 22:20 UTC | Jul 11, 16:30 UTC | 18h 10m |
| 2026-07-10 | SVA986 | - | Jul 10, 21:55 UTC | Jul 11, 16:30 UTC | 18h 35m |
| 2026-07-10 | SVA983 | - | Jul 10, 19:55 UTC | Jul 10, 20:05 UTC | 10m |
| 2026-07-09 | SVA982 | - | Jul 9, 22:20 UTC | Jul 10, 17:05 UTC | 18h 45m |
| 2026-07-09 | SVA982 | - | Jul 9, 20:20 UTC | Jul 10, 17:05 UTC | 20h 45m |
| 2026-07-09 | SVA982 | - | Jul 9, 19:15 UTC | Jul 10, 17:05 UTC | 21h 50m |
| 2026-07-09 | SVA3048 | - | Jul 9, 08:45 UTC | Jul 9, 13:40 UTC | 4h 55m |
| 2026-07-09 | SVA3048 | - | Jul 9, 07:35 UTC | Jul 9, 08:40 UTC | 1h 5m |
| 2026-07-08 | SVA3047 | - | Jul 8, 20:30 UTC | Jul 9, 03:25 UTC | 6h 55m |
| 2026-07-07 | SVA3046 | EMA → JED | Jul 7, 23:55 UTC | Jul 8, 16:25 UTC | 16h 30m |
| 2026-07-07 | SVA993 | - | Jul 7, 22:00 UTC | Jul 7, 22:10 UTC | 10m |
| 2026-07-05 | SVA992 | RUH → SZX | Jul 5, 23:05 UTC | Jul 6, 17:10 UTC | 18h 5m |
| 2026-07-05 | SVA969 | - | Jul 5, 19:30 UTC | Jul 5, 19:55 UTC | 25m |
| 2026-07-05 | SVA969 | - | Jul 5, 16:25 UTC | Jul 5, 18:20 UTC | 1h 55m |
| 2026-07-05 | SVA969 | - | Jul 5, 14:35 UTC | Jul 5, 14:50 UTC | 15m |
| 2026-07-05 | SVA968 | - | Jul 5, 11:25 UTC | Jul 5, 12:00 UTC | 35m |
| 2026-07-05 | SVA968 | - | Jul 5, 03:35 UTC | Jul 5, 09:50 UTC | 6h 15m |
| 2026-07-02 | SVA3047 | - | Jul 2, 19:30 UTC | Jul 3, 03:10 UTC | 7h 40m |
| 2026-07-02 | SVA3046 | EMA → JED | Jul 2, 09:20 UTC | Jul 2, 16:20 UTC | 7h 0m |
| 2026-06-29 | SVA3961 | HKG → HKG | Jun 29, 12:49 UTC | Jun 29, 19:15 UTC | 6h 25m |
| 2026-06-29 | SVA3961 | HKG → HKG | Jun 29, 11:50 UTC | Jun 29, 12:05 UTC | 15m |
| 2026-06-29 | SVA3960 | - | Jun 29, 08:50 UTC | Jun 29, 09:29 UTC | 40m |
| 2026-06-28 | SVA3960 | - | Jun 28, 12:19 UTC | Jun 29, 08:04 UTC | 19h 45m |
| 2026-06-28 | SVA3960 | - | Jun 28, 10:19 UTC | Jun 29, 08:04 UTC | 21h 45m |
| 2026-06-28 | SVA3960 | - | Jun 28, 10:10 UTC | Jun 29, 08:04 UTC | 21h 55m |
| 2026-06-27 | SVA917 | JED → BRU | Jun 27, 12:45 UTC | Jun 28, 06:00 UTC | 17h 15m |
| 2026-06-27 | SVA972 | - | Jun 27, 02:04 UTC | Jun 27, 10:10 UTC | 8h 5m |
| 2026-06-26 | SVA3041 | JED → KRF | Jun 26, 16:30 UTC | Jun 26, 21:30 UTC | 5h 0m |
| 2026-06-25 | SVA3040 | LGG → LGG | Jun 25, 09:14 UTC | Jun 25, 14:24 UTC | 5h 10m |
| 2026-06-24 | SVA3040 | LGG → LGG | Jun 24, 14:20 UTC | Jun 25, 14:14 UTC | 23h 55m |
| 2026-06-24 | SVA932 | LGG → RUH | Jun 24, 12:20 UTC | Jun 25, 12:10 UTC | 23h 50m |
| 2026-06-24 | SVA932 | LGG → RUH | Jun 24, 11:29 UTC | Jun 25, 10:15 UTC | 22h 45m |
| 2026-06-23 | SVA931 | JED → LGG | Jun 23, 16:09 UTC | Jun 24, 08:04 UTC | 15h 55m |
| 2026-06-23 | SVA963 | HKG → RUH | Jun 23, 15:24 UTC | Jun 23, 15:34 UTC | 10m |
| 2026-06-23 | SVA962 | RUH → HKG | Jun 23, 12:45 UTC | Jun 23, 13:15 UTC | 30m |
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-AK72 page for operator, model, and routing details .