sensors Mode-S transponder
710100
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AK71 · BOEING 777-200LR
- Hex
- 710100
- Octal
- 34200400
- Decimal
- 7,405,824
- Country
- SA
- Tail
- HZ-AK71
- Type
- B77L
- Flights observed
- 197
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 6h ago
Last known position
Country allocation
The ICAO 24-bit address 710100 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 |
|---|---|---|---|
| SVA982 | - | 20 | 2026-07-17 |
| SVA983 | - | 15 | 2026-07-17 |
| SVA992 | - | 13 | 2026-07-16 |
| SVA978 | - | 12 | 2026-07-12 |
| SVA993 | - | 11 | 2026-07-16 |
| SVA987 | - | 11 | 2026-07-04 |
| SVA972 | - | 10 | 2026-07-11 |
| SVA986 | - | 9 | 2026-07-04 |
| SVA973 | - | 8 | 2026-07-11 |
| SVA962 | - | 8 | 2026-07-13 |
| SVA969 | - | 6 | 2026-06-29 |
| SVA3031 | Saudi Arabian Airlines | 6 | 2026-04-25 |
| SVA918 | Saudi Arabian Airlines | 5 | 2026-05-24 |
| SVA917 | - | 5 | 2026-07-12 |
| SVA3048 | - | 5 | 2026-06-30 |
| SVA984 | Saudi Arabian Airlines | 4 | 2026-06-02 |
| SVA968 | - | 4 | 2026-06-28 |
| SVA924 | Saudi Arabian Airlines | 4 | 2026-06-22 |
| SVA923 | Saudi Arabian Airlines | 4 | 2026-07-05 |
| SVA3033 | Saudi Arabian Airlines | 4 | 2026-04-24 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | SVA983 | - | Jul 17, 22:55 UTC | Jul 18, 02:14 UTC | 3h 20m |
| 2026-07-17 | SVA983 | - | Jul 17, 20:44 UTC | Jul 17, 21:00 UTC | 15m |
| 2026-07-17 | SVA982 | - | Jul 17, 17:50 UTC | Jul 17, 18:25 UTC | 35m |
| 2026-07-17 | SVA982 | - | Jul 17, 00:35 UTC | Jul 17, 16:04 UTC | 15h 30m |
| 2026-07-16 | SVA993 | - | Jul 16, 22:35 UTC | Jul 16, 22:49 UTC | 15m |
| 2026-07-16 | SVA992 | - | Jul 16, 12:30 UTC | Jul 16, 18:34 UTC | 6h 5m |
| 2026-07-15 | SVA932 | - | Jul 15, 03:40 UTC | Jul 15, 07:05 UTC | 3h 25m |
| 2026-07-14 | SVA931 | JED → LGG | Jul 14, 09:05 UTC | Jul 15, 00:15 UTC | 15h 9m |
| 2026-07-14 | SVA963 | - | Jul 14, 07:05 UTC | Jul 14, 07:15 UTC | 10m |
| 2026-07-13 | SVA962 | - | Jul 13, 11:10 UTC | Jul 14, 05:05 UTC | 17h 55m |
| 2026-07-13 | SVA979 | - | Jul 13, 08:30 UTC | Jul 14, 05:05 UTC | 20h 35m |
| 2026-07-12 | SVA978 | - | Jul 12, 10:05 UTC | Jul 13, 02:30 UTC | 16h 25m |
| 2026-07-12 | SVA917 | - | Jul 12, 02:40 UTC | Jul 12, 05:50 UTC | 3h 10m |
| 2026-07-11 | SVA973 | - | Jul 11, 14:10 UTC | Jul 12, 02:35 UTC | 12h 25m |
| 2026-07-11 | SVA973 | - | Jul 11, 12:10 UTC | Jul 11, 12:20 UTC | 10m |
| 2026-07-11 | SVA972 | - | Jul 11, 09:30 UTC | Jul 11, 10:10 UTC | 40m |
| 2026-07-10 | SVA972 | - | Jul 10, 14:25 UTC | Jul 11, 07:15 UTC | 16h 51m |
| 2026-07-10 | SVA993 | - | Jul 10, 09:55 UTC | Jul 10, 14:20 UTC | 4h 25m |
| 2026-07-10 | SVA993 | - | Jul 10, 08:00 UTC | Jul 10, 08:10 UTC | 10m |
| 2026-07-09 | SVA992 | - | Jul 9, 10:00 UTC | Jul 10, 03:15 UTC | 17h 15m |
| 2026-07-08 | SVA978 | - | Jul 8, 23:00 UTC | Jul 9, 05:15 UTC | 6h 15m |
| 2026-07-08 | SVA978 | RUH → CAN | Jul 8, 02:05 UTC | Jul 9, 00:10 UTC | 22h 5m |
| 2026-07-07 | SVA983 | - | Jul 7, 19:25 UTC | Jul 8, 02:15 UTC | 6h 50m |
| 2026-07-07 | SVA983 | - | Jul 7, 18:35 UTC | Jul 7, 18:50 UTC | 15m |
| 2026-07-07 | SVA982 | - | Jul 7, 07:50 UTC | Jul 7, 16:25 UTC | 8h 35m |
| 2026-07-06 | SVA982 | - | Jul 6, 20:05 UTC | Jul 7, 16:25 UTC | 20h 20m |
| 2026-07-06 | SVA982 | - | Jul 6, 18:05 UTC | Jul 7, 16:25 UTC | 22h 20m |
| 2026-07-06 | SVA982 | - | Jul 6, 17:30 UTC | Jul 7, 16:00 UTC | 22h 30m |
| 2026-07-05 | SVA923 | JED → BRU | Jul 5, 21:25 UTC | Jul 6, 13:30 UTC | 16h 5m |
| 2026-07-05 | SVA983 | - | Jul 5, 20:35 UTC | Jul 5, 20:45 UTC | 10m |
| 2026-07-05 | SVA982 | - | Jul 5, 18:00 UTC | Jul 5, 18:20 UTC | 20m |
| 2026-07-04 | SVA982 | - | Jul 4, 22:50 UTC | Jul 5, 16:25 UTC | 17h 35m |
| 2026-07-04 | SVA982 | - | Jul 4, 20:05 UTC | Jul 5, 16:25 UTC | 20h 20m |
| 2026-07-04 | SVA987 | - | Jul 4, 17:55 UTC | Jul 4, 18:10 UTC | 15m |
| 2026-07-04 | SVA986 | - | Jul 4, 14:40 UTC | Jul 4, 15:05 UTC | 25m |
| 2026-07-03 | SVA986 | - | Jul 3, 21:50 UTC | Jul 4, 14:00 UTC | 16h 10m |
| 2026-07-03 | SVA983 | - | Jul 3, 19:45 UTC | Jul 3, 20:00 UTC | 15m |
| 2026-07-02 | SVA982 | - | Jul 2, 23:30 UTC | Jul 3, 17:05 UTC | 17h 35m |
| 2026-07-02 | SVA982 | - | Jul 2, 20:05 UTC | Jul 3, 17:05 UTC | 21h 0m |
| 2026-07-02 | SVA982 | - | Jul 2, 19:05 UTC | Jul 3, 17:05 UTC | 22h 0m |
| 2026-07-02 | SVA987 | - | Jul 2, 17:40 UTC | Jul 3, 14:00 UTC | 20h 20m |
| 2026-07-02 | SVA987 | - | Jul 2, 16:55 UTC | Jul 2, 17:05 UTC | 10m |
| 2026-07-02 | SVA986 | - | Jul 2, 07:00 UTC | Jul 2, 12:30 UTC | 5h 30m |
| 2026-06-30 | SVA3048 | - | Jun 30, 11:35 UTC | Jul 1, 05:30 UTC | 17h 55m |
| 2026-06-30 | SVA3048 | - | Jun 30, 02:30 UTC | Jul 1, 01:20 UTC | 22h 50m |
| 2026-06-30 | SVA3048 | - | Jun 30, 00:04 UTC | Jul 1, 00:00 UTC | 23h 56m |
| 2026-06-29 | SVA3048 | - | Jun 29, 22:55 UTC | Jun 30, 18:30 UTC | 19h 35m |
| 2026-06-29 | SVA993 | - | Jun 29, 22:00 UTC | Jun 29, 22:10 UTC | 10m |
| 2026-06-29 | SVA992 | RUH → SZX | Jun 29, 04:00 UTC | Jun 29, 18:10 UTC | 14h 10m |
| 2026-06-29 | SVA969 | - | Jun 29, 01:05 UTC | Jun 29, 01:20 UTC | 15m |
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-AK71 page for operator, model, and routing details .