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

Last known position

Most recent position reported by Mode-S 710101.

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

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-06-02 SVA932 LGG → RUH Jun 2, 22:35 UTCJun 3, 01:35 UTC3h 0m
2026-06-02 SVA931 JED → LGG Jun 2, 19:05 UTCJun 2, 19:15 UTC10m
2026-06-02 SVA931 JED → LGG Jun 2, 00:30 UTCJun 2, 16:20 UTC15h 50m
2026-06-01 SVA963 HKG → RUH Jun 1, 23:45 UTCJun 2, 00:00 UTC15m
2026-06-01 SVA962 RUH → HKG Jun 1, 20:25 UTCJun 1, 20:50 UTC25m
2026-06-01 SVA962 RUH → HKG Jun 1, 14:55 UTCJun 1, 18:20 UTC3h 25m
2026-05-30 SVA986 RUH → HKG May 30, 02:45 UTCMay 30, 21:45 UTC19h 0m
2026-05-29 SVA982 RUH → HKG May 29, 23:20 UTCMay 29, 23:50 UTC30m
2026-05-29 SVA982 RUH → HKG May 29, 16:05 UTCMay 29, 21:25 UTC5h 20m
2026-05-28 SVA979 CAN → RUH May 28, 03:50 UTCMay 28, 08:45 UTC4h 55m
2026-05-27 SVA978 RUH → CAN May 27, 08:15 UTCMay 27, 22:15 UTC14h 0m
2026-05-27 SVA985 HKG → RUH May 27, 05:55 UTCMay 27, 06:09 UTC15m
2026-05-26 SVA984 DMM → HKG May 26, 00:35 UTCMay 26, 15:35 UTC15h 0m
2026-05-25 SVA969 BOM → JED May 25, 20:15 UTCMay 25, 20:30 UTC15m
2026-05-25 SVA969 BOM → JED May 25, 17:30 UTCMay 25, 17:50 UTC20m
2026-05-25 SVA969 BOM → JED May 25, 15:10 UTCMay 25, 15:25 UTC15m
2026-05-25 SVA968 JED → BOM May 25, 11:55 UTCMay 25, 12:35 UTC40m
2026-05-25 SVA968 JED → BOM May 25, 04:25 UTCMay 25, 09:50 UTC5h 25m
2026-05-23 SVA987 HKG → RUH May 23, 20:25 UTCMay 24, 01:55 UTC5h 30m
2026-05-23 SVA987 HKG → RUH May 23, 18:00 UTCMay 23, 18:10 UTC10m
2026-05-22 SVA986 RUH → HKG May 22, 22:55 UTCMay 23, 14:55 UTC15h 59m
2026-05-22 SVA983 HKG → RUH May 22, 20:05 UTCMay 22, 20:20 UTC15m
2026-05-21 SVA982 RUH → HKG May 21, 20:20 UTCMay 22, 15:35 UTC19h 15m
2026-05-21 SVA982 RUH → HKG May 21, 19:45 UTCMay 22, 15:35 UTC19h 50m
2026-05-21 SVA987 HKG → RUH May 21, 17:20 UTCMay 21, 17:35 UTC15m
2026-05-21 SVA986 RUH → HKG May 21, 14:00 UTCMay 21, 14:35 UTC35m
2026-05-20 SVA981 HKG → RUH May 20, 19:25 UTCMay 21, 12:05 UTC16h 40m
2026-05-20 SVA980 RUH → HKG May 20, 15:40 UTCMay 20, 15:55 UTC15m
2026-05-20 SVA980 RUH → HKG May 20, 07:35 UTCMay 20, 12:30 UTC4h 55m
2026-05-18 SVA924 MST → JED May 18, 18:50 UTCMay 18, 22:25 UTC3h 35m
2026-05-18 SVA923 JED → BRU May 18, 01:00 UTCMay 18, 15:10 UTC14h 10m
2026-05-17 SVA983 HKG → RUH May 17, 22:15 UTCMay 17, 22:30 UTC15m
2026-05-17 SVA982 RUH → HKG May 17, 18:40 UTCMay 17, 19:05 UTC25m
2026-05-16 SVA979 CAN → RUH May 16, 23:55 UTCMay 17, 16:35 UTC16h 40m
2026-05-16 SVA979 CAN → RUH May 16, 21:25 UTCMay 16, 21:35 UTC10m
2026-05-16 SVA978 RUH → CAN May 16, 00:15 UTCMay 16, 16:20 UTC16h 6m
2026-05-15 SVA993 SZX → RUH May 15, 21:45 UTCMay 15, 22:00 UTC15m
2026-05-14 SVA992 RUH → SZX May 14, 23:50 UTCMay 15, 16:30 UTC16h 39m
2026-05-14 SVA993 SZX → RUH May 14, 21:10 UTCMay 14, 21:25 UTC15m
2026-05-14 SVA992 RUH → SZX May 14, 10:50 UTCMay 14, 15:50 UTC5h 0m
2026-05-12 SVA932 LGG → RUH May 12, 22:45 UTCMay 13, 02:15 UTC3h 30m
2026-05-12 SVA931 JED → LGG May 12, 02:45 UTCMay 12, 19:10 UTC16h 25m
2026-05-11 SVA962 RUH → HKG May 11, 03:15 UTCMay 11, 21:00 UTC17h 46m
2026-05-11 SVA962 RUH → HKG May 11, 00:40 UTCMay 11, 21:00 UTC20h 21m
2026-05-10 SVA978 RUH → CAN May 10, 00:20 UTCMay 10, 19:45 UTC19h 25m
2026-05-09 SVA979 CAN → RUH May 9, 23:55 UTCMay 10, 19:45 UTC19h 50m
2026-05-09 SVA978 RUH → CAN May 9, 00:10 UTCMay 9, 16:05 UTC15h 55m
2026-05-08 SVA993 SZX → RUH May 8, 21:30 UTCMay 8, 21:40 UTC10m
2026-05-08 SVA992 RUH → SZX May 8, 00:20 UTCMay 8, 16:30 UTC16h 10m
2026-05-07 SVA993 SZX → RUH May 7, 21:50 UTCMay 7, 22:05 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-AK72 page for operator, model, and routing details .

Mode-S 710101 frequently asked

What is Mode-S code 710101?
710101 is an ICAO 24-bit transponder address. Allocated to Saudi Arabia. Assigned to HZ-AK72.
Where is Mode-S 710101 registered?
Mode-S code 710101 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 710101 broadcasting right now?
No active broadcast right now. Last signal was 1h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 710101, octal 34200401, decimal 7,405,825.
What flights does 710101 operate?
Mode-S 710101 has broadcast 20 distinct callsigns, including SVA992, SVA987, SVA982, SVA986, SVA993.