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