sensors Mode-S transponder
7100B8
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AQ14 · AIRBUS A-330-300
- Hex
- 7100B8
- Octal
- 34200270
- Decimal
- 7,405,752
- Country
- SA
- Tail
- HZ-AQ14
- Type
- A333
- Flights observed
- 49
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 7100B8 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 |
|---|---|---|---|
| SVA417 | Saudi Arabian Airlines | 5 | 2026-05-13 |
| SVA258 | Saudi Arabian Airlines | 4 | 2026-04-21 |
| SVA708 | Saudi Arabian Airlines | 3 | 2026-04-20 |
| SVA321 | Saudi Arabian Airlines | 3 | 2026-05-13 |
| SVA259 | Saudi Arabian Airlines | 3 | 2026-04-20 |
| SVA239 | Saudi Arabian Airlines | 3 | 2026-04-13 |
| SVA238 | - | 3 | 2026-04-13 |
| SVA709 | Saudi Arabian Airlines | 2 | 2026-04-18 |
| SVA597 | Saudi Arabian Airlines | 2 | 2026-04-27 |
| SVA596 | Saudi Arabian Airlines | 2 | 2026-04-27 |
| SVA9743 | - | 1 | 2026-05-21 |
| SVA9719 | - | 1 | 2026-05-23 |
| SVA9653 | - | 1 | 2026-05-17 |
| SVA588 | Saudi Arabian Airlines | 1 | 2026-05-26 |
| SVA5550 | - | 1 | 2026-05-18 |
| SVA418 | - | 1 | 2026-04-24 |
| SVA389 | Saudi Arabian Airlines | 1 | 2026-04-30 |
| SVA388 | Saudi Arabian Airlines | 1 | 2026-05-28 |
| SVA386 | Saudi Arabian Airlines | 1 | 2026-05-27 |
| SVA383 | Saudi Arabian Airlines | 1 | 2026-05-21 |
Recent flights last 49
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-28 | SVA388 | CAI → JED | May 28, 20:40 UTC | May 28, 20:50 UTC | 10m |
| 2026-05-27 | SVA386 | CAI → JED | May 27, 23:25 UTC | May 27, 23:35 UTC | 10m |
| 2026-05-26 | SVA588 | JED → DXB | May 26, 11:20 UTC | May 26, 14:50 UTC | 3h 30m |
| 2026-05-23 | SVA9719 | - | May 23, 04:15 UTC | May 23, 04:45 UTC | 30m |
| 2026-05-22 | SVA210 | MXP → RUH | May 22, 14:45 UTC | May 22, 17:35 UTC | 2h 50m |
| 2026-05-21 | SVA211 | JED → MXP | May 21, 21:20 UTC | May 22, 11:40 UTC | 14h 20m |
| 2026-05-21 | SVA9743 | - | May 21, 08:45 UTC | May 21, 09:05 UTC | 20m |
| 2026-05-21 | SVA383 | JED → CAI | May 21, 01:55 UTC | May 21, 02:05 UTC | 10m |
| 2026-05-20 | SVA266 | IST → JED | May 20, 11:40 UTC | May 20, 18:35 UTC | 6h 55m |
| 2026-05-20 | SVA265 | JED → IST | May 20, 01:45 UTC | May 20, 08:45 UTC | 7h 1m |
| 2026-05-19 | SVA306 | - | May 19, 01:45 UTC | May 19, 12:30 UTC | 10h 45m |
| 2026-05-18 | SVA309 | JED → CAI | May 18, 04:05 UTC | May 18, 23:45 UTC | 19h 39m |
| 2026-05-18 | SVA5550 | - | May 18, 02:50 UTC | May 18, 23:45 UTC | 20h 54m |
| 2026-05-17 | SVA9653 | - | May 17, 21:55 UTC | May 17, 23:45 UTC | 1h 50m |
| 2026-05-13 | SVA417 | RUH → CAI | May 13, 21:55 UTC | May 14, 11:25 UTC | 13h 30m |
| 2026-05-13 | SVA321 | RUH → CAI | May 13, 13:50 UTC | May 13, 20:00 UTC | 6h 10m |
| 2026-05-13 | SVA417 | RUH → CAI | May 13, 11:15 UTC | May 13, 11:40 UTC | 25m |
| 2026-05-12 | SVA313 | RUH → CAI | May 12, 15:35 UTC | May 12, 16:00 UTC | 25m |
| 2026-05-12 | SVA311 | RUH → CAI | May 12, 06:15 UTC | May 12, 06:35 UTC | 20m |
| 2026-05-09 | SVA303 | JED → CAI | May 9, 15:45 UTC | May 9, 16:00 UTC | 15m |
| 2026-04-30 | SVA389 | JED → CAI | Apr 30, 18:50 UTC | Apr 30, 19:00 UTC | 10m |
| 2026-04-27 | SVA597 | DXB → MED | Apr 27, 09:55 UTC | Apr 27, 11:00 UTC | 1h 5m |
| 2026-04-27 | SVA596 | MED → DXB | Apr 27, 06:55 UTC | Apr 27, 08:00 UTC | 1h 5m |
| 2026-04-24 | SVA418 | - | Apr 24, 13:25 UTC | Apr 24, 13:35 UTC | 10m |
| 2026-04-24 | SVA417 | RUH → CAI | Apr 24, 11:00 UTC | Apr 24, 11:20 UTC | 20m |
| 2026-04-23 | SVA597 | DXB → MED | Apr 23, 10:05 UTC | Apr 23, 16:10 UTC | 6h 5m |
| 2026-04-22 | SVA596 | MED → DXB | Apr 22, 22:00 UTC | Apr 23, 07:55 UTC | 9h 55m |
| 2026-04-22 | SVA321 | RUH → CAI | Apr 22, 13:20 UTC | Apr 22, 20:15 UTC | 6h 55m |
| 2026-04-22 | SVA417 | RUH → CAI | Apr 22, 10:55 UTC | Apr 22, 11:10 UTC | 15m |
| 2026-04-21 | SVA258 | IST → MED | Apr 21, 12:05 UTC | Apr 22, 11:10 UTC | 23h 5m |
| 2026-04-21 | SVA258 | IST → MED | Apr 21, 11:15 UTC | Apr 21, 12:55 UTC | 1h 40m |
| 2026-04-20 | SVA259 | MED → IST | Apr 20, 22:25 UTC | Apr 21, 08:55 UTC | 10h 30m |
| 2026-04-20 | SVA708 | RUH → KHI | Apr 20, 04:25 UTC | Apr 20, 20:20 UTC | 15h 56m |
| 2026-04-19 | SVA258 | IST → MED | Apr 19, 12:05 UTC | Apr 20, 10:55 UTC | 22h 50m |
| 2026-04-19 | SVA258 | IST → MED | Apr 19, 11:25 UTC | Apr 20, 10:00 UTC | 22h 35m |
| 2026-04-19 | SVA259 | MED → IST | Apr 19, 07:35 UTC | Apr 19, 08:50 UTC | 1h 15m |
| 2026-04-18 | SVA259 | MED → IST | Apr 18, 10:10 UTC | Apr 19, 08:50 UTC | 22h 40m |
| 2026-04-18 | SVA708 | RUH → KHI | Apr 18, 05:25 UTC | Apr 18, 05:40 UTC | 15m |
| 2026-04-18 | SVA708 | RUH → KHI | Apr 18, 04:45 UTC | Apr 18, 05:40 UTC | 55m |
| 2026-04-18 | SVA709 | KHI → MED | Apr 18, 04:40 UTC | Apr 18, 11:20 UTC | 6h 40m |
| 2026-04-17 | SVA709 | KHI → MED | Apr 17, 14:00 UTC | Apr 18, 11:20 UTC | 21h 20m |
| 2026-04-14 | SVA321 | - | Apr 14, 19:40 UTC | Apr 14, 20:05 UTC | 25m |
| 2026-04-14 | SVA417 | RUH → CAI | Apr 14, 10:55 UTC | Apr 14, 11:20 UTC | 25m |
| 2026-04-13 | SVA238 | - | Apr 13, 16:15 UTC | Apr 13, 18:50 UTC | 2h 35m |
| 2026-04-13 | SVA238 | - | Apr 13, 15:50 UTC | Apr 13, 18:50 UTC | 3h 0m |
| 2026-04-13 | SVA238 | - | Apr 13, 15:25 UTC | Apr 13, 16:15 UTC | 50m |
| 2026-04-13 | SVA239 | RUH → GVA | Apr 13, 12:20 UTC | Apr 13, 12:35 UTC | 15m |
| 2026-04-13 | SVA239 | RUH → GVA | Apr 13, 11:55 UTC | Apr 13, 12:35 UTC | 40m |
| 2026-04-13 | SVA239 | RUH → GVA | Apr 13, 08:25 UTC | Apr 13, 12:15 UTC | 3h 50m |
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-AQ14 page for operator, model, and routing details .