sensors Mode-S transponder
7103D8
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AK42 · BOEING 777-300ER
- Hex
- 7103D8
- Octal
- 34201730
- Decimal
- 7,406,552
- Country
- SA
- Tail
- HZ-AK42
- Type
- B77W
- Flights observed
- 130
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 29m ago
Current position
Country allocation
The ICAO 24-bit address 7103D8 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 |
|---|---|---|---|
| SVA021 | Saudi Arabian Airlines | 17 | 2026-07-19 |
| SVA143 | - | 15 | 2026-06-24 |
| SVA020 | - | 14 | 2026-07-20 |
| SVA035 | - | 12 | 2026-06-30 |
| SVA121 | - | 10 | 2026-06-28 |
| SVA037 | Saudi Arabian Airlines | 9 | 2026-07-22 |
| SVA036 | - | 9 | 2026-06-30 |
| SVA111 | - | 7 | 2026-06-28 |
| SVA144 | - | 6 | 2026-06-25 |
| SVA038 | Saudi Arabian Airlines | 5 | 2026-07-23 |
| SVA110 | - | 4 | 2026-06-29 |
| SVA127 | Saudi Arabian Airlines | 3 | 2026-05-17 |
| SVA023 | Saudi Arabian Airlines | 3 | 2026-04-25 |
| SVA123 | - | 2 | 2026-07-10 |
| SVA122 | Saudi Arabian Airlines | 2 | 2026-05-04 |
| SVA119 | Saudi Arabian Airlines | 2 | 2026-05-12 |
| SVA595 | - | 1 | 2026-07-07 |
| SVA555 | Saudi Arabian Airlines | 1 | 2026-07-21 |
| SVA554 | - | 1 | 2026-07-21 |
| SVA379 | - | 1 | 2026-07-16 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-23 | SVA038 | IAD → RUH | Jul 23, 00:10 UTC | Jul 23, 09:45 UTC | 9h 35m |
| 2026-07-22 | SVA037 | RUH → IAD | Jul 22, 10:20 UTC | Jul 22, 21:30 UTC | 11h 10m |
| 2026-07-21 | SVA555 | DXB → RUH | Jul 21, 15:15 UTC | Jul 21, 16:05 UTC | 50m |
| 2026-07-21 | SVA554 | - | Jul 21, 11:25 UTC | Jul 21, 12:55 UTC | 1h 30m |
| 2026-07-20 | SVA020 | - | Jul 20, 02:15 UTC | Jul 20, 10:25 UTC | 8h 10m |
| 2026-07-19 | SVA021 | JED → JFK | Jul 19, 08:25 UTC | Jul 19, 18:30 UTC | 10h 5m |
| 2026-07-16 | SVA378 | CMN → JED | Jul 16, 18:19 UTC | Jul 16, 22:25 UTC | 4h 5m |
| 2026-07-16 | SVA379 | - | Jul 16, 12:20 UTC | Jul 16, 15:55 UTC | 3h 35m |
| 2026-07-12 | SVA372 | CMN → JED | Jul 12, 14:30 UTC | Jul 12, 18:25 UTC | 3h 55m |
| 2026-07-12 | SVA373 | - | Jul 12, 07:20 UTC | Jul 12, 11:25 UTC | 4h 5m |
| 2026-07-10 | SVA124 | - | Jul 10, 16:15 UTC | Jul 10, 20:40 UTC | 4h 25m |
| 2026-07-10 | SVA123 | - | Jul 10, 09:30 UTC | Jul 10, 13:15 UTC | 3h 45m |
| 2026-07-09 | SVA123 | - | Jul 9, 10:25 UTC | Jul 10, 10:00 UTC | 23h 35m |
| 2026-07-09 | SVA020 | - | Jul 9, 00:50 UTC | Jul 9, 10:30 UTC | 9h 40m |
| 2026-07-08 | SVA021 | - | Jul 8, 11:05 UTC | Jul 8, 21:25 UTC | 10h 20m |
| 2026-07-07 | SVA595 | - | Jul 7, 19:15 UTC | Jul 8, 08:00 UTC | 12h 45m |
| 2026-07-07 | SVA020 | - | Jul 7, 00:10 UTC | Jul 7, 17:15 UTC | 17h 5m |
| 2026-07-06 | SVA021 | - | Jul 6, 07:20 UTC | Jul 6, 19:05 UTC | 11h 45m |
| 2026-06-30 | SVA036 | - | Jun 30, 23:05 UTC | Jul 1, 07:50 UTC | 8h 45m |
| 2026-06-30 | SVA035 | - | Jun 30, 07:50 UTC | Jun 30, 18:55 UTC | 11h 5m |
| 2026-06-29 | SVA035 | - | Jun 29, 14:04 UTC | Jun 30, 12:50 UTC | 22h 46m |
| 2026-06-29 | SVA035 | - | Jun 29, 12:05 UTC | Jun 30, 12:00 UTC | 23h 56m |
| 2026-06-29 | SVA110 | - | Jun 29, 10:04 UTC | Jun 30, 10:00 UTC | 23h 56m |
| 2026-06-29 | SVA110 | - | Jun 29, 09:40 UTC | Jun 30, 08:00 UTC | 22h 21m |
| 2026-06-28 | SVA111 | - | Jun 28, 15:44 UTC | Jun 29, 05:54 UTC | 14h 10m |
| 2026-06-28 | SVA121 | - | Jun 28, 08:05 UTC | Jun 28, 12:39 UTC | 4h 35m |
| 2026-06-26 | SVA038 | IAD → TUI | Jun 26, 23:15 UTC | Jun 27, 09:29 UTC | 10h 15m |
| 2026-06-26 | SVA037 | - | Jun 26, 08:00 UTC | Jun 26, 19:39 UTC | 11h 40m |
| 2026-06-25 | SVA037 | - | Jun 25, 14:04 UTC | Jun 26, 13:10 UTC | 23h 5m |
| 2026-06-25 | SVA037 | - | Jun 25, 12:04 UTC | Jun 26, 12:00 UTC | 23h 55m |
| 2026-06-25 | SVA144 | - | Jun 25, 10:04 UTC | Jun 26, 09:59 UTC | 23h 55m |
| 2026-06-24 | SVA143 | CDG → CDG | Jun 24, 10:25 UTC | Jun 25, 05:09 UTC | 18h 45m |
| 2026-06-24 | SVA143 | - | Jun 24, 00:34 UTC | Jun 24, 05:05 UTC | 4h 30m |
| 2026-06-19 | SVA038 | IAD → TUI | Jun 19, 23:09 UTC | Jun 20, 09:44 UTC | 10h 35m |
| 2026-06-19 | SVA037 | - | Jun 19, 07:39 UTC | Jun 19, 19:39 UTC | 12h 0m |
| 2026-06-18 | SVA038 | - | Jun 18, 08:05 UTC | Jun 19, 07:59 UTC | 23h 54m |
| 2026-06-17 | SVA038 | - | Jun 17, 23:20 UTC | Jun 18, 09:15 UTC | 9h 55m |
| 2026-06-17 | SVA037 | - | Jun 17, 07:25 UTC | Jun 17, 19:10 UTC | 11h 45m |
| 2026-06-16 | SVA037 | - | Jun 16, 18:05 UTC | Jun 17, 18:00 UTC | 23h 56m |
| 2026-06-16 | SVA037 | - | Jun 16, 16:05 UTC | Jun 17, 14:00 UTC | 21h 56m |
| 2026-06-16 | SVA037 | - | Jun 16, 15:35 UTC | Jun 17, 14:00 UTC | 22h 26m |
| 2026-06-16 | SVA121 | - | Jun 16, 08:05 UTC | Jun 16, 12:39 UTC | 4h 35m |
| 2026-06-15 | SVA121 | - | Jun 15, 12:05 UTC | Jun 16, 12:00 UTC | 23h 55m |
| 2026-06-15 | SVA110 | - | Jun 15, 10:05 UTC | Jun 16, 10:00 UTC | 23h 55m |
| 2026-06-15 | SVA110 | - | Jun 15, 09:45 UTC | Jun 15, 13:54 UTC | 4h 10m |
| 2026-06-14 | SVA111 | - | Jun 14, 15:40 UTC | Jun 15, 06:20 UTC | 14h 40m |
| 2026-06-13 | SVA121 | - | Jun 13, 18:05 UTC | Jun 14, 13:05 UTC | 19h 1m |
| 2026-06-13 | SVA121 | - | Jun 13, 16:05 UTC | Jun 14, 13:05 UTC | 21h 0m |
| 2026-06-13 | SVA121 | - | Jun 13, 15:40 UTC | Jun 14, 13:05 UTC | 21h 25m |
| 2026-06-13 | SVA121 | - | Jun 13, 07:55 UTC | Jun 13, 13:05 UTC | 5h 10m |
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-AK42 page for operator, model, and routing details .