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
- 110
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 1h 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 | 11 | 2026-06-11 |
| SVA311 | - | 9 | 2026-07-11 |
| SVA321 | - | 6 | 2026-07-13 |
| SVA417 | - | 4 | 2026-06-30 |
| SVA313 | - | 4 | 2026-07-12 |
| SVA312 | - | 4 | 2026-07-12 |
| SVA236 | - | 4 | 2026-04-14 |
| SVA210 | Saudi Arabian Airlines | 4 | 2026-06-11 |
| SVA708 | - | 3 | 2026-07-11 |
| SVA389 | Saudi Arabian Airlines | 3 | 2026-06-21 |
| SVA388 | Saudi Arabian Airlines | 3 | 2026-06-21 |
| SVA128 | - | 3 | 2026-07-10 |
| SVA9828 | - | 2 | 2026-06-03 |
| 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 |
| SVA431 | Saudi Arabian Airlines | 2 | 2026-06-09 |
| SVA3227 | Saudi Arabian Airlines | 2 | 2026-06-01 |
| SVA320 | - | 2 | 2026-07-13 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | SVA304 | CAI → JED | Jul 14, 15:30 UTC | Jul 14, 15:40 UTC | 10m |
| 2026-07-13 | SVA320 | - | Jul 13, 22:40 UTC | Jul 14, 13:15 UTC | 14h 35m |
| 2026-07-13 | SVA321 | - | Jul 13, 13:15 UTC | Jul 13, 21:00 UTC | 7h 45m |
| 2026-07-12 | SVA312 | - | Jul 12, 18:25 UTC | Jul 13, 11:10 UTC | 16h 45m |
| 2026-07-12 | SVA313 | - | Jul 12, 09:00 UTC | Jul 12, 16:35 UTC | 7h 35m |
| 2026-07-11 | SVA311 | - | Jul 11, 18:10 UTC | Jul 12, 07:10 UTC | 13h 0m |
| 2026-07-11 | SVA708 | - | Jul 11, 04:30 UTC | Jul 11, 15:55 UTC | 11h 25m |
| 2026-07-10 | SVA708 | - | Jul 10, 18:20 UTC | Jul 11, 15:55 UTC | 21h 36m |
| 2026-07-10 | SVA128 | - | Jul 10, 16:20 UTC | Jul 11, 15:55 UTC | 23h 35m |
| 2026-07-10 | SVA128 | - | Jul 10, 15:25 UTC | Jul 11, 10:50 UTC | 19h 25m |
| 2026-07-10 | SVA129 | - | Jul 10, 02:05 UTC | Jul 10, 13:00 UTC | 10h 55m |
| 2026-07-09 | SVA323 | - | Jul 9, 23:30 UTC | Jul 9, 23:50 UTC | 20m |
| 2026-07-09 | SVA311 | - | Jul 9, 06:20 UTC | Jul 9, 06:35 UTC | 15m |
| 2026-07-08 | SVA321 | - | Jul 8, 19:40 UTC | Jul 8, 19:50 UTC | 10m |
| 2026-07-07 | SVA709 | - | Jul 7, 11:30 UTC | Jul 7, 12:25 UTC | 55m |
| 2026-07-06 | SVA128 | - | Jul 6, 15:55 UTC | Jul 7, 07:20 UTC | 15h 25m |
| 2026-07-06 | SVA129 | - | Jul 6, 09:45 UTC | Jul 6, 13:30 UTC | 3h 45m |
| 2026-07-04 | SVA301 | - | Jul 4, 15:25 UTC | Jul 5, 07:55 UTC | 16h 30m |
| 2026-07-04 | SVA305 | JED → CAI | Jul 4, 12:50 UTC | Jul 4, 13:10 UTC | 20m |
| 2026-07-03 | SVA212 | - | Jul 3, 16:20 UTC | Jul 4, 13:10 UTC | 20h 50m |
| 2026-07-03 | SVA212 | - | Jul 3, 14:25 UTC | Jul 4, 13:10 UTC | 22h 45m |
| 2026-07-03 | SVA213 | - | Jul 3, 08:25 UTC | Jul 3, 12:00 UTC | 3h 35m |
| 2026-07-02 | SVA311 | - | Jul 2, 06:20 UTC | Jul 2, 06:35 UTC | 15m |
| 2026-06-30 | SVA417 | - | Jun 30, 10:45 UTC | Jun 30, 10:55 UTC | 10m |
| 2026-06-29 | SVA238 | GVA → RUH | Jun 29, 14:09 UTC | Jun 30, 00:20 UTC | 10h 10m |
| 2026-06-29 | SVA239 | - | Jun 29, 08:09 UTC | Jun 29, 12:05 UTC | 3h 55m |
| 2026-06-27 | SVA597 | - | Jun 27, 09:44 UTC | Jun 27, 10:40 UTC | 55m |
| 2026-06-26 | SVA256 | IST → JED | Jun 26, 12:44 UTC | Jun 27, 08:05 UTC | 19h 20m |
| 2026-06-25 | SVA257 | - | Jun 25, 22:04 UTC | Jun 26, 10:25 UTC | 12h 20m |
| 2026-06-25 | SVA321 | - | Jun 25, 13:14 UTC | Jun 25, 19:44 UTC | 6h 30m |
| 2026-06-25 | SVA417 | - | Jun 25, 10:39 UTC | Jun 25, 10:55 UTC | 15m |
| 2026-06-22 | SVA300 | CAI → JED | Jun 22, 09:54 UTC | Jun 22, 10:10 UTC | 15m |
| 2026-06-21 | SVA388 | CAI → JED | Jun 21, 20:50 UTC | Jun 22, 07:40 UTC | 10h 50m |
| 2026-06-21 | SVA389 | JED → CAI | Jun 21, 18:04 UTC | Jun 21, 18:44 UTC | 40m |
| 2026-06-21 | SVA307 | JED → CAI | Jun 21, 09:40 UTC | Jun 21, 09:59 UTC | 20m |
| 2026-06-20 | SVA308 | CAI → JED | Jun 20, 02:14 UTC | Jun 20, 13:14 UTC | 11h 0m |
| 2026-06-19 | SVA309 | - | Jun 19, 23:25 UTC | Jun 19, 23:54 UTC | 30m |
| 2026-06-18 | SVA311 | - | Jun 18, 21:50 UTC | Jun 19, 06:35 UTC | 8h 44m |
| 2026-06-18 | SVA321 | RUH → CAI | Jun 18, 13:30 UTC | Jun 18, 19:45 UTC | 6h 15m |
| 2026-06-17 | SVA312 | CAI → RUH | Jun 17, 18:30 UTC | Jun 18, 11:05 UTC | 16h 35m |
| 2026-06-17 | SVA313 | RUH → CAI | Jun 17, 09:15 UTC | Jun 17, 16:00 UTC | 6h 45m |
| 2026-06-17 | SVA311 | - | Jun 17, 06:20 UTC | Jun 17, 06:35 UTC | 15m |
| 2026-06-15 | SVA312 | CAI → RUH | Jun 15, 18:15 UTC | Jun 15, 18:35 UTC | 20m |
| 2026-06-15 | SVA313 | RUH → CAI | Jun 15, 09:10 UTC | Jun 15, 16:04 UTC | 6h 55m |
| 2026-06-15 | SVA311 | - | Jun 15, 06:24 UTC | Jun 15, 06:40 UTC | 15m |
| 2026-06-14 | SVA9658 | - | Jun 14, 02:20 UTC | Jun 14, 03:55 UTC | 1h 35m |
| 2026-06-13 | SVA5549 | - | Jun 13, 21:25 UTC | Jun 14, 00:30 UTC | 3h 5m |
| 2026-06-11 | SVA210 | MXP → RUH | Jun 11, 14:30 UTC | Jun 11, 17:40 UTC | 3h 10m |
| 2026-06-11 | SVA211 | JED → MXP | Jun 11, 09:10 UTC | Jun 11, 12:00 UTC | 2h 50m |
| 2026-06-10 | SVA211 | JED → MXP | Jun 10, 12:20 UTC | Jun 11, 12:00 UTC | 23h 40m |
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 .