sensors Mode-S transponder
7100B5
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AQ11 · AIRBUS A-330-300
- Hex
- 7100B5
- Octal
- 34200265
- Decimal
- 7,405,749
- Country
- SA
- Tail
- HZ-AQ11
- Type
- A333
- Flights observed
- 38
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 7100B5 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 |
|---|---|---|---|
| SVA257 | Saudi Arabian Airlines | 6 | 2026-05-21 |
| SVA256 | Saudi Arabian Airlines | 3 | 2026-05-21 |
| SVA792 | Saudi Arabian Airlines | 2 | 2026-06-02 |
| SVA589 | Saudi Arabian Airlines | 2 | 2026-04-30 |
| SVA588 | Saudi Arabian Airlines | 2 | 2026-05-22 |
| SVA305 | Saudi Arabian Airlines | 2 | 2026-05-05 |
| SVA266 | Saudi Arabian Airlines | 2 | 2026-05-22 |
| SVA9827 | - | 1 | 2026-04-29 |
| SVA9801 | - | 1 | 2026-05-13 |
| SVA9655 | - | 1 | 2026-05-19 |
| SVA700 | Saudi Arabian Airlines | 1 | 2026-04-26 |
| SVA568 | Saudi Arabian Airlines | 1 | 2026-05-25 |
| SVA5636 | - | 1 | 2026-05-19 |
| SVA5500 | - | 1 | 2026-04-19 |
| SVA3228 | Saudi Arabian Airlines | 1 | 2026-04-30 |
| SVA313 | Saudi Arabian Airlines | 1 | 2026-05-16 |
| SVA312 | Saudi Arabian Airlines | 1 | 2026-05-16 |
| SVA311 | Saudi Arabian Airlines | 1 | 2026-05-16 |
| SVA308 | Saudi Arabian Airlines | 1 | 2026-05-24 |
| SVA303 | Saudi Arabian Airlines | 1 | 2026-05-05 |
Recent flights last 38
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | SVA792 | RUH → PEW | Jun 2, 02:25 UTC | Jun 2, 10:30 UTC | 8h 5m |
| 2026-06-01 | SVA792 | RUH → PEW | Jun 1, 13:20 UTC | Jun 2, 10:30 UTC | 21h 10m |
| 2026-06-01 | SVA258 | IST → MED | Jun 1, 11:25 UTC | Jun 2, 10:30 UTC | 23h 5m |
| 2026-06-01 | SVA259 | MED → IST | Jun 1, 03:10 UTC | Jun 1, 09:50 UTC | 6h 40m |
| 2026-05-31 | SVA264 | IST → RUH | May 31, 14:00 UTC | May 31, 15:45 UTC | 1h 45m |
| 2026-05-31 | SVA263 | RUH → IST | May 31, 09:30 UTC | May 31, 11:30 UTC | 2h 0m |
| 2026-05-25 | SVA568 | JED → DXB | May 25, 08:55 UTC | May 25, 12:55 UTC | 4h 0m |
| 2026-05-24 | SVA308 | CAI → JED | May 24, 01:45 UTC | May 24, 01:55 UTC | 10m |
| 2026-05-22 | SVA588 | JED → DXB | May 22, 18:15 UTC | May 23, 11:05 UTC | 16h 49m |
| 2026-05-22 | SVA266 | IST → JED | May 22, 09:45 UTC | May 22, 16:25 UTC | 6h 40m |
| 2026-05-21 | SVA256 | IST → JED | May 21, 13:40 UTC | May 22, 07:00 UTC | 17h 20m |
| 2026-05-21 | SVA257 | JED → IST | May 21, 01:45 UTC | May 21, 10:35 UTC | 8h 50m |
| 2026-05-20 | SVA257 | JED → IST | May 20, 13:20 UTC | May 21, 10:35 UTC | 21h 15m |
| 2026-05-20 | SVA257 | JED → IST | May 20, 11:10 UTC | May 20, 11:20 UTC | 10m |
| 2026-05-20 | SVA257 | JED → IST | May 20, 09:20 UTC | May 20, 10:40 UTC | 1h 20m |
| 2026-05-19 | SVA5636 | - | May 19, 04:40 UTC | May 19, 04:50 UTC | 10m |
| 2026-05-19 | SVA9655 | - | May 19, 02:25 UTC | May 19, 03:00 UTC | 35m |
| 2026-05-18 | SVA266 | IST → JED | May 18, 09:50 UTC | May 18, 11:30 UTC | 1h 40m |
| 2026-05-18 | SVA265 | JED → IST | May 18, 06:01 UTC | May 18, 07:55 UTC | 1h 55m |
| 2026-05-16 | SVA312 | CAI → RUH | May 16, 18:20 UTC | May 17, 06:55 UTC | 12h 35m |
| 2026-05-16 | SVA313 | RUH → CAI | May 16, 15:55 UTC | May 16, 16:20 UTC | 25m |
| 2026-05-16 | SVA311 | RUH → CAI | May 16, 06:25 UTC | May 16, 06:50 UTC | 25m |
| 2026-05-13 | SVA9801 | - | May 13, 01:55 UTC | May 13, 12:40 UTC | 10h 45m |
| 2026-05-05 | SVA305 | JED → CAI | May 5, 18:15 UTC | May 6, 13:15 UTC | 19h 0m |
| 2026-05-05 | SVA303 | JED → CAI | May 5, 15:50 UTC | May 5, 16:00 UTC | 10m |
| 2026-05-01 | SVA305 | JED → CAI | May 1, 13:15 UTC | May 1, 13:25 UTC | 10m |
| 2026-04-30 | SVA589 | DXB → JED | Apr 30, 14:00 UTC | May 1, 13:15 UTC | 23h 15m |
| 2026-04-30 | SVA3228 | IST → MED | Apr 30, 02:55 UTC | Apr 30, 11:45 UTC | 8h 50m |
| 2026-04-29 | SVA9827 | - | Apr 29, 18:25 UTC | Apr 30, 00:50 UTC | 6h 24m |
| 2026-04-26 | SVA700 | JED → KHI | Apr 26, 15:35 UTC | Apr 27, 05:50 UTC | 14h 15m |
| 2026-04-25 | SVA1117 | DMM → JED | Apr 25, 15:30 UTC | Apr 25, 15:40 UTC | 10m |
| 2026-04-23 | SVA589 | DXB → JED | Apr 23, 14:00 UTC | Apr 23, 15:10 UTC | 1h 10m |
| 2026-04-23 | SVA588 | JED → DXB | Apr 23, 10:35 UTC | Apr 23, 11:45 UTC | 1h 10m |
| 2026-04-19 | SVA5500 | - | Apr 19, 07:25 UTC | Apr 19, 12:10 UTC | 4h 45m |
| 2026-04-17 | SVA256 | IST → JED | Apr 17, 13:20 UTC | Apr 17, 14:35 UTC | 1h 15m |
| 2026-04-17 | SVA256 | IST → JED | Apr 17, 12:50 UTC | Apr 17, 13:15 UTC | 25m |
| 2026-04-17 | SVA257 | JED → IST | Apr 17, 09:20 UTC | Apr 17, 10:10 UTC | 50m |
| 2026-04-17 | SVA257 | JED → IST | Apr 17, 08:55 UTC | Apr 17, 09:15 UTC | 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-AQ11 page for operator, model, and routing details .