sensors Mode-S transponder
710121
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AK43 · BOEING 777-300ER
- Hex
- 710121
- Octal
- 34200441
- Decimal
- 7,405,857
- Country
- SA
- Tail
- HZ-AK43
- Type
- B77W
- Flights observed
- 150
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 16h ago
Last known position
Country allocation
The ICAO 24-bit address 710121 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 |
|---|---|---|---|
| SVA143 | Saudi Arabian Airlines | 19 | 2026-05-19 |
| SVA020 | - | 17 | 2026-07-05 |
| SVA023 | - | 15 | 2026-06-18 |
| SVA021 | - | 15 | 2026-07-04 |
| SVA035 | - | 10 | 2026-06-14 |
| SVA022 | - | 10 | 2026-06-18 |
| SVA037 | Saudi Arabian Airlines | 8 | 2026-05-08 |
| SVA121 | - | 7 | 2026-06-19 |
| SVA111 | - | 7 | 2026-06-21 |
| SVA144 | Saudi Arabian Airlines | 6 | 2026-05-19 |
| SVA038 | Saudi Arabian Airlines | 6 | 2026-05-09 |
| SVA041 | Saudi Arabian Airlines | 4 | 2026-06-08 |
| SVA036 | Saudi Arabian Airlines | 4 | 2026-06-14 |
| SVA379 | - | 3 | 2026-07-12 |
| SVA042 | Saudi Arabian Airlines | 3 | 2026-06-09 |
| SVA122 | Saudi Arabian Airlines | 2 | 2026-05-17 |
| SVA595 | - | 1 | 2026-07-05 |
| SVA378 | - | 1 | 2026-07-12 |
| SVA377 | - | 1 | 2026-06-26 |
| SVA376 | - | 1 | 2026-06-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | SVA372 | CMN → JED | Jul 13, 14:00 UTC | Jul 13, 18:20 UTC | 4h 20m |
| 2026-07-13 | SVA373 | - | Jul 13, 08:01 UTC | Jul 13, 11:25 UTC | 3h 25m |
| 2026-07-12 | SVA378 | - | Jul 12, 18:45 UTC | Jul 13, 07:55 UTC | 13h 10m |
| 2026-07-12 | SVA379 | - | Jul 12, 11:35 UTC | Jul 12, 16:01 UTC | 4h 25m |
| 2026-07-11 | SVA379 | - | Jul 11, 18:50 UTC | Jul 12, 16:01 UTC | 21h 10m |
| 2026-07-11 | SVA379 | - | Jul 11, 16:20 UTC | Jul 12, 16:01 UTC | 23h 40m |
| 2026-07-11 | SVA228 | BCN → JED | Jul 11, 16:00 UTC | Jul 12, 14:05 UTC | 22h 5m |
| 2026-07-11 | SVA229 | - | Jul 11, 09:45 UTC | Jul 11, 13:05 UTC | 3h 20m |
| 2026-07-05 | SVA595 | - | Jul 5, 19:15 UTC | Jul 5, 20:05 UTC | 50m |
| 2026-07-05 | SVA020 | - | Jul 5, 04:50 UTC | Jul 5, 17:30 UTC | 12h 40m |
| 2026-07-05 | SVA020 | - | Jul 5, 00:10 UTC | Jul 5, 01:25 UTC | 1h 15m |
| 2026-07-04 | SVA021 | - | Jul 4, 07:25 UTC | Jul 4, 18:30 UTC | 11h 5m |
| 2026-07-03 | SVA021 | - | Jul 3, 08:20 UTC | Jul 4, 07:50 UTC | 23h 30m |
| 2026-07-02 | SVA020 | - | Jul 2, 23:40 UTC | Jul 3, 08:55 UTC | 9h 15m |
| 2026-07-02 | SVA021 | - | Jul 2, 07:20 UTC | Jul 2, 18:50 UTC | 11h 30m |
| 2026-07-01 | SVA021 | - | Jul 1, 08:20 UTC | Jul 2, 07:50 UTC | 23h 30m |
| 2026-06-30 | SVA020 | - | Jun 30, 23:35 UTC | Jul 1, 08:20 UTC | 8h 45m |
| 2026-06-30 | SVA021 | - | Jun 30, 07:20 UTC | Jun 30, 18:05 UTC | 10h 45m |
| 2026-06-26 | SVA376 | - | Jun 26, 07:14 UTC | Jun 26, 11:09 UTC | 3h 55m |
| 2026-06-26 | SVA377 | - | Jun 26, 01:24 UTC | Jun 26, 04:50 UTC | 3h 25m |
| 2026-06-22 | SVA110 | - | Jun 22, 09:49 UTC | Jun 22, 14:14 UTC | 4h 25m |
| 2026-06-21 | SVA111 | - | Jun 21, 10:19 UTC | Jun 22, 06:05 UTC | 19h 45m |
| 2026-06-21 | SVA111 | - | Jun 21, 09:24 UTC | Jun 22, 06:05 UTC | 20h 40m |
| 2026-06-20 | SVA111 | - | Jun 20, 16:05 UTC | Jun 21, 06:10 UTC | 14h 5m |
| 2026-06-19 | SVA121 | - | Jun 19, 18:20 UTC | Jun 20, 13:19 UTC | 19h 0m |
| 2026-06-19 | SVA121 | - | Jun 19, 15:49 UTC | Jun 20, 13:19 UTC | 21h 30m |
| 2026-06-18 | SVA121 | - | Jun 18, 21:35 UTC | Jun 19, 12:25 UTC | 14h 49m |
| 2026-06-18 | SVA022 | JFK → LHR | Jun 18, 16:40 UTC | Jun 19, 12:25 UTC | 19h 44m |
| 2026-06-18 | SVA023 | - | Jun 18, 02:10 UTC | Jun 18, 13:35 UTC | 11h 25m |
| 2026-06-14 | SVA036 | IAD → JED | Jun 14, 23:10 UTC | Jun 15, 08:00 UTC | 8h 50m |
| 2026-06-14 | SVA035 | - | Jun 14, 07:55 UTC | Jun 14, 19:20 UTC | 11h 25m |
| 2026-06-13 | SVA020 | JFK → JED | Jun 13, 08:20 UTC | Jun 14, 08:15 UTC | 23h 55m |
| 2026-06-13 | SVA020 | JFK → JED | Jun 13, 00:00 UTC | Jun 13, 09:15 UTC | 9h 14m |
| 2026-06-12 | SVA021 | - | Jun 12, 07:40 UTC | Jun 12, 18:45 UTC | 11h 5m |
| 2026-06-10 | SVA020 | JFK → JED | Jun 10, 23:30 UTC | Jun 11, 08:10 UTC | 8h 40m |
| 2026-06-10 | SVA021 | JED → JFK | Jun 10, 08:25 UTC | Jun 10, 18:45 UTC | 10h 20m |
| 2026-06-09 | SVA021 | JED → JFK | Jun 9, 14:20 UTC | Jun 10, 14:00 UTC | 23h 40m |
| 2026-06-09 | SVA021 | JED → JFK | Jun 9, 12:45 UTC | Jun 10, 12:15 UTC | 23h 30m |
| 2026-06-09 | SVA042 | LAX → JED | Jun 9, 04:25 UTC | Jun 9, 15:50 UTC | 11h 25m |
| 2026-06-08 | SVA041 | JED → LAX | Jun 8, 09:05 UTC | Jun 8, 23:00 UTC | 13h 55m |
| 2026-06-07 | SVA041 | JED → LAX | Jun 7, 16:20 UTC | Jun 8, 14:35 UTC | 22h 15m |
| 2026-06-07 | SVA041 | JED → LAX | Jun 7, 14:20 UTC | Jun 8, 14:15 UTC | 23h 55m |
| 2026-06-07 | SVA042 | LAX → JED | Jun 7, 13:25 UTC | Jun 8, 12:15 UTC | 22h 50m |
| 2026-06-07 | SVA042 | LAX → JED | Jun 7, 04:25 UTC | Jun 7, 17:30 UTC | 13h 5m |
| 2026-06-06 | SVA041 | JED → LAX | Jun 6, 08:15 UTC | Jun 6, 22:34 UTC | 14h 20m |
| 2026-06-02 | SVA036 | IAD → JED | Jun 2, 23:35 UTC | Jun 3, 08:15 UTC | 8h 40m |
| 2026-06-02 | SVA035 | JED → IAD | Jun 2, 07:50 UTC | Jun 2, 19:15 UTC | 11h 25m |
| 2026-06-01 | SVA035 | JED → IAD | Jun 1, 08:45 UTC | Jun 2, 08:15 UTC | 23h 30m |
| 2026-05-31 | SVA036 | IAD → JED | May 31, 23:00 UTC | Jun 1, 08:45 UTC | 9h 45m |
| 2026-05-31 | SVA035 | JED → IAD | May 31, 08:25 UTC | May 31, 19:25 UTC | 11h 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-AK43 page for operator, model, and routing details .