sensors Mode-S transponder
7100C0
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AK32 · BOEING 777-300ER
- Hex
- 7100C0
- Octal
- 34200300
- Decimal
- 7,405,760
- Country
- SA
- Tail
- HZ-AK32
- Type
- B77W
- Flights observed
- 67
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 7100C0 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 |
|---|---|---|---|
| SVA827 | Saudi Arabian Airlines | 5 | 2026-05-01 |
| SVA9528 | - | 3 | 2026-05-14 |
| SVA800 | Saudi Arabian Airlines | 3 | 2026-04-28 |
| SVA5224 | - | 3 | 2026-06-04 |
| SVA5194 | - | 3 | 2026-06-03 |
| SVA9512 | - | 2 | 2026-05-11 |
| SVA9496 | - | 2 | 2026-05-08 |
| SVA9431 | - | 2 | 2026-05-21 |
| SVA826 | Saudi Arabian Airlines | 2 | 2026-04-25 |
| SVA807 | Saudi Arabian Airlines | 2 | 2026-04-27 |
| SVA805 | Saudi Arabian Airlines | 2 | 2026-05-31 |
| SVA803 | Saudi Arabian Airlines | 2 | 2026-06-02 |
| SVA5808 | - | 2 | 2026-06-06 |
| SVA5148 | - | 2 | 2026-06-01 |
| SVA9690 | - | 1 | 2026-05-17 |
| SVA9668 | - | 1 | 2026-05-18 |
| SVA9666 | - | 1 | 2026-05-17 |
| SVA9650 | - | 1 | 2026-05-06 |
| SVA9623 | - | 1 | 2026-05-04 |
| SVA9542 | - | 1 | 2026-06-07 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-07 | SVA9542 | - | Jun 7, 07:30 UTC | Jun 7, 09:05 UTC | 1h 35m |
| 2026-06-06 | SVA5288 | - | Jun 6, 08:05 UTC | Jun 7, 02:04 UTC | 18h 0m |
| 2026-06-06 | SVA5808 | - | Jun 6, 01:20 UTC | Jun 6, 06:00 UTC | 4h 40m |
| 2026-06-05 | SVA5808 | - | Jun 5, 07:05 UTC | Jun 6, 06:00 UTC | 22h 55m |
| 2026-06-05 | SVA9466 | - | Jun 5, 03:20 UTC | Jun 5, 03:35 UTC | 15m |
| 2026-06-04 | SVA5224 | - | Jun 4, 17:25 UTC | Jun 5, 01:25 UTC | 8h 0m |
| 2026-06-04 | SVA5224 | - | Jun 4, 04:05 UTC | Jun 5, 01:25 UTC | 21h 20m |
| 2026-06-04 | SVA5224 | - | Jun 4, 03:25 UTC | Jun 5, 01:25 UTC | 22h 0m |
| 2026-06-03 | SVA9440 | - | Jun 3, 23:45 UTC | Jun 4, 00:00 UTC | 15m |
| 2026-06-03 | SVA5194 | - | Jun 3, 13:45 UTC | Jun 3, 21:35 UTC | 7h 50m |
| 2026-06-03 | SVA5194 | - | Jun 3, 00:05 UTC | Jun 3, 21:35 UTC | 21h 30m |
| 2026-06-02 | SVA5194 | - | Jun 2, 22:05 UTC | Jun 3, 21:35 UTC | 23h 30m |
| 2026-06-02 | SVA803 | DAC → JED | Jun 2, 21:40 UTC | Jun 3, 17:15 UTC | 19h 35m |
| 2026-06-02 | SVA5802 | - | Jun 2, 01:20 UTC | Jun 2, 19:35 UTC | 18h 15m |
| 2026-06-01 | SVA5148 | - | Jun 1, 15:20 UTC | Jun 1, 23:10 UTC | 7h 50m |
| 2026-05-31 | SVA5148 | - | May 31, 22:05 UTC | Jun 1, 22:00 UTC | 23h 55m |
| 2026-05-31 | SVA805 | DAC → JED | May 31, 20:05 UTC | Jun 1, 19:05 UTC | 23h 0m |
| 2026-05-31 | SVA805 | DAC → JED | May 31, 19:05 UTC | Jun 1, 17:40 UTC | 22h 35m |
| 2026-05-31 | SVA5804 | - | May 31, 12:20 UTC | May 31, 17:05 UTC | 4h 45m |
| 2026-05-30 | SVA771 | MAA → JED | May 30, 06:05 UTC | May 30, 06:40 UTC | 35m |
| 2026-05-30 | SVA770 | JED → BOM | May 30, 03:00 UTC | May 30, 03:55 UTC | 55m |
| 2026-05-21 | SVA5420 | - | May 21, 18:25 UTC | May 21, 19:10 UTC | 45m |
| 2026-05-21 | SVA9431 | - | May 21, 02:40 UTC | May 21, 15:55 UTC | 13h 15m |
| 2026-05-20 | SVA9431 | - | May 20, 18:45 UTC | May 21, 15:55 UTC | 21h 10m |
| 2026-05-20 | SVA3776 | RUH → COK | May 20, 00:25 UTC | May 20, 16:10 UTC | 15h 46m |
| 2026-05-19 | SVA3648 | JED → BOM | May 19, 11:35 UTC | May 19, 22:40 UTC | 11h 5m |
| 2026-05-18 | SVA9668 | - | May 18, 17:00 UTC | May 19, 09:25 UTC | 16h 24m |
| 2026-05-18 | SVA738 | JED → LHE | May 18, 06:20 UTC | May 18, 22:30 UTC | 16h 9m |
| 2026-05-17 | SVA9690 | - | May 17, 10:20 UTC | May 18, 03:50 UTC | 17h 30m |
| 2026-05-17 | SVA9666 | - | May 17, 05:00 UTC | May 17, 08:25 UTC | 3h 25m |
| 2026-05-15 | SVA5187 | - | May 15, 04:35 UTC | May 15, 08:55 UTC | 4h 20m |
| 2026-05-14 | SVA9528 | - | May 14, 21:25 UTC | May 15, 02:30 UTC | 5h 5m |
| 2026-05-14 | SVA9528 | - | May 14, 07:20 UTC | May 15, 02:30 UTC | 19h 10m |
| 2026-05-14 | SVA9528 | - | May 14, 02:55 UTC | May 15, 01:50 UTC | 22h 55m |
| 2026-05-13 | SVA9521 | - | May 13, 16:10 UTC | May 14, 00:15 UTC | 8h 5m |
| 2026-05-12 | SVA5111 | - | May 12, 11:15 UTC | May 12, 15:35 UTC | 4h 20m |
| 2026-05-11 | SVA9512 | - | May 11, 14:50 UTC | May 12, 09:00 UTC | 18h 11m |
| 2026-05-11 | SVA9512 | - | May 11, 11:00 UTC | May 12, 09:00 UTC | 22h 1m |
| 2026-05-11 | SVA9500 | - | May 11, 03:35 UTC | May 11, 08:25 UTC | 4h 50m |
| 2026-05-09 | SVA5203 | - | May 9, 11:50 UTC | May 9, 16:10 UTC | 4h 20m |
| 2026-05-08 | SVA9496 | - | May 8, 14:20 UTC | May 9, 10:00 UTC | 19h 40m |
| 2026-05-08 | SVA9496 | - | May 8, 12:04 UTC | May 9, 10:00 UTC | 21h 55m |
| 2026-05-08 | SVA5211 | - | May 8, 10:29 UTC | May 9, 10:00 UTC | 23h 30m |
| 2026-05-07 | SVA9459 | - | May 7, 23:39 UTC | May 8, 07:39 UTC | 8h 0m |
| 2026-05-06 | SVA3061 | DEL → JED | May 6, 15:10 UTC | May 6, 15:40 UTC | 30m |
| 2026-05-06 | SVA9650 | - | May 6, 08:55 UTC | May 6, 12:45 UTC | 3h 50m |
| 2026-05-04 | SVA9623 | - | May 4, 18:45 UTC | May 5, 04:20 UTC | 9h 35m |
| 2026-05-01 | SVA827 | CGK → JED | May 1, 18:55 UTC | May 1, 23:30 UTC | 4h 35m |
| 2026-05-01 | SVA827 | CGK → JED | May 1, 18:05 UTC | May 1, 18:20 UTC | 15m |
| 2026-04-30 | SVA803 | DAC → JED | Apr 30, 20:45 UTC | May 1, 15:05 UTC | 18h 20m |
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-AK32 page for operator, model, and routing details .