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
- 80
- Distinct callsigns
- 14
- Country
- SA
- Last broadcast
- 1d ago
Last known 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 14 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| SVA021 | Saudi Arabian Airlines | 14 | 2026-06-05 |
| SVA143 | Saudi Arabian Airlines | 13 | 2026-06-03 |
| SVA020 | Saudi Arabian Airlines | 11 | 2026-06-06 |
| SVA035 | Saudi Arabian Airlines | 9 | 2026-05-30 |
| SVA036 | Saudi Arabian Airlines | 8 | 2026-05-31 |
| SVA144 | Saudi Arabian Airlines | 5 | 2026-06-03 |
| SVA111 | Saudi Arabian Airlines | 5 | 2026-05-08 |
| SVA127 | Saudi Arabian Airlines | 3 | 2026-05-17 |
| SVA121 | Saudi Arabian Airlines | 3 | 2026-05-04 |
| SVA023 | Saudi Arabian Airlines | 3 | 2026-04-25 |
| SVA122 | Saudi Arabian Airlines | 2 | 2026-05-04 |
| SVA119 | Saudi Arabian Airlines | 2 | 2026-05-12 |
| SVA108 | - | 1 | 2026-04-12 |
| SVA022 | Saudi Arabian Airlines | 1 | 2026-04-25 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-06 | SVA020 | JFK → JED | Jun 6, 00:10 UTC | Jun 6, 09:24 UTC | 9h 15m |
| 2026-06-05 | SVA021 | JED → JFK | Jun 5, 07:30 UTC | Jun 5, 18:40 UTC | 11h 10m |
| 2026-06-03 | SVA144 | CDG → RUH | Jun 3, 10:10 UTC | Jun 3, 13:00 UTC | 2h 50m |
| 2026-06-03 | SVA143 | RUH → CDG | Jun 3, 01:10 UTC | Jun 3, 05:10 UTC | 4h 0m |
| 2026-06-02 | SVA143 | RUH → CDG | Jun 2, 08:05 UTC | Jun 3, 05:10 UTC | 21h 5m |
| 2026-06-02 | SVA143 | RUH → CDG | Jun 2, 06:05 UTC | Jun 3, 05:10 UTC | 23h 5m |
| 2026-06-02 | SVA020 | JFK → JED | Jun 2, 05:55 UTC | Jun 3, 04:00 UTC | 22h 5m |
| 2026-06-02 | SVA020 | JFK → JED | Jun 2, 02:05 UTC | Jun 3, 02:00 UTC | 23h 55m |
| 2026-06-02 | SVA020 | JFK → JED | Jun 2, 00:55 UTC | Jun 2, 09:50 UTC | 8h 55m |
| 2026-06-01 | SVA021 | JED → JFK | Jun 1, 07:40 UTC | Jun 1, 18:50 UTC | 11h 10m |
| 2026-05-31 | SVA021 | JED → JFK | May 31, 14:20 UTC | Jun 1, 14:00 UTC | 23h 40m |
| 2026-05-31 | SVA021 | JED → JFK | May 31, 12:05 UTC | Jun 1, 12:00 UTC | 23h 55m |
| 2026-05-31 | SVA036 | IAD → JED | May 31, 10:05 UTC | Jun 1, 10:00 UTC | 23h 55m |
| 2026-05-31 | SVA036 | IAD → JED | May 31, 00:15 UTC | May 31, 14:20 UTC | 14h 5m |
| 2026-05-30 | SVA036 | IAD → JED | May 30, 18:05 UTC | May 31, 14:20 UTC | 20h 15m |
| 2026-05-30 | SVA035 | JED → IAD | May 30, 16:05 UTC | May 31, 14:20 UTC | 22h 15m |
| 2026-05-30 | SVA035 | JED → IAD | May 30, 14:50 UTC | May 31, 13:55 UTC | 23h 5m |
| 2026-05-28 | SVA020 | JFK → JED | May 28, 03:30 UTC | May 28, 13:00 UTC | 9h 30m |
| 2026-05-27 | SVA021 | JED → JFK | May 27, 07:10 UTC | May 27, 18:05 UTC | 10h 55m |
| 2026-05-26 | SVA020 | JFK → JED | May 26, 08:04 UTC | May 27, 07:45 UTC | 23h 40m |
| 2026-05-26 | SVA020 | JFK → JED | May 26, 00:29 UTC | May 26, 09:29 UTC | 9h 0m |
| 2026-05-25 | SVA021 | JED → JFK | May 25, 07:15 UTC | May 25, 18:10 UTC | 10h 55m |
| 2026-05-24 | SVA021 | JED → JFK | May 24, 08:05 UTC | May 25, 07:45 UTC | 23h 40m |
| 2026-05-23 | SVA036 | IAD → JED | May 23, 23:05 UTC | May 24, 08:55 UTC | 9h 50m |
| 2026-05-23 | SVA035 | JED → IAD | May 23, 09:20 UTC | May 23, 19:40 UTC | 10h 21m |
| 2026-05-21 | SVA036 | IAD → JED | May 21, 23:15 UTC | May 22, 08:05 UTC | 8h 50m |
| 2026-05-21 | SVA035 | JED → IAD | May 21, 07:55 UTC | May 21, 19:50 UTC | 11h 55m |
| 2026-05-20 | SVA035 | JED → IAD | May 20, 08:05 UTC | May 21, 08:00 UTC | 23h 55m |
| 2026-05-19 | SVA036 | IAD → JED | May 19, 23:10 UTC | May 20, 08:40 UTC | 9h 31m |
| 2026-05-19 | SVA035 | JED → IAD | May 19, 07:50 UTC | May 19, 19:30 UTC | 11h 40m |
| 2026-05-18 | SVA035 | JED → IAD | May 18, 16:05 UTC | May 19, 13:15 UTC | 21h 9m |
| 2026-05-18 | SVA035 | JED → IAD | May 18, 14:15 UTC | May 19, 13:15 UTC | 22h 59m |
| 2026-05-17 | SVA127 | JED → CDG | May 17, 16:05 UTC | May 18, 12:00 UTC | 19h 55m |
| 2026-05-17 | SVA127 | JED → CDG | May 17, 15:25 UTC | May 18, 12:00 UTC | 20h 35m |
| 2026-05-16 | SVA127 | JED → CDG | May 16, 21:40 UTC | May 17, 13:15 UTC | 15h 35m |
| 2026-05-16 | SVA020 | JFK → JED | May 16, 00:05 UTC | May 16, 19:30 UTC | 19h 26m |
| 2026-05-15 | SVA020 | JFK → JED | May 15, 23:40 UTC | May 16, 19:30 UTC | 19h 51m |
| 2026-05-15 | SVA021 | JED → JFK | May 15, 07:50 UTC | May 15, 19:05 UTC | 11h 14m |
| 2026-05-14 | SVA021 | JED → JFK | May 14, 08:15 UTC | May 15, 08:00 UTC | 23h 45m |
| 2026-05-13 | SVA020 | JFK → JED | May 13, 23:55 UTC | May 14, 08:15 UTC | 8h 20m |
| 2026-05-13 | SVA021 | JED → JFK | May 13, 09:00 UTC | May 13, 19:35 UTC | 10h 35m |
| 2026-05-12 | SVA021 | JED → JFK | May 12, 16:05 UTC | May 13, 13:20 UTC | 21h 15m |
| 2026-05-12 | SVA021 | JED → JFK | May 12, 14:05 UTC | May 13, 13:20 UTC | 23h 15m |
| 2026-05-12 | SVA119 | JED → LHR | May 12, 07:20 UTC | May 12, 11:40 UTC | 4h 20m |
| 2026-05-11 | SVA119 | JED → LHR | May 11, 08:05 UTC | May 12, 08:00 UTC | 23h 55m |
| 2026-05-10 | SVA020 | JFK → JED | May 10, 23:35 UTC | May 11, 08:50 UTC | 9h 15m |
| 2026-05-10 | SVA021 | JED → JFK | May 10, 07:30 UTC | May 10, 18:39 UTC | 11h 10m |
| 2026-05-09 | SVA021 | JED → JFK | May 9, 12:05 UTC | May 10, 12:00 UTC | 23h 55m |
| 2026-05-09 | SVA144 | CDG → RUH | May 9, 10:05 UTC | May 10, 10:00 UTC | 23h 55m |
| 2026-05-09 | SVA144 | CDG → RUH | May 9, 09:45 UTC | May 10, 08:00 UTC | 22h 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-AK42 page for operator, model, and routing details .