sensors Mode-S transponder
7100C8
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AK36 · BOEING 777-300ER
- Hex
- 7100C8
- Octal
- 34200310
- Decimal
- 7,405,768
- Country
- SA
- Tail
- HZ-AK36
- Type
- B77W
- Flights observed
- 146
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 9h ago
Last known position
Country allocation
The ICAO 24-bit address 7100C8 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 | - | 32 | 2026-07-14 |
| SVA020 | - | 20 | 2026-07-15 |
| SVA037 | Saudi Arabian Airlines | 12 | 2026-06-01 |
| SVA023 | Saudi Arabian Airlines | 12 | 2026-06-11 |
| SVA041 | Saudi Arabian Airlines | 8 | 2026-06-29 |
| SVA038 | Saudi Arabian Airlines | 8 | 2026-06-02 |
| SVA143 | Saudi Arabian Airlines | 7 | 2026-05-27 |
| SVA111 | Saudi Arabian Airlines | 7 | 2026-06-03 |
| SVA042 | Saudi Arabian Airlines | 7 | 2026-06-30 |
| SVA035 | - | 6 | 2026-06-20 |
| SVA122 | Saudi Arabian Airlines | 5 | 2026-05-24 |
| SVA022 | Saudi Arabian Airlines | 5 | 2026-06-11 |
| SVA121 | Saudi Arabian Airlines | 4 | 2026-06-04 |
| SVA036 | - | 4 | 2026-06-20 |
| SVA144 | Saudi Arabian Airlines | 2 | 2026-04-25 |
| SVA119 | Saudi Arabian Airlines | 2 | 2026-05-04 |
| SVA110 | Saudi Arabian Airlines | 2 | 2026-05-22 |
| SVA124 | - | 1 | 2026-07-17 |
| SVA123 | - | 1 | 2026-07-17 |
| SVA109 | Saudi Arabian Airlines | 1 | 2026-05-30 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | SVA124 | - | Jul 17, 16:29 UTC | Jul 17, 19:55 UTC | 3h 25m |
| 2026-07-17 | SVA123 | - | Jul 17, 09:30 UTC | Jul 17, 13:15 UTC | 3h 45m |
| 2026-07-15 | SVA020 | - | Jul 15, 00:05 UTC | Jul 15, 09:30 UTC | 9h 25m |
| 2026-07-14 | SVA021 | - | Jul 14, 07:20 UTC | Jul 14, 18:20 UTC | 11h 0m |
| 2026-07-13 | SVA021 | - | Jul 13, 20:05 UTC | Jul 14, 18:20 UTC | 22h 15m |
| 2026-07-13 | SVA021 | - | Jul 13, 19:30 UTC | Jul 14, 18:00 UTC | 22h 30m |
| 2026-07-12 | SVA020 | - | Jul 12, 23:55 UTC | Jul 13, 17:50 UTC | 17h 55m |
| 2026-07-12 | SVA021 | - | Jul 12, 07:10 UTC | Jul 12, 17:55 UTC | 10h 45m |
| 2026-07-11 | SVA020 | - | Jul 11, 08:05 UTC | Jul 12, 07:50 UTC | 23h 45m |
| 2026-07-11 | SVA020 | - | Jul 11, 00:20 UTC | Jul 11, 09:50 UTC | 9h 30m |
| 2026-07-10 | SVA021 | - | Jul 10, 08:30 UTC | Jul 10, 19:00 UTC | 10h 30m |
| 2026-07-07 | SVA020 | - | Jul 7, 23:55 UTC | Jul 8, 09:00 UTC | 9h 5m |
| 2026-07-07 | SVA021 | - | Jul 7, 07:10 UTC | Jul 7, 18:15 UTC | 11h 5m |
| 2026-07-06 | SVA021 | - | Jul 6, 20:05 UTC | Jul 7, 18:15 UTC | 22h 10m |
| 2026-07-06 | SVA021 | - | Jul 6, 19:30 UTC | Jul 7, 18:00 UTC | 22h 30m |
| 2026-07-06 | SVA020 | - | Jul 6, 00:30 UTC | Jul 6, 17:45 UTC | 17h 15m |
| 2026-07-05 | SVA021 | - | Jul 5, 09:15 UTC | Jul 5, 18:30 UTC | 9h 15m |
| 2026-07-04 | SVA021 | - | Jul 4, 20:05 UTC | Jul 5, 18:30 UTC | 22h 25m |
| 2026-07-04 | SVA021 | - | Jul 4, 19:35 UTC | Jul 5, 18:00 UTC | 22h 25m |
| 2026-07-04 | SVA020 | - | Jul 4, 00:10 UTC | Jul 4, 17:40 UTC | 17h 30m |
| 2026-07-03 | SVA021 | - | Jul 3, 07:55 UTC | Jul 3, 18:25 UTC | 10h 30m |
| 2026-07-01 | SVA020 | - | Jul 1, 23:35 UTC | Jul 2, 08:00 UTC | 8h 25m |
| 2026-07-01 | SVA021 | - | Jul 1, 07:15 UTC | Jul 1, 18:20 UTC | 11h 5m |
| 2026-06-30 | SVA021 | - | Jun 30, 16:05 UTC | Jul 1, 12:15 UTC | 20h 10m |
| 2026-06-30 | SVA021 | - | Jun 30, 14:05 UTC | Jul 1, 12:15 UTC | 22h 10m |
| 2026-06-30 | SVA042 | LAX → JED | Jun 30, 12:45 UTC | Jul 1, 12:00 UTC | 23h 15m |
| 2026-06-30 | SVA042 | LAX → JED | Jun 30, 04:35 UTC | Jun 30, 17:35 UTC | 13h 0m |
| 2026-06-29 | SVA041 | JED → LAX | Jun 29, 08:19 UTC | Jun 29, 22:24 UTC | 14h 5m |
| 2026-06-28 | SVA041 | JED → LAX | Jun 28, 16:05 UTC | Jun 29, 16:00 UTC | 23h 55m |
| 2026-06-28 | SVA041 | JED → LAX | Jun 28, 14:04 UTC | Jun 29, 13:04 UTC | 23h 0m |
| 2026-06-28 | SVA042 | LAX → JED | Jun 28, 12:50 UTC | Jun 29, 12:00 UTC | 23h 10m |
| 2026-06-28 | SVA042 | LAX → JED | Jun 28, 04:29 UTC | Jun 28, 17:10 UTC | 12h 40m |
| 2026-06-27 | SVA041 | JED → LAX | Jun 27, 08:29 UTC | Jun 27, 22:45 UTC | 14h 15m |
| 2026-06-26 | SVA041 | JED → LAX | Jun 26, 16:05 UTC | Jun 27, 13:35 UTC | 21h 30m |
| 2026-06-26 | SVA041 | JED → LAX | Jun 26, 14:05 UTC | Jun 27, 13:35 UTC | 23h 30m |
| 2026-06-26 | SVA042 | LAX → JED | Jun 26, 13:10 UTC | Jun 27, 11:59 UTC | 22h 50m |
| 2026-06-26 | SVA042 | LAX → JED | Jun 26, 04:14 UTC | Jun 26, 17:50 UTC | 13h 35m |
| 2026-06-25 | SVA041 | JED → LAX | Jun 25, 08:24 UTC | Jun 25, 22:39 UTC | 14h 15m |
| 2026-06-23 | SVA042 | LAX → JED | Jun 23, 04:29 UTC | Jun 23, 17:44 UTC | 13h 15m |
| 2026-06-22 | SVA041 | JED → LAX | Jun 22, 08:10 UTC | Jun 22, 22:44 UTC | 14h 35m |
| 2026-06-20 | SVA036 | - | Jun 20, 23:29 UTC | Jun 21, 09:15 UTC | 9h 45m |
| 2026-06-20 | SVA035 | - | Jun 20, 08:09 UTC | Jun 20, 17:59 UTC | 9h 50m |
| 2026-06-14 | SVA020 | - | Jun 14, 23:54 UTC | Jun 15, 08:25 UTC | 8h 30m |
| 2026-06-14 | SVA021 | - | Jun 14, 07:25 UTC | Jun 14, 18:15 UTC | 10h 50m |
| 2026-06-11 | SVA022 | JFK → RUH | Jun 11, 17:00 UTC | Jun 12, 02:35 UTC | 9h 36m |
| 2026-06-11 | SVA023 | RUH → JFK | Jun 11, 03:10 UTC | Jun 11, 14:15 UTC | 11h 5m |
| 2026-06-08 | SVA020 | JFK → JED | Jun 8, 23:55 UTC | Jun 9, 08:55 UTC | 9h 0m |
| 2026-06-08 | SVA021 | JED → JFK | Jun 8, 08:35 UTC | Jun 8, 19:00 UTC | 10h 25m |
| 2026-06-06 | SVA036 | IAD → JED | Jun 6, 23:09 UTC | Jun 7, 08:45 UTC | 9h 35m |
| 2026-06-06 | SVA035 | JED → IAD | Jun 6, 08:00 UTC | Jun 6, 19:30 UTC | 11h 30m |
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-AK36 page for operator, model, and routing details .