sensors Mode-S transponder
7100C3
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AK35 · BOEING 777-300ER
- Hex
- 7100C3
- Octal
- 34200303
- Decimal
- 7,405,763
- Country
- SA
- Tail
- HZ-AK35
- Type
- B77W
- Flights observed
- 63
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 20d ago
Last known position
Country allocation
The ICAO 24-bit address 7100C3 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 |
|---|---|---|---|
| SVA807 | Saudi Arabian Airlines | 4 | 2026-04-15 |
| SVA9490 | - | 3 | 2026-05-12 |
| SVA9388 | - | 3 | 2026-04-29 |
| SVA9352 | - | 3 | 2026-04-27 |
| SVA9305 | - | 3 | 2026-04-23 |
| SVA861 | Saudi Arabian Airlines | 3 | 2026-05-04 |
| SVA818 | Saudi Arabian Airlines | 3 | 2026-04-18 |
| SVA760 | Saudi Arabian Airlines | 3 | 2026-05-04 |
| SVA758 | - | 3 | 2026-04-13 |
| SVA9397 | - | 2 | 2026-05-02 |
| SVA9385 | - | 2 | 2026-04-28 |
| SVA9345 | - | 2 | 2026-04-22 |
| SVA9336 | - | 2 | 2026-04-26 |
| SVA9326 | - | 2 | 2026-04-25 |
| SVA9309 | - | 2 | 2026-04-24 |
| SVA862 | Saudi Arabian Airlines | 2 | 2026-05-03 |
| SVA819 | Saudi Arabian Airlines | 2 | 2026-04-18 |
| SVA806 | - | 2 | 2026-04-15 |
| SVA800 | Saudi Arabian Airlines | 2 | 2026-05-10 |
| SVA5219 | - | 2 | 2026-05-12 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-12 | SVA5219 | - | May 12, 18:50 UTC | May 12, 19:35 UTC | 45m |
| 2026-05-12 | SVA5219 | - | May 12, 15:01 UTC | May 12, 15:10 UTC | 10m |
| 2026-05-12 | SVA9490 | - | May 12, 12:10 UTC | May 12, 12:25 UTC | 15m |
| 2026-05-11 | SVA9490 | - | May 11, 16:50 UTC | May 12, 11:35 UTC | 18h 46m |
| 2026-05-11 | SVA9490 | - | May 11, 15:25 UTC | May 12, 11:35 UTC | 20h 11m |
| 2026-05-11 | SVA9740 | - | May 11, 09:30 UTC | May 11, 13:15 UTC | 3h 45m |
| 2026-05-10 | SVA800 | JED → DAC | May 10, 09:30 UTC | May 10, 09:45 UTC | 15m |
| 2026-05-09 | SVA800 | JED → DAC | May 9, 16:45 UTC | May 10, 07:15 UTC | 14h 30m |
| 2026-05-07 | SVA803 | DAC → JED | May 7, 20:50 UTC | May 7, 21:55 UTC | 1h 5m |
| 2026-05-07 | SVA802 | JED → DAC | May 7, 17:20 UTC | May 7, 18:15 UTC | 55m |
| 2026-05-05 | SVA761 | DEL → RUH | May 5, 13:40 UTC | May 5, 21:20 UTC | 7h 40m |
| 2026-05-04 | SVA760 | RUH → DEL | May 4, 16:50 UTC | May 5, 11:40 UTC | 18h 51m |
| 2026-05-04 | SVA760 | RUH → DEL | May 4, 16:30 UTC | May 5, 11:40 UTC | 19h 11m |
| 2026-05-04 | SVA760 | RUH → DEL | May 4, 12:50 UTC | May 5, 11:40 UTC | 22h 51m |
| 2026-05-04 | SVA861 | MNL → RUH | May 4, 11:05 UTC | May 5, 10:45 UTC | 23h 41m |
| 2026-05-04 | SVA861 | MNL → RUH | May 4, 10:15 UTC | May 5, 08:45 UTC | 22h 31m |
| 2026-05-04 | SVA861 | MNL → RUH | May 4, 08:00 UTC | May 4, 16:50 UTC | 8h 50m |
| 2026-05-03 | SVA862 | RUH → MNL | May 3, 21:00 UTC | May 4, 05:20 UTC | 8h 20m |
| 2026-05-03 | SVA862 | RUH → MNL | May 3, 03:20 UTC | May 4, 02:45 UTC | 23h 24m |
| 2026-05-03 | SVA5943 | - | May 3, 01:15 UTC | May 3, 21:24 UTC | 20h 9m |
| 2026-05-02 | SVA9688 | - | May 2, 09:00 UTC | May 2, 22:50 UTC | 13h 50m |
| 2026-05-02 | SVA9397 | - | May 2, 00:35 UTC | May 2, 00:45 UTC | 10m |
| 2026-05-01 | SVA9397 | - | May 1, 16:45 UTC | May 2, 00:05 UTC | 7h 20m |
| 2026-04-30 | SVA5109 | - | Apr 30, 10:40 UTC | Apr 30, 16:00 UTC | 5h 21m |
| 2026-04-29 | SVA9388 | - | Apr 29, 13:05 UTC | Apr 30, 08:30 UTC | 19h 24m |
| 2026-04-29 | SVA9388 | - | Apr 29, 11:35 UTC | Apr 30, 08:30 UTC | 20h 54m |
| 2026-04-29 | SVA9388 | - | Apr 29, 07:40 UTC | Apr 30, 04:25 UTC | 20h 45m |
| 2026-04-28 | SVA9385 | - | Apr 28, 11:15 UTC | Apr 29, 04:55 UTC | 17h 40m |
| 2026-04-28 | SVA9385 | - | Apr 28, 07:25 UTC | Apr 29, 04:44 UTC | 21h 20m |
| 2026-04-27 | SVA9352 | - | Apr 27, 10:30 UTC | Apr 28, 04:20 UTC | 17h 50m |
| 2026-04-27 | SVA9352 | - | Apr 27, 06:50 UTC | Apr 28, 04:20 UTC | 21h 30m |
| 2026-04-27 | SVA9352 | - | Apr 27, 06:30 UTC | Apr 28, 04:20 UTC | 21h 50m |
| 2026-04-26 | SVA9336 | - | Apr 26, 09:35 UTC | Apr 27, 03:55 UTC | 18h 20m |
| 2026-04-26 | SVA9336 | - | Apr 26, 05:55 UTC | Apr 27, 03:55 UTC | 22h 0m |
| 2026-04-25 | SVA9326 | - | Apr 25, 09:05 UTC | Apr 26, 03:05 UTC | 18h 0m |
| 2026-04-25 | SVA9326 | - | Apr 25, 04:50 UTC | Apr 26, 03:05 UTC | 22h 15m |
| 2026-04-24 | SVA9309 | - | Apr 24, 08:30 UTC | Apr 25, 02:10 UTC | 17h 40m |
| 2026-04-24 | SVA9309 | - | Apr 24, 04:10 UTC | Apr 25, 02:10 UTC | 22h 0m |
| 2026-04-23 | SVA9305 | - | Apr 23, 07:01 UTC | Apr 24, 00:25 UTC | 17h 24m |
| 2026-04-23 | SVA9305 | - | Apr 23, 02:50 UTC | Apr 24, 00:25 UTC | 21h 35m |
| 2026-04-22 | SVA9345 | - | Apr 22, 06:30 UTC | Apr 23, 00:15 UTC | 17h 45m |
| 2026-04-22 | SVA9345 | - | Apr 22, 02:15 UTC | Apr 23, 00:15 UTC | 22h 0m |
| 2026-04-20 | SVA9305 | - | Apr 20, 19:45 UTC | Apr 21, 03:50 UTC | 8h 5m |
| 2026-04-19 | SVA726 | - | Apr 19, 16:45 UTC | Apr 19, 17:05 UTC | 20m |
| 2026-04-18 | SVA819 | CGK → JED | Apr 18, 14:35 UTC | Apr 18, 15:25 UTC | 50m |
| 2026-04-18 | SVA819 | CGK → JED | Apr 18, 10:50 UTC | Apr 18, 11:00 UTC | 10m |
| 2026-04-18 | SVA818 | JED → CGK | Apr 18, 08:20 UTC | Apr 18, 08:35 UTC | 15m |
| 2026-04-18 | SVA818 | JED → CGK | Apr 18, 07:00 UTC | Apr 18, 07:20 UTC | 20m |
| 2026-04-18 | SVA818 | JED → CGK | Apr 18, 03:40 UTC | Apr 18, 04:30 UTC | 50m |
| 2026-04-16 | SVA705 | KHI → JED | Apr 16, 23:30 UTC | Apr 16, 23:40 UTC | 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-AK35 page for operator, model, and routing details .