sensors Mode-S transponder
7100B9
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AQ15 · AIRBUS A-330-300
- Hex
- 7100B9
- Octal
- 34200271
- Decimal
- 7,405,753
- Country
- SA
- Tail
- HZ-AQ15
- Type
- A333
- Flights observed
- 41
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address 7100B9 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 |
|---|---|---|---|
| SVA211 | Saudi Arabian Airlines | 6 | 2026-04-28 |
| SVA236 | - | 4 | 2026-04-14 |
| SVA700 | - | 2 | 2026-04-13 |
| SVA589 | Saudi Arabian Airlines | 2 | 2026-05-03 |
| SVA588 | Saudi Arabian Airlines | 2 | 2026-05-08 |
| SVA5500 | - | 2 | 2026-04-18 |
| SVA417 | Saudi Arabian Airlines | 2 | 2026-05-28 |
| SVA321 | Saudi Arabian Airlines | 2 | 2026-05-28 |
| SVA318 | Saudi Arabian Airlines | 2 | 2026-05-07 |
| SVA311 | Saudi Arabian Airlines | 2 | 2026-05-05 |
| SVA237 | Saudi Arabian Airlines | 2 | 2026-04-14 |
| SVA210 | Saudi Arabian Airlines | 2 | 2026-04-28 |
| SVA9801 | - | 1 | 2026-04-18 |
| SVA708 | Saudi Arabian Airlines | 1 | 2026-05-30 |
| SVA596 | Saudi Arabian Airlines | 1 | 2026-05-27 |
| SVA431 | Saudi Arabian Airlines | 1 | 2026-04-17 |
| SVA389 | Saudi Arabian Airlines | 1 | 2026-04-22 |
| SVA388 | Saudi Arabian Airlines | 1 | 2026-04-22 |
| SVA320 | Saudi Arabian Airlines | 1 | 2026-05-28 |
| SVA313 | Saudi Arabian Airlines | 1 | 2026-05-09 |
Recent flights last 41
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | SVA708 | RUH → KHI | May 30, 04:15 UTC | May 30, 04:55 UTC | 40m |
| 2026-05-28 | SVA320 | CAI → RUH | May 28, 21:50 UTC | May 28, 22:05 UTC | 15m |
| 2026-05-28 | SVA321 | RUH → CAI | May 28, 13:25 UTC | May 28, 19:50 UTC | 6h 25m |
| 2026-05-28 | SVA417 | RUH → CAI | May 28, 10:50 UTC | May 28, 11:10 UTC | 20m |
| 2026-05-27 | SVA596 | MED → DXB | May 27, 06:34 UTC | May 27, 07:00 UTC | 26m |
| 2026-05-09 | SVA312 | CAI → RUH | May 9, 18:20 UTC | May 9, 18:30 UTC | 10m |
| 2026-05-09 | SVA313 | RUH → CAI | May 9, 15:50 UTC | May 9, 16:10 UTC | 20m |
| 2026-05-08 | SVA588 | JED → DXB | May 8, 10:35 UTC | May 8, 11:09 UTC | 35m |
| 2026-05-07 | SVA318 | CAI → MED | May 7, 06:40 UTC | May 7, 06:50 UTC | 10m |
| 2026-05-05 | SVA311 | RUH → CAI | May 5, 06:25 UTC | May 5, 06:45 UTC | 20m |
| 2026-05-04 | SVA321 | RUH → CAI | May 4, 19:35 UTC | May 4, 20:00 UTC | 25m |
| 2026-05-04 | SVA417 | RUH → CAI | May 4, 11:15 UTC | May 4, 11:35 UTC | 20m |
| 2026-05-03 | SVA589 | DXB → JED | May 3, 14:20 UTC | May 4, 11:35 UTC | 21h 15m |
| 2026-05-03 | SVA589 | DXB → JED | May 3, 13:40 UTC | May 4, 11:35 UTC | 21h 55m |
| 2026-05-03 | SVA588 | JED → DXB | May 3, 10:45 UTC | May 3, 11:55 UTC | 1h 10m |
| 2026-05-02 | SVA318 | CAI → MED | May 2, 06:55 UTC | May 2, 07:05 UTC | 10m |
| 2026-05-01 | SVA302 | CAI → JED | May 1, 18:25 UTC | May 1, 18:40 UTC | 15m |
| 2026-05-01 | SVA301 | JED → CAI | May 1, 07:40 UTC | May 1, 07:50 UTC | 10m |
| 2026-04-28 | SVA210 | MXP → RUH | Apr 28, 14:30 UTC | Apr 29, 07:15 UTC | 16h 45m |
| 2026-04-28 | SVA211 | JED → MXP | Apr 28, 09:15 UTC | Apr 28, 12:00 UTC | 2h 45m |
| 2026-04-26 | SVA210 | MXP → RUH | Apr 26, 14:40 UTC | Apr 26, 16:55 UTC | 2h 15m |
| 2026-04-25 | SVA211 | JED → MXP | Apr 25, 16:20 UTC | Apr 26, 12:05 UTC | 19h 45m |
| 2026-04-25 | SVA211 | JED → MXP | Apr 25, 14:45 UTC | Apr 26, 12:05 UTC | 21h 20m |
| 2026-04-24 | SVA211 | JED → MXP | Apr 24, 16:20 UTC | Apr 25, 12:05 UTC | 19h 45m |
| 2026-04-24 | SVA211 | JED → MXP | Apr 24, 14:25 UTC | Apr 25, 12:05 UTC | 21h 40m |
| 2026-04-24 | SVA211 | JED → MXP | Apr 24, 09:20 UTC | Apr 24, 11:55 UTC | 2h 35m |
| 2026-04-22 | SVA388 | CAI → JED | Apr 22, 20:40 UTC | Apr 22, 21:05 UTC | 25m |
| 2026-04-22 | SVA389 | JED → CAI | Apr 22, 18:45 UTC | Apr 22, 18:55 UTC | 10m |
| 2026-04-19 | SVA311 | RUH → CAI | Apr 19, 06:50 UTC | Apr 19, 07:05 UTC | 15m |
| 2026-04-18 | SVA5500 | - | Apr 18, 10:40 UTC | Apr 19, 07:05 UTC | 20h 25m |
| 2026-04-18 | SVA9801 | - | Apr 18, 07:25 UTC | Apr 18, 07:50 UTC | 25m |
| 2026-04-18 | SVA5500 | - | Apr 18, 06:50 UTC | Apr 18, 12:00 UTC | 5h 10m |
| 2026-04-17 | SVA431 | JED → NBO | Apr 17, 21:05 UTC | Apr 17, 21:15 UTC | 10m |
| 2026-04-14 | SVA236 | - | Apr 14, 16:35 UTC | Apr 14, 16:45 UTC | 10m |
| 2026-04-14 | SVA236 | - | Apr 14, 14:50 UTC | Apr 14, 16:25 UTC | 1h 35m |
| 2026-04-14 | SVA236 | - | Apr 14, 14:10 UTC | Apr 14, 14:45 UTC | 35m |
| 2026-04-14 | SVA237 | JED → GVA | Apr 14, 10:50 UTC | Apr 14, 12:35 UTC | 1h 45m |
| 2026-04-14 | SVA237 | JED → GVA | Apr 14, 09:45 UTC | Apr 14, 11:05 UTC | 1h 20m |
| 2026-04-13 | SVA700 | - | Apr 13, 00:20 UTC | Apr 13, 01:00 UTC | 40m |
| 2026-04-13 | SVA700 | - | Apr 13, 00:00 UTC | Apr 13, 01:00 UTC | 1h 0m |
| 2026-04-12 | SVA236 | - | Apr 12, 17:15 UTC | Apr 12, 18:20 UTC | 1h 5m |
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-AQ15 page for operator, model, and routing details .