sensors Mode-S transponder
7100C1
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AK33 · BOEING 777-300ER
- Hex
- 7100C1
- Octal
- 34200301
- Decimal
- 7,405,761
- Country
- SA
- Tail
- HZ-AK33
- Type
- B77W
- Flights observed
- 68
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 7100C1 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 |
|---|---|---|---|
| SVA804 | Saudi Arabian Airlines | 6 | 2026-05-06 |
| SVA738 | Saudi Arabian Airlines | 4 | 2026-05-16 |
| SVA9495 | - | 3 | 2026-05-10 |
| SVA827 | Saudi Arabian Airlines | 3 | 2026-05-26 |
| SVA826 | Saudi Arabian Airlines | 3 | 2026-05-26 |
| SVA810 | Saudi Arabian Airlines | 3 | 2026-05-18 |
| SVA5146 | - | 3 | 2026-06-01 |
| SVA9480 | - | 2 | 2026-05-11 |
| SVA806 | Saudi Arabian Airlines | 2 | 2026-05-17 |
| SVA805 | Saudi Arabian Airlines | 2 | 2026-05-06 |
| SVA772 | - | 2 | 2026-04-13 |
| SVA728 | Saudi Arabian Airlines | 2 | 2026-05-15 |
| SVA5807 | - | 2 | 2026-05-04 |
| SVA5735 | - | 2 | 2026-05-15 |
| SVA5237 | - | 2 | 2026-05-13 |
| SVA341 | Saudi Arabian Airlines | 2 | 2026-05-14 |
| SVA9650 | - | 1 | 2026-05-01 |
| SVA9492 | - | 1 | 2026-05-12 |
| SVA9458 | - | 1 | 2026-05-09 |
| SVA9312 | - | 1 | 2026-04-27 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | SVA5172 | - | Jun 2, 00:30 UTC | Jun 2, 20:15 UTC | 19h 45m |
| 2026-06-01 | SVA9303 | - | Jun 1, 20:55 UTC | Jun 1, 21:10 UTC | 15m |
| 2026-06-01 | SVA5146 | - | Jun 1, 11:20 UTC | Jun 1, 19:10 UTC | 7h 50m |
| 2026-05-31 | SVA5146 | - | May 31, 23:05 UTC | Jun 1, 19:10 UTC | 20h 5m |
| 2026-05-31 | SVA5146 | - | May 31, 20:45 UTC | Jun 1, 19:10 UTC | 22h 25m |
| 2026-05-31 | SVA5802 | - | May 31, 01:11 UTC | May 31, 18:50 UTC | 17h 39m |
| 2026-05-29 | SVA734 | MED → LHE | May 29, 00:20 UTC | May 29, 06:10 UTC | 5h 50m |
| 2026-05-26 | SVA827 | CGK → JED | May 26, 21:44 UTC | May 26, 23:14 UTC | 1h 30m |
| 2026-05-26 | SVA827 | CGK → JED | May 26, 17:59 UTC | May 26, 18:10 UTC | 10m |
| 2026-05-26 | SVA826 | JED → CGK | May 26, 16:00 UTC | May 26, 16:10 UTC | 10m |
| 2026-05-26 | SVA826 | JED → CGK | May 26, 07:59 UTC | May 26, 15:24 UTC | 7h 25m |
| 2026-05-22 | SVA827 | CGK → JED | May 22, 21:35 UTC | May 22, 23:10 UTC | 1h 35m |
| 2026-05-22 | SVA826 | JED → CGK | May 22, 07:30 UTC | May 22, 14:20 UTC | 6h 50m |
| 2026-05-21 | SVA801 | DAC → RUH | May 21, 15:55 UTC | May 21, 16:05 UTC | 10m |
| 2026-05-20 | SVA726 | JED → ISB | May 20, 19:10 UTC | May 20, 22:50 UTC | 3h 40m |
| 2026-05-19 | SVA3149 | - | May 19, 15:45 UTC | May 19, 16:15 UTC | 30m |
| 2026-05-19 | SVA5811 | - | May 19, 00:10 UTC | May 19, 14:00 UTC | 13h 50m |
| 2026-05-18 | SVA810 | JED → DAC | May 18, 05:50 UTC | May 18, 22:10 UTC | 16h 19m |
| 2026-05-17 | SVA806 | RUH → DAC | May 17, 22:50 UTC | May 18, 03:25 UTC | 4h 35m |
| 2026-05-16 | SVA738 | JED → LHE | May 16, 06:06 UTC | May 16, 22:30 UTC | 16h 25m |
| 2026-05-16 | SVA738 | JED → LHE | May 16, 03:00 UTC | May 16, 22:30 UTC | 19h 30m |
| 2026-05-15 | SVA5735 | - | May 15, 12:50 UTC | May 16, 06:16 UTC | 17h 25m |
| 2026-05-15 | SVA5735 | - | May 15, 09:35 UTC | May 16, 06:16 UTC | 20h 40m |
| 2026-05-15 | SVA728 | JED → ISB | May 15, 07:10 UTC | May 16, 06:16 UTC | 23h 5m |
| 2026-05-14 | SVA728 | JED → ISB | May 14, 16:20 UTC | May 15, 12:55 UTC | 20h 35m |
| 2026-05-14 | SVA5558 | - | May 14, 15:35 UTC | May 15, 12:55 UTC | 21h 20m |
| 2026-05-14 | SVA341 | JED → ALG | May 14, 10:31 UTC | May 15, 09:40 UTC | 23h 10m |
| 2026-05-14 | SVA341 | JED → ALG | May 14, 09:50 UTC | May 15, 08:00 UTC | 22h 10m |
| 2026-05-13 | SVA5237 | - | May 13, 00:00 UTC | May 13, 00:40 UTC | 40m |
| 2026-05-12 | SVA5237 | - | May 12, 20:20 UTC | May 12, 20:30 UTC | 10m |
| 2026-05-12 | SVA9492 | - | May 12, 15:10 UTC | May 12, 15:25 UTC | 15m |
| 2026-05-11 | SVA5191 | - | May 11, 19:40 UTC | May 12, 11:05 UTC | 15h 25m |
| 2026-05-11 | SVA9480 | - | May 11, 07:00 UTC | May 11, 11:55 UTC | 4h 55m |
| 2026-05-10 | SVA9480 | - | May 10, 14:59 UTC | May 11, 11:55 UTC | 20h 55m |
| 2026-05-10 | SVA5361 | - | May 10, 11:00 UTC | May 11, 07:40 UTC | 20h 40m |
| 2026-05-10 | SVA9495 | - | May 10, 03:10 UTC | May 10, 08:20 UTC | 5h 10m |
| 2026-05-09 | SVA9495 | - | May 9, 12:20 UTC | May 10, 08:20 UTC | 20h 0m |
| 2026-05-09 | SVA9495 | - | May 9, 12:00 UTC | May 10, 08:20 UTC | 20h 20m |
| 2026-05-09 | SVA9458 | - | May 9, 00:40 UTC | May 9, 05:45 UTC | 5h 5m |
| 2026-05-06 | SVA805 | DAC → JED | May 6, 18:55 UTC | May 7, 00:05 UTC | 5h 10m |
| 2026-05-06 | SVA804 | JED → DAC | May 6, 00:25 UTC | May 6, 16:45 UTC | 16h 20m |
| 2026-05-05 | SVA804 | JED → DAC | May 5, 20:20 UTC | May 6, 16:45 UTC | 20h 25m |
| 2026-05-05 | SVA805 | DAC → JED | May 5, 19:35 UTC | May 6, 16:45 UTC | 21h 10m |
| 2026-05-05 | SVA804 | JED → DAC | May 5, 00:25 UTC | May 5, 17:25 UTC | 17h 0m |
| 2026-05-04 | SVA5807 | - | May 4, 06:20 UTC | May 5, 05:40 UTC | 23h 21m |
| 2026-05-04 | SVA5807 | - | May 4, 06:10 UTC | May 5, 02:10 UTC | 20h 1m |
| 2026-05-03 | SVA806 | RUH → DAC | May 3, 22:49 UTC | May 4, 03:15 UTC | 4h 25m |
| 2026-05-01 | SVA5909 | - | May 1, 14:55 UTC | May 1, 18:30 UTC | 3h 35m |
| 2026-05-01 | SVA9650 | - | May 1, 10:00 UTC | May 1, 12:50 UTC | 2h 50m |
| 2026-04-30 | SVA809 | DAC → JED | Apr 30, 07:40 UTC | Apr 30, 10:15 UTC | 2h 35m |
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-AK33 page for operator, model, and routing details .