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
No current signal · last broadcast 2h ago
Flights observed
115
Distinct callsigns
20
Country
SA
Last broadcast
2h ago

Last known position

Most recent position reported by Mode-S 710102.

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

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-30 SVA972 RUH → HKG May 30, 08:55 UTCMay 30, 14:30 UTC5h 35m
2026-05-28 SVA3048 - May 28, 23:50 UTCMay 29, 17:20 UTC17h 30m
2026-05-28 SVA3048 - May 28, 21:05 UTCMay 29, 17:20 UTC20h 15m
2026-05-27 SVA3046 EMA → JED May 27, 19:25 UTCMay 28, 14:30 UTC19h 5m
2026-05-27 SVA981 HKG → RUH May 27, 18:35 UTCMay 27, 18:50 UTC15m
2026-05-27 SVA980 RUH → HKG May 27, 15:45 UTCMay 27, 16:10 UTC25m
2026-05-27 SVA980 RUH → HKG May 27, 08:15 UTCMay 27, 13:25 UTC5h 10m
2026-05-25 SVA924 MST → JED May 25, 18:40 UTCMay 25, 21:30 UTC2h 49m
2026-05-24 SVA923 JED → BRU May 24, 23:00 UTCMay 25, 13:40 UTC14h 40m
2026-05-24 SVA983 HKG → RUH May 24, 20:30 UTCMay 24, 20:40 UTC10m
2026-05-24 SVA982 RUH → HKG May 24, 17:00 UTCMay 24, 17:35 UTC35m
2026-05-24 SVA982 RUH → HKG May 24, 11:50 UTCMay 24, 15:10 UTC3h 20m
2026-05-21 SVA904 LGG → RUH May 21, 13:35 UTCMay 21, 16:30 UTC2h 55m
2026-05-20 SVA905 JED → JFK May 20, 16:35 UTCMay 21, 09:35 UTC17h 0m
2026-05-20 SVA963 HKG → RUH May 20, 13:45 UTCMay 20, 14:00 UTC15m
2026-05-20 SVA962 RUH → HKG May 20, 10:20 UTCMay 20, 10:45 UTC25m
2026-05-19 SVA962 RUH → HKG May 19, 19:45 UTCMay 20, 08:15 UTC12h 31m
2026-05-19 SVA3025 - May 19, 14:15 UTCMay 19, 17:10 UTC2h 55m
2026-05-16 SVA987 HKG → RUH May 16, 20:55 UTCMay 17, 01:50 UTC4h 55m
2026-05-16 SVA987 HKG → RUH May 16, 17:50 UTCMay 16, 18:00 UTC10m
2026-05-16 SVA986 RUH → HKG May 16, 13:55 UTCMay 16, 14:16 UTC20m
2026-05-15 SVA983 HKG → RUH May 15, 21:25 UTCMay 16, 11:46 UTC14h 21m
2026-05-15 SVA983 HKG → RUH May 15, 18:55 UTCMay 15, 19:10 UTC15m
2026-05-15 SVA982 RUH → HKG May 15, 14:55 UTCMay 15, 15:25 UTC30m
2026-05-14 SVA982 RUH → HKG May 14, 19:45 UTCMay 15, 12:55 UTC17h 10m
2026-05-14 SVA987 HKG → RUH May 14, 16:50 UTCMay 14, 17:05 UTC15m
2026-05-13 SVA986 RUH → HKG May 13, 21:20 UTCMay 14, 13:10 UTC15h 50m
2026-05-13 SVA981 HKG → RUH May 13, 18:35 UTCMay 13, 18:50 UTC15m
2026-05-13 SVA980 RUH → HKG May 13, 14:40 UTCMay 13, 15:20 UTC40m
2026-05-12 SVA980 RUH → HKG May 12, 21:10 UTCMay 13, 12:40 UTC15h 30m
2026-05-12 SVA985 HKG → RUH May 12, 18:40 UTCMay 12, 18:45 UTC5m
2026-05-12 SVA984 DMM → HKG May 12, 10:00 UTCMay 12, 15:30 UTC5h 30m
2026-05-10 SVA969 BOM → JED May 10, 16:30 UTCMay 10, 17:59 UTC1h 30m
2026-05-10 SVA969 BOM → JED May 10, 14:00 UTCMay 10, 14:09 UTC10m
2026-05-10 SVA968 JED → BOM May 10, 10:40 UTCMay 10, 11:05 UTC25m
2026-05-10 SVA968 JED → BOM May 10, 03:50 UTCMay 10, 08:54 UTC5h 5m
2026-05-08 SVA977 HKG → JED May 8, 15:15 UTCMay 8, 16:55 UTC1h 40m
2026-05-08 SVA977 HKG → JED May 8, 12:44 UTCMay 8, 12:55 UTC10m
2026-05-08 SVA976 RUH → HKG May 8, 08:59 UTCMay 8, 09:30 UTC30m
2026-05-07 SVA976 RUH → HKG May 7, 12:35 UTCMay 8, 06:50 UTC18h 15m
2026-05-07 SVA976 RUH → HKG May 7, 12:00 UTCMay 8, 06:50 UTC18h 50m
2026-05-07 SVA3915 - May 7, 06:40 UTCMay 7, 08:30 UTC1h 50m
2026-05-06 SVA932 LGG → RUH May 6, 02:10 UTCMay 6, 04:55 UTC2h 44m
2026-05-05 SVA931 JED → LGG May 5, 05:30 UTCMay 5, 22:40 UTC17h 10m
2026-05-05 SVA963 HKG → RUH May 5, 03:00 UTCMay 5, 03:10 UTC10m
2026-05-04 SVA962 RUH → HKG May 4, 20:40 UTCMay 4, 21:10 UTC30m
2026-05-04 SVA962 RUH → HKG May 4, 04:00 UTCMay 4, 18:45 UTC14h 46m
2026-05-03 SVA978 RUH → CAN May 3, 01:55 UTCMay 3, 19:45 UTC17h 49m
2026-05-02 SVA993 SZX → RUH May 2, 06:35 UTCMay 2, 20:55 UTC14h 20m
2026-05-02 SVA993 SZX → RUH May 2, 04:10 UTCMay 2, 04:25 UTC15m

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 .

Mode-S 710102 frequently asked

What is Mode-S code 710102?
710102 is an ICAO 24-bit transponder address. Allocated to Saudi Arabia. Assigned to HZ-AK73.
Where is Mode-S 710102 registered?
Mode-S code 710102 is allocated to Saudi Arabia (SA). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 710102 broadcasting right now?
No active broadcast right now. Last signal was 2h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 710102, octal 34200402, decimal 7,405,826.
What flights does 710102 operate?
Mode-S 710102 has broadcast 20 distinct callsigns, including SVA992, SVA978, SVA993, SVA980, SVA982.